-
-
Notifications
You must be signed in to change notification settings - Fork 623
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
how to send requests with large body #311
Comments
@pintsized any insights on this? I am also facing the same issue. |
What does "doesn't work" mean? I haven't got time to analyse wireshark output for you, if you need help then please provide more detail. |
sorry about that. It gives a That said, is there any limitation imposed by the library? The code I shared works absolutely fine if I remove the large body or use a smaller body. |
Before any request is made, a connection must be established. This error is telling you that, for some reason, your Nginx server cannot open a connection to the URI. You'll want to investigate that. |
I just figured it out that using My use case is a So I wanted to know if I should do something extra when dealing with large request body? Is there a threshold, I could do something like
Here is the original issue if you are interested
The URI is perfectly fine, I can assure you of that. |
I can't say why you're having problems sending a largish body directly - there are no hardcoded limitations (other that nginx worker memory). If you really want to allocate 11MB of data in a string and push it over the wire in one go, well I guess it should work. But you probably don't want to do that. The If you get a |
I am facing problems sending requests with large body as it fails with a
connection refused
error. Here is the code snippet that doesn't work:Here is a capture of the request using wireshark: https://drive.google.com/file/d/19UajGULTjN4eJJKfSKdzHV7JwpwxEPWm/view?usp=sharing
The text was updated successfully, but these errors were encountered: