Informational response not treated as a response for httpcore.stream.
#572
-
|
A websocket handshake requires the client send a certain request, and the server respond with a 101 status code (indicating that both should switch to websockets protocol). However, HTTPCore continues a loop for an event until it gets an HTTPCore should probably support this usecase. Reproducer: I was under the impression this was the intended method for websockets due to encode/httpx#304 (comment). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think you've got the right impression here, yes, but haven't had a chance to look at it yet. Will try to do so later this week, but nudge me if I don't get there... |
Beta Was this translation helpful? Give feedback.
-
|
Okay, now resolved here... #581 |
Beta Was this translation helpful? Give feedback.
I think you've got the right impression here, yes, but haven't had a chance to look at it yet. Will try to do so later this week, but nudge me if I don't get there...