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

In a lot cases, I suspect it's the same both ways, since the URL parser also percent-escapes some stuff. Either way such bytes will be percent-escaped. Non-ASCII bytes, however, run into questions around whether the process believes it sees plain bytes or UTF-8.

I haven't tested anything, but from source inspection, it looks like Chrome will take the first non-empty Location header, and then there's a very old TODO comment "Is this consistent with other browsers?". :-)

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