On 2026-07-26 15:16, Eric Covener wrote:
This number means the limit of my request line. We see there's 1 byte of
difference compared to the number given by the documentation of the server
(8190).
From my reading it looks like the high level code allocates space for
2 bytes over the limit (presumably to account for CR LF but not null
termination).
But the lower level functions it calls don't return the CR LF, only
null termination, resulting in accepting 1 additional byte of real
content.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
I understand you're saying that it's expected, though maybe not desired. But what "high level
code" and "lower level functions" do you mean?
Before a while I learned that there's this tool called ngrep (I'm quite
unfamiliar with networking). I figured out that when I run it with
ngrep -x -d any '^HEAD ' 'tcp port 80'
then I can see (it's an excerpt, of course)
61 61 61 61 61 61 61 20 48 54 54 50 2f 31 2e 31 aaaaaaa HTTP/1.1
0d 0a 48 6f 73 74 3a 20 6c 6f 63 61 6c 68 6f 73 ..Host: localhos
You can see there "0d 0a" (= CR LF) after "HTTP/1.1". Does it help?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
