Ticket #612 (enhancement)
Opened 2 years ago
Last modified 2 years ago
Mechanism to set Content-Length on streamed responses
Status: closed (fixed)
| Reported by: | cduffy@spamcop.net | Assigned to: | rdelon |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | CherryPy code | Keywords: | |
| Cc: |
Presently, Content-Length is cleared when streaming; the reasoning is discussed on-list at http://permalink.gmane.org/gmane.comp.python.cherrypy/2817.
Quoting from said email (by Robert Brewer):
The solution I've wanted to pursue for a while now is this: provide a different "safe" mechanism via the "chunked" transfer-coding (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1), which would require cooperation on the WSGI server side. If we had that, then we could make that the norm and allow "streaming" content to be unsafe in rare cases. But until we have that, I have a hard time only providing an "unsafe" mechanism.
Change History
12/02/06 13:51:27: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
- milestone set to 3.0.


Fixed in trunk in [1465].