-
-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP/1.1 bidirectional streaming #1475
Comments
I'd suggest anything here would likely be folded into #1150. I'm not at all sure that we'd support this over HTTP/1.1 since it's not really designed to be used in that way, and you can't reliably know that servers or intermediaries (proxies, gateways, etc) would support it (they typically won't). In contrast to HTTP/2 which does. But in either case it's not really feasibly on our radar at this point in time. |
Closing for housekeeping… I agree with Tom, don't think this could be within our scope right now. Also because this is would be non-standard HTTP/1.1, meaning in any language you'd need to do something custom with most clients anyway. FWIW, if that's really what you need and you're fine getting your hands dirty, then feel free to look into the HTTPCore source code and duplicate and play with the HTTP/1.1 code to accomodate your use case. (Or perhaps more realistically, consider updating the server implementation to do simpler TCP socket networking, without any HTTP at all, and then do that on the client as well?) |
We do now support functionality through the "network_stream" extension. See also ticket #2599 for documenting this properly in |
Checklist
Is your feature related to a problem? Please describe.
I have an http server implementing a remote shell, think zork or zsh. When a client connects it immediately responds with "200 OK" before consuming the request body
Here's an example echo server:
Describe the solution you would like.
I want to be able to able to
await
for a response resolving when the headers have been received before the body has been sent. I'd also like to be able to send and receive data without passing a generator as the http bodyAdditional context
some sort of interface like this
The text was updated successfully, but these errors were encountered: