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

Thank you for reporting this, I've done some work on specifying headers better, but have not had the time to investigate `Location` more fully. (See #814.)

I was hoping we could use https://infra.spec.whatwg.org/#isomorphic-encode, but unfortunately that would not match what you are seeing.

Another thing that's problematic around `Location` is when there's duplicate headers. And in particular if we somehow want to preserve equivalency between comma-separated and newline-separated values. (That's a thing I'm aiming for, to be robust against naïvely-combining intermediaries.)

Have you written web-platform-tests when fixing this regression?

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