Comment #14 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
(reply to comments, 10 and 13, by MsGuireV110 and daniel.r.kegel) The HTTP "Refresh:" header is not supposed to be honorred if it is not an absolute URL, but here you used a relative URL "/public" (relative to the current document's URL ?). Is it supposed to work anyway when the Refresh is specified in a HTML <meta> element instead? My opinion is that the <meta> element should not accept what the HTTP header also does not accept as valid. If you make the HTTP implementation generous (accepting the comma or space instead of semicolon, or accepting relative URLs), the same patch should be applied to the HTML renderer within its support for <meta> (but the HTTP header will still have higher precedence for the header with the same "Refresh" name, ignoring case, if it is also present, as this Refrsh header type is not cumulative). -- 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 -~----------~----~----~----~------~----~------~--~---
