On Tue, 26 Apr 2016 18:31:31 +0200 Rainer Jung <rainer.jung at kippdata.de> wrote: > The second pattern looks like "Transfer-Encoding: chunked". In this > mode, a response is sent in chunks and each chunk is preceded by a > hex number telling how big the next chunk is. The last chunk is > followed by a "0" indicating no more chunks are expected. So the "2" > is the size of the chunk size (two hex digits), next comes the chunk > itself. > > That sort of encoding is typically used for dynamic content, when the > final size of the response is not known in advance to avoid needing > to buffer the whole response before sending it. It does not use a > content-length header. Another case might be a transformation during > response delivery that changes the size in a way that is not easy to > calculate in advance, like compression. Thanks, that was it. if I look at the data coming that's exactly how it looks like. (I still wonder why apache does that - for a 404 error page - but at least now I know what's going on) -- Hanno B?ck https://hboeck.de/ mail/jabber: hanno at hboeck.de GPG: BBB51E42 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160426/b4aab656/attachment.sig>
