Project

General

Profile

Bug #387

Some apps not using long URL, redirects

Added by jcleftie over 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
12/23/2009
Due date:
% Done:

0%


Description

Example:

Blog - WordPress - When you hover over the link under installed apps in the HDA it shows the long URL in the browser status window, but when clicked, redirects to the short url of http://blog. Typing the long URL by hand takes me to http://www.blog.com. When accessing the HDA through the VPN, all apps should be useable through the long URL.

Other apps also have this problem, I can update the bug with whatever others I find and can duplicate.

History

#1 Updated by cpg over 11 years ago

  • Status changed from New to Closed
  • Assignee set to cpg

i just checked it and it is using long URLs.

however, this looks like it is actually an instance of #398 ... which is a big battle we're having with DNS ...

so, my theory of what it's happening is that the full url is being used (as indicated by the address bar), then it is not resolving, which bounces to OpenDNS, which gives it to blog.com. ...

feel free to reopen if you think it needs to be, needless to say.

#2 Updated by kingsizebk almost 11 years ago

cpg wrote:

i just checked it and it is using long URLs.

however, this looks like it is actually an instance of #398 ... which is a big battle we're having with DNS ...

so, my theory of what it's happening is that the full url is being used (as indicated by the address bar), then it is not resolving, which bounces to OpenDNS, which gives it to blog.com. ...

feel free to reopen if you think it needs to be, needless to say.

Here is what is happening for me (a fresh installation, by the book, on 5/22/2010):

Just as described above, when I hover over the link in the browser I see the full/long URL and when I click it, I end up on the OpenDNS page. I used curl to see what is going on and I found that the GET request is sent to the full/long URL and the response contains a redirect (HTTP 302) to the short URL. Here it is (obfuscated intentionally):

#>curl -vvv http://blog.domain.tld
  • About to connect() to blog.domain.tld port 80 (#0)
  • Trying 208.111.200.248... connected
  • Connected to blog.domain.tld (111.222.333.444) port 80 (#0)

GET / HTTP/1.1
User-Agent: curl/7.19.0 (i386-pc-win32) libcurl/7.19.0 OpenSSL/0.9.8h zlib/1.2.3
Host: blog.domain.tld
Accept: */*

< HTTP/1.1 301 Moved Permanently
< Date: Sun, 23 May 2010 18:26:18 GMT
< Server: Apache/2.2.14 (Fedora)
< X-Powered-By: PHP/5.3.2
< X-Pingback: http://blog/xmlrpc.php
< Location: http://blog/
< Content-Length: 0
< Connection: close
< Content-Type: text/html; charset=UTF-8
<
  • Closing connection #0

Also available in: Atom