You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This uses three spaces between the un-encoded password and the mountPt. [I have damaged both strings to protect the innocence). Bottom line is that HTTP (and hence NTRIP) want to see one a single space as the delimiter here. Anything else is invalid, although many devices try to make allowances.
It is not clear to me how esp32-xbee allowed this to be created as an input, but the white space should be trimmed down to make it a valid request. Ideally it should be impossible for the end user to create this.
The text was updated successfully, but these errors were encountered:
Want to bump this and ask nebkat to please contact me. When I take a look at the logs for RTK2go.com:2101 an open NTRIP Caster my employer runs, I am seeing a growing number of connections from NTRIP ESP32_XBee_Ntrip_Server/1.0 with minor problems (bad data, mixed data content, connecting without data to send, connection drop off with large buffer retries, etc.). The growing number of connections (many originating from Poland) is a tribute to the sucess of this software. But would be a bit better if some of the more common problems found in NTRIP connection logic could be fixed. And I would like to help with that.
I was looking at our public caster at RTK2go.com this morning and noticed the following (getting rejected)
This uses three spaces between the un-encoded password and the mountPt. [I have damaged both strings to protect the innocence). Bottom line is that HTTP (and hence NTRIP) want to see one a single space as the delimiter here. Anything else is invalid, although many devices try to make allowances.
It is not clear to me how esp32-xbee allowed this to be created as an input, but the white space should be trimmed down to make it a valid request. Ideally it should be impossible for the end user to create this.
The text was updated successfully, but these errors were encountered: