Re: [whatwg/fetch] Acting on incomplete headers (#472)

I guess there is at least one thing here to act on which is what should happen when you remove the newline after "sad" (i.e., no newlines at all after headers). At that point Firefox starts acting funny and is seemingly non-deterministic, Safari network errors the response, and Chrome keeps trucking. I will create separate tests for that and make those expect a network error per Safari's behavior.

-- 
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/472#issuecomment-772344774