all these requests are equivalent conforming to rfc 2616 (HTTP/1.1) (CR LF omitted for better readability) (1) HEAD / HTTP/1.1 Host: hardened.gentoo.org (2) HEAD / HTTP/1.1 Host:hardened.gentoo.org (3) HEAD http://www.gentoo.org/ HTTP/1.1 Host: hardened.gentoo.org (4) HEAD / HTTP/1.1 Host: hardened.%67entoo.org (5) HEAD / HTTP/1.1 Host: hardened.gentoo.org:80 (6) HEAD / HTTP/1.1 Host: hardened.gentoo.org: Request (1) works fine (HTTP/1.1 301 Moved Permanently), all other fail (HTTP/1.1 404 Not Found). As a consequence, hardened.gentoo.org may not be usable behind some proxies, with exotic clients, tools like net-analyzer/httping, self-written scripts or manual usage of telnet. (www.gentoo.org works perfectly with corresponding requests)
There's no hardened.gentoo.org site, it's only a redirect from UltraDNS, i.e. not a Gentoo server: $ host hardened.gentoo.org hardened.gentoo.org is an alias for crs.ultradns.net. crs.ultradns.net has address 204.74.99.100 $ curl -I hardened.gentoo.org HTTP/1.1 301 Moved Permanently Date: Wed, 18 Feb 2009 17:28:32 GMT Server: UltraDNS Client Redirection Server Last-Modified: Wed, 18 Feb 2009 17:28:32 GMT Accept-Ranges: none Connection: close Content-type: text/html Location: http://www.gentoo.org/proj/en/hardened/
Yes, but still the redirect fails and gives the impression, as if hardened.gentoo.org was completely broken, because http://hardened.gentoo.org/ is the main portal for hardened. A working redirect is also expected from some ebuilds like e. g. app-misc/pax-utils (HOMEPAGE="http://hardened.gentoo.org/pax-utils.xml"). However, I just wanted to have this pointed out. Leaving RESOLVED CANTFIX.
Reopening to elevate to UltraDNS.
UltraDNS ticket filed. Confirmation to mirror-admin@ with Message-Id <20090219015818.DD36BB5CBC@smtp.gentoo.org>
Got a first response from UltraDNS. No resolution yet.
UltraDNS response: > We have evaluated the results you submitted regarding our URL > Forwarding product. We are currently reviewing the redesign efforts > to modify the behavior of the product for your redirection requirements > and compliance standards. We will keep you updated regarding > the progress of our scheduling and development efforts to fix > this behavior. So we're in for a wait of 1-3 months probably for their full development cycle.
I just tested all requests from above again. They all seem to work now. Therefore I set this bug to RESOLVED/FIXED now.
(In reply to comment #7) > I just tested all requests from above again. They all seem to work now. > Therefore I set this bug to RESOLVED/FIXED now. > Thanks.
