Comment #15 on issue 20117 by verdyp: Chrome doesn't respect http-equiv refresh with space instead of semicolon http://code.google.com/p/chromium/issues/detail?id=20117
Note that the HTTP "Refresh" header was not specified in any RFC; it was tolerated with HTTP/1.0 as a vendor extension, but it is disallowed with HTTP/1.1, i.e. RFC 2616; it has been replaced with the standard "Location" header with some restrictions and semantics (to comply with HTTP proxies). The "location" header also requires an absolute URI and can only be returned with specific HTTP status for redirects. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
