|
| 1 | +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 | +<HTML> |
| 3 | + <HEAD> |
| 4 | + <TITLE> [squid-users] passing request body in GET requests |
| 5 | + </TITLE> |
| 6 | + <LINK REL="Index" HREF="index.html" > |
| 7 | + <LINK REL="made" HREF="mailto:squid-users%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-users%5D%20passing%20request%20body%20in%20GET%20requests&In-Reply-To=%3Ca55651a5-2fac-4819-8c56-d1f0d31737f2%40treenet.co.nz%3E"> |
| 8 | + <META NAME="robots" CONTENT="index,nofollow"> |
| 9 | + <style type="text/css"> |
| 10 | + pre { |
| 11 | + white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ |
| 12 | + } |
| 13 | + </style> |
| 14 | + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> |
| 15 | + |
| 16 | + |
| 17 | + </HEAD> |
| 18 | + <BODY BGCOLOR="#ffffff"> |
| 19 | + <H1>[squid-users] passing request body in GET requests</H1> |
| 20 | + <B>Amos Jeffries</B> |
| 21 | + <A HREF="mailto:squid-users%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-users%5D%20passing%20request%20body%20in%20GET%20requests&In-Reply-To=%3Ca55651a5-2fac-4819-8c56-d1f0d31737f2%40treenet.co.nz%3E" |
| 22 | + TITLE="[squid-users] passing request body in GET requests">squid3 at treenet.co.nz |
| 23 | + </A><BR> |
| 24 | + <I>Sun Mar 1 02:24:20 UTC 2026</I> |
| 25 | + <P><UL> |
| 26 | + |
| 27 | + |
| 28 | + <LI> <B>Messages sorted by:</B> |
| 29 | + <a href="date.html#27823">[ date ]</a> |
| 30 | + <a href="thread.html#27823">[ thread ]</a> |
| 31 | + <a href="subject.html#27823">[ subject ]</a> |
| 32 | + <a href="author.html#27823">[ author ]</a> |
| 33 | + </LI> |
| 34 | + </UL> |
| 35 | + <HR> |
| 36 | +<!--beginarticle--> |
| 37 | +<PRE>On 28/02/2026 00:45, Matus UHLAR - fantomas wrote: |
| 38 | +><i> Hello, |
| 39 | +</I>><i> |
| 40 | +</I>><i> our client uses SW RTKLIB which tends to send data using GET requests, |
| 41 | +</I>><i> containing request body (...) with no Transfer-Encoding: or Content- |
| 42 | +</I>><i> Length: headers and using HTTP/1.0 protocol (hardcoded). |
| 43 | +</I>><i> |
| 44 | +</I>><i> |
| 45 | +</I>><i> On squid, the request body is dropped |
| 46 | +</I>><i> |
| 47 | +</I>><i> Am I correct if I assume this is correct from protocol point of view |
| 48 | +</I>><i> or is there any way to pass this data through proxy? |
| 49 | +</I> |
| 50 | + |
| 51 | +This is odd behaviour from RTKLIB (and invalid HTTP). The other NTRIP |
| 52 | +protocol agents I could find doing the same operation do not send |
| 53 | +anything after their GET request headers. |
| 54 | + |
| 55 | +The RTKLIB sources show it sending a Connection::close. So to any HTTP |
| 56 | +agent(s) it will just be unwanted extra bytes on the TCP stream, they |
| 57 | +will be dropped and maybe logged. |
| 58 | + |
| 59 | + |
| 60 | +To send any content in an HTTP/1.0 GET request requires the |
| 61 | +Content-Length header. |
| 62 | + |
| 63 | +NTRIP protocol specification claims to be HTTP/1.1 compliant which means |
| 64 | +Transfer-Encoding is technically valid, although still semantically |
| 65 | +dubious for GET. Better just not to send content in GET. |
| 66 | + |
| 67 | +HTH |
| 68 | +Amos |
| 69 | + |
| 70 | +</PRE> |
| 71 | + |
| 72 | +<!--endarticle--> |
| 73 | + <HR> |
| 74 | + <P><UL> |
| 75 | + <!--threads--> |
| 76 | + |
| 77 | + |
| 78 | + <LI> <B>Messages sorted by:</B> |
| 79 | + <a href="date.html#27823">[ date ]</a> |
| 80 | + <a href="thread.html#27823">[ thread ]</a> |
| 81 | + <a href="subject.html#27823">[ subject ]</a> |
| 82 | + <a href="author.html#27823">[ author ]</a> |
| 83 | + </LI> |
| 84 | + </UL> |
| 85 | + |
| 86 | +<hr> |
| 87 | +<a href="https://lists.squid-cache.org/listinfo/squid-users">More information about the squid-users |
| 88 | +mailing list</a><br> |
| 89 | +</body></html> |
0 commit comments