Hello
When visiting the website (http://www.akiba-online.com/forum/main.php) with Firefox Beta, I get this message:
The problem also occurs with Firefox Aurora and Nightly, but not with the latest stable Firefox.
After some tests, it seems that the problem is due to an empty "Location" header in the HTTP response (the HTTP status code is 200).
Normally, a "Location" header should be present (and valued) only with 201, 202 or 3xx status codes. See: http://en.wikipedia.org/wiki/HTTP_location.
Removing the empty "Location" header seems to correct the problem. Maybe the new Firefox under development are more strict with response headers.
Thank you to the admin of the website if he can look into this problem.
When visiting the website (http://www.akiba-online.com/forum/main.php) with Firefox Beta, I get this message:
Code:
Corrupted Content Error
The page you are trying to view cannot be shown because an error in the data transmission was detected.
The page you are trying to view cannot be shown because an error in the data transmission was detected.
Please contact the website owners to inform them of this problem.The problem also occurs with Firefox Aurora and Nightly, but not with the latest stable Firefox.
After some tests, it seems that the problem is due to an empty "Location" header in the HTTP response (the HTTP status code is 200).
Normally, a "Location" header should be present (and valued) only with 201, 202 or 3xx status codes. See: http://en.wikipedia.org/wiki/HTTP_location.
Code:
GET /forum/main.php HTTP/1.1
Host: www.akiba-online.com
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20100101 Firefox/12.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.8,fr-fr;q=0.5,fr;q=0.3
Accept-Encoding: gzip, deflate
DNT: 1
Connection: keep-alive
+++RESP 177+++
HTTP/1.1 200 OK
Content-Type: text/html; charset=ISO-8859-1
Pragma: private
X-UA-Compatible: IE=7
X-GeoIP:
Location:
Vary: Accept-Encoding
Content-Length: 77882
Date: Sat, 17 Mar 2012 17:56:08 GMT
X-Varnish: ********* *********
Age: 1685
Connection: keep-alive
Server: nginxRemoving the empty "Location" header seems to correct the problem. Maybe the new Firefox under development are more strict with response headers.
Thank you to the admin of the website if he can look into this problem.