|Chrome Throws Error 305 on Redirections to HTTPS or WWW Addition to URL||kelana777||12/23/11 3:11 AM|
Google Chrome version 16.0.912.63:
Operating System: All
Error Message: Error 350 (net::ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION): Multiple Location headers received. This is disallowed to protect against HTTP response-splitting attacks.
Extensions installed: Irrelevant
It seems that v16 now regards redirection to the same URL as a 305 error. Fair enough, that makes sense since self-redirection is suspicious.
But, Chrome16 seems to not count the WWW nor HTTP(S) part of the URL. So a redirection to a secure connection or a redirection to add 'www' to the front of the URL resulted in the error.
None of the other major browsers (IE, FF) exhibit this behaviour.
I think a "self"-redirection to HTTPS is perfectly acceptable as most websites do not make their whole website secure, but just on certain pages where sensitive information is being passed on.
Additionally, Google doesn't like duplicate connection so it's safe to say most SEO best practices include a self-redirection to the "www." version of the URL when a visitor accidentally goes to the non-www version of the URL.
Does anyone see this behaviour and/or know how are we supposed to treat these redirections?
|Re: Chrome Throws Error 305 on Redirections to HTTPS or WWW Addition to URL||aris2168||12/23/11 3:29 PM|