-
Notifications
You must be signed in to change notification settings - Fork 13
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
What causes 400 error? #15
Comments
I need to figure out the right error codes to use. I think pretty much any error returns the HTTP code 400 at present. Looking at the sources for the load command, this can be the result of:
Of these, I would guess that the first is most likely. You can figure this out by using the -v option with proploader. That will give you the gory details of the HTTP interactions. |
Thanks! Yes, it's the "Transfer already in progress" issue. This is a state it gets in where there's no recover short of physically power-cycling the Wi-Fi Module:
|
I'm not sure, but I think this issue has been resolved. |
Unfortunately, I think the firmware uses a HTTP 400 error for everything. I should make a pass through and try to map these to more sensible error codes. |
What causes the load returned 400 error?
When it happens, it happens very swiftly (fast response; no perceptible delay between loading second-stage loader message and the load returned 400 message. Also, it happens many time in a row during successive attempts.
The text was updated successfully, but these errors were encountered: