Custom Query (104 matches)
Results (37 - 39 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #112 | fixed | Case sensitive when checking request headers, not HTTP standard | ||
| Description |
Hello, we receveived an email describing a problem with the professional NtripCaster: "One thing I just happened to notice is that the caster seems to be case sensitive when checking request headers. It would be nice if this was case insensitive to follow the HTTP standard. This was an issue for me because I was trying to use a service which converts request headers to lowercase and so all requests were NTRIP v1 because "ntrip-version" isn't "Ntrip-Version", and since v1 responses aren't HTTP they were being dropped by the service." Best regards, Peter Neumaier |
|||
| #111 | worksforme | TLS protocol together with a proxy server doesn't work | ||
| Description |
Hello, when setting up a relay and trying to use TLS protocol together with our proxy, we cannot receive data. Using the same TLS connection without proxy works fine. The proxy doesn't seem to be the problem, because we are successfully receiving data through the same port when using BNC software. We are using Ntrip Caster Version 2.0.36. Best regards, Peter |
|||
| #110 | fixed | Missing GLONASS slot numbers in RINEX | ||
| Description |
I have BNC 2.12.6 generating RINEX 3 observation files for a number of stations that have RTCM MSM 4 streams. The manual indicates that in order to decode the slot number I need to add an ephemeris stream with message 1020. I have added the RTCM3-MGEX IGS stream for this. I can see I am getting GLONASS ephemerides as BNC will write out the RINEX 3 navigation file with this data. However all my observation files have an empty GLONASS slot header:
|
|||
