View Single Post
      12-20-2011, 01:30 AM   #15
Agent Smith
skinrock's Avatar

Drives: 2016 i8
Join Date: Jan 2011
Location: The Matrix

iTrader: (9)

Garage List
2016 BMW i8  [0.00]
I don't think it's necessarily a browser bug, I think the browsers that are throwing the error are doing the right thing. Chrome actually tells you:

Error 350 (net::ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION): Multiple Location headers received. This is disallowed to protect against HTTP response splitting attacks.

If you view the response headers in a browser that loads the page, you can see why it's saying this. When you click that link, the first thing it does is a 302 redirect to, since that's the actual domain you want. In order to do the redirect, it sets the Location header. Once it loads that same url on, it performs a second 302 redirect. This second redirect is because of the "goto=newpost", it changes the url to the one that takes you directly to the newest post. But it has to set the Location header again to do this. So now the browser thinks the location was changed twice, and some of them don't like it.

Further proof, if you go to directly, it can do the redirect properly: