-
Notifications
You must be signed in to change notification settings - Fork 270
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
Chunk large request bodies into multiple http.request.body events #126
Comments
You seem to be correct and you can probably turn this ticket into a feature request instead. |
Yes, you're correct. Daphne doesn't support bodies chunking at this time. |
Yup, tagged it as an enhancement. This will probably get a lot easier with the changes I'm proposing to Channels in the near future (http://www.aeracode.org/2017/7/11/towards-channels-20/), so it's likely we'll wait till then to implement it as it'll perform much better. |
Thanks, interesting read. |
Just to reconfirm that Daphne 2.0 still does not support chunking incoming HTTP bodies, though it's less of a problem as it's now an in-memory dict that gets passed around rather than going over a channel layer. It should still be fixed to read from the client socket progressively, though. |
I've encountered this problem lately and I would like to try and solve this issue. Would you say this is currently solvable? Are there any new insights about this issue? |
It's solvable, but might already be solved in |
Alternatively as the docs in Channels mentions you can route traffic based on traffic type using NGINX. If you need this up and running for production sites you can route similar to this. Requirements:
|
I've been searching through the code and Channels seems to support reading chunked bodies, but Daphne always sends the whole body in the
http.request
message.Am i missing something?
The text was updated successfully, but these errors were encountered: