[ https://issues.apache.org/jira/brow...action_12511031 ]

Mike Looijmans commented on MODPYTHON-238:
------------------------------------------

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 u
se 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 surpris
e someone.

Mike Looijmans
Philips Natlab / Topic Automation






> 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 allo
w handlers to use:
>   req.connection.keepalive = apache.AP_CONN_CLOSE
> Doing this before any data is written has the effect of disabling keepalive and al
so turning off chunked encoding for response content when no content length has been
 supplied.

[ Post a follow-up to this message ]