Re: [whatwg/fetch] HTTP/1 parsing (#1156)

Unfortunately, removing old behavior here is now pretty resource intensive, in terms of launch process in Chrome:
* Add code to gather data, wait months for data.
* Get feedback from other browsers [I don't think I've ever been in contact with a single Safari person]
* Go through intent process (Tag review can probably be skipped, at least)
* Usher through release process

As I'm not longer on the network team, I have limited time to work on this sort of stuff.  That having been said, I certainly support adding tests and working towards both tighter parsing and unifying behavior here, and I can probably find time to address what I view as most concerning (which, here, is status code handling/overflow).

@kinu @yutakahirano:  Kinuko, Yutaka, would your team be interested in pursuing this?

-- 
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/1156#issuecomment-770935446