-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Crashing on some large API Requests #7014
Comments
Update: If I change my POST data to return less informaion, it wont crash. But the issue is I need all the informaion in the request. I tried updating |
I have done a work around by call calling the API from another server and creating a smaller API from that responce containing only the informaion I need that the ESP then calls |
@jLynx what was the original returned data size? Use Fiddler or Wireshark to catch it. |
@Misiu as mentioned above, it's 15,287 |
@jLynx sorry, I missed that |
Multiply that by 2x since there will be copying involved if you're using Your change to StackThunk has no effect on HTTP requests. You will need to use a different, non-buffering way to access the data, and it will probably need to be parsed as it comes in, not buffered until completely received. |
Basic Infos
Platform
Settings in IDE
Problem Description
Crashing on some API POST calls.
I can make my first call which logs into the site and returns a JSON object containing a token
Next I need to use that token as a cookie to get the real data I need from the API, the issue is it crashes here and I am not quite sure why.
In this example I have removed getting the token and just hard coded it in as it still crashes when I do that.
MCVE Sketch
Debug Messages
Decoded:
I have also tried doing what was suggested on #6811
But I was not able to get a read out as it would just crash
Note: When I give it an incorrect cookie, it works fine and dispalys and error saying I am not logged in, when I give it a valid cookie it will crash. This leaves me to beleive that the response it too long for it to handle maybe?
The length of the content I should be getting back will vary but is currently: 15,287 (Worked this out by calling the API on my desktop)
The text was updated successfully, but these errors were encountered: