Re: [whatwg/fetch] HTTP 101 response NOT for websockets (Issue #1397)

> I thought this was no longer valid, but it still is. It now affects this line:
> 
> > If status is 101, break.
> 
> Another way of handling this might be to refactor "process early hints response" and make it work for any 1xx response, requiring the caller to filter.

I don't see the advantage is that. early hints are specific to 103. Perhaps in the future we would have other provisional 1xx headers that fetch needs to deal with like 101.

> 
> Thinking about it, perhaps that's even necessary? Or does a WebSocket handshake succeed if the server first sends a 199 and then a 101? And what about a 199 and then a 103?
> 

Yes, the way I understand a 109 etc. should simply be ignored (until someone specifies that it does something).




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

Message ID: <whatwg/fetch/issues/1397/1197740090@github.com>