Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)

Relatedly, I don't think there's any spec that covers what to do on bad redirect location headers.  Browsers could ignore the header (Which for Chrome, at least, would result in treating the 3xx as the final destination, as opposed to hard-failing the request) or hard-fail, which is what Chrome actually does, after trying its best to handle non-ASCII characters.

This is a more general issue with headers outside the expected range of values - browsers can ignore the header, fail the entire request, or try their best anyways (though in the last case, of course, what "try your best anyways" means is often not clear cut, and would need to be specified - which basically means changing the spec for what values are valid, and what they mean).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/883#issuecomment-2296516409
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/883/2296516409@github.com>