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. Graham _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
