[Web-SIG] Chunked Tranfer encoding on request content.

Graham Dumpleton grahamd at dscpl.com.au
Mon Mar 5 02:33:38 CET 2007

Sidnei da Silva wrote ..
> I'm not quite aware of the 100 Continue semantics, but I know that
> applications which request Transfer-Encoding: chunked should *not*
> expect a Content-Length response header, nor should the WSGI thingie
> doing the 'chunking' need to know it in advance.
> 'chunked' is actually very simple. Simplifying it a lot, it basically
> needs to output '%x\r\n%s\r\n' % (len(chunk), chunk) for every chunk
> of data except the last which should be '0\r\n\r\n'. The only trick
> here is ensuring that no chunk of length '0' is written except the
> last.
> What might be happening is that CherryPy is outputting the whole
> response body as a single chunk, and relying on the 'Content-Length'
> header, which would be silly, I hope that's not what's happening
> though I haven't looked.

I am not talking about the response body. I am talking about the body of
the request. For example, the body of a POST request being sent from
client to server.


More information about the Web-SIG mailing list