On 28/02/2026 00:45, Matus UHLAR - fantomas wrote:
Hello,

our client uses SW RTKLIB which tends to send data using GET requests, containing request body (...) with no Transfer-Encoding: or Content- Length: headers and using HTTP/1.0 protocol (hardcoded).


On squid, the request body is dropped

Am I correct if I assume this is correct from protocol point of view
or is there any way to pass this data through proxy?


This is odd behaviour from RTKLIB (and invalid HTTP). The other NTRIP protocol agents I could find doing the same operation do not send anything after their GET request headers.

The RTKLIB sources show it sending a Connection::close. So to any HTTP agent(s) it will just be unwanted extra bytes on the TCP stream, they will be dropped and maybe logged.


To send any content in an HTTP/1.0 GET request requires the Content-Length header.

NTRIP protocol specification claims to be HTTP/1.1 compliant which means Transfer-Encoding is technically valid, although still semantically dubious for GET. Better just not to send content in GET.

HTH
Amos

_______________________________________________
squid-users mailing list
[email protected]
https://lists.squid-cache.org/listinfo/squid-users

Reply via email to