Repository navigation
Informational response not treated as a response for httpcore.stream.
#572
Answered
by
lovelydinosaur
A5rocks
asked this question in
Potential Issue
|
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). |
Answered by
lovelydinosaur
Sep 26, 2022
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... |
1 reply
Answer selected by
lovelydinosaur
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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...