|
Mike Looijmans
nlv11281 at natlab.research.philips.com
Mon Jul 9 01:13:29 EDT 2007
If there is a separate req.chunked, I'd advise to keep them separated. It's perfectly valid to have a chunked stream with a connection: close setting, and someone is bound to use that. For one thing, it allows the client to reliably detect whether all the data has really been sent. Having a side-effect like setting one disables the other is bound to surprise someone. Mike Looijmans Philips Natlab / Topic Automation Graham Dumpleton (JIRA) wrote: > [ https://issues.apache.org/jira/browse/MODPYTHON-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510973 ] > > Graham Dumpleton commented on MODPYTHON-238: > -------------------------------------------- > > Actually also need to make req.chunked writable. As it has to be set to 0 in combination with setting close for keepalive to disabled chunked encoding for response. > >> req.connection.keepalive should be writable >> ------------------------------------------- >> >> Key: MODPYTHON-238 >> URL: https://issues.apache.org/jira/browse/MODPYTHON-238 >> Project: mod_python >> Issue Type: Improvement >> Components: core >> Affects Versions: 3.3.1 >> Reporter: Graham Dumpleton >> Priority: Minor >> >> The attribute req.connection.keepalive should be writable. This would allow handlers to use: >> req.connection.keepalive = apache.AP_CONN_CLOSE >> Doing this before any data is written has the effect of disabling keepalive and also turning off chunked encoding for response content when no content length has been supplied. >
|