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

So two main things with this header as far as I can tell:

1. We need to figure out the set of bytes that map to their code point equivalent and those that need to go through https://url.spec.whatwg.org/#percent-encode for the `Location` header. The resulting string can go into the URL parser, for which there are browser differences, but that's a separate layer that needs solving independently.
2. We need to figure out the duplicate value situation.

There's also the base URL question, that #633 goes into and still isn't resolved, but can be solved independently from the parser aspects.

-- 
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-474811864