- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 01 Feb 2005 03:29:59 +0000
- To: www-validator-cvs@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1069 ------- Additional Comments From ot@w3.org 2005-02-01 03:29 ------- (In reply to comment #0) > Seems that when you have in an img tag, > src="http://domain.com///path_to_file/file.jpg" the validator returns a 302 > localhost error. Do you have any conclusive sign that this behaviour only happens when the page contains an image? Here is the transcript of an HTTP session: % telnet actionhour.net 80 Trying 66.235.203.171... Connected to host219.ipowerweb.com. Escape character is '^]'. HEAD /test2.html HTTP/1.1 Host: actionhour.net User-Agent: W3C_Validator/1.305.2.148 libwww-perl/5.803 HTTP/1.1 302 Found Date: Tue, 01 Feb 2005 03:08:50 GMT Server: Apache/1.3.31 (Unix) mod_log_bytes/0.3 FrontPage/5.0.2.2635 PHP/4.3.10 mod_ssl/2.8.19 OpenSSL/0.9.7d Location: http://localhost/ Content-Type: text/html; charset=iso-8859-1 As you can see, it's the server that redirects, in a strangely broken manner, the page requested to http:/ /localhost. This is not the first time we get this "redirection to localhost" problem: http://lists.w3.org/Archives/Public/www-validator/2005Jan/0100.html http://lists.w3.org/Archives/Public/www-validator/2005Jan/0098.html % host actionhour.net actionhour.net has address 66.235.203.171 % host www.ezyworkathome.com www.ezyworkathome.com has address 66.235.203.80 These two are using the same ISP (iPowerWeb) % host www.falconberry.com www.falconberry.com has address 66.235.193.159 The third one was using a different ISP (Startlogic.com), contacted their tech support and apparently the issue is gone. All three are using the same server software: Server: Apache/1.3.31 (Unix) mod_log_bytes/0.3 FrontPage/5.0.2.2635 PHP/4.3.10 mod_ssl/2.8.19 OpenSSL/0.9.7d Either there is a version of apache with frontpage extensions being distributed that is broken (or comes with broken configuration defaults), or this is a new trend among Web Hosting companies. We'll have to contact these WebHosts to figure it out...
Received on Tuesday, 1 February 2005 03:30:00 UTC