-
Notifications
You must be signed in to change notification settings - Fork 46
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
431 Request Header Fields Too Large #24
Comments
Hi Jon, Thanks for submitting, this probably means your browser has some very large header that it is sending to the ESP32. If you are using Chrome, could you try:
Just to check whether this is an unusual header from your browser, or if it is a standard request for which the maximum request header size should be adjusted in the ESP32. Best Regards, |
This might be off topic, but I post it in case it is not, apologies if it is. If the "Header fields are too long" could be referring to the reply from the NTRIP Caster in case of error it is easy for this to be quite large. Please be aware the size of a full reply will vary with the number of entries in the Caster table. A small Caster might be <500 bytes, while a large one can exceed 150kb. The RTK2go machine states "Content-Length: 35403" just at the moment (the actual header part is much smaller). If your connection is accepted you get ICY 200, but if there are any issues you get the full table sent back at you. This is as per the RTCM NTRIP spec. |
Out of curiosity I checked the size of the Headers in my browser's request was sending to get the local web config page. 434 characters, so not 512 characters but getting a bit close for comfort. It is amazing how verbose things are these days. |
Fixed in 8f91f4b |
Hi,
I keep receiving this in my log file, and when the http page refreshes. The full error is:
I'm using v0.5.2 with NTRIP server configured to work with rtk2go.com.
Without packet capturing I don't think I can get the full header etc, so any advice on how best to achieve this most welcome!
A great product, will be very handy...
Jon
The text was updated successfully, but these errors were encountered: