|Subject:||Reading a HTTP stream - big "Content-Length" mismatch|
|Posted by:||R.Wieser (addre…@not.available)|
|Date:||Thu, 5 Sep 2019|
I'm trying to read raw HTTP data, and just ran into a situation where the
"Content-Length" entry exeeded the actual content length by a /large/ margin
(~350 KB vs ~50KB). A bit of googeling tells me that that should never
happen, and should be regarded as an error.
One "minor" detail though: The header also contains a "Connection: close"
entry, but some more googeling doesn't tell me which one /should/ take
priority, if at all(!).
The involved URL is https://www.questionablecontent.net/QCRSS.xml (its a
Does anybody know how cases like these should be handled ?
I tried to find a more related newsgroup for the above question, but could
not find one. If one exists than please advice.