[ http://issues.apache.org/jira/browse/MODPYTHON-76?page=comments#action_12367168 ]
Graham Dumpleton commented on MODPYTHON-76: ------------------------------------------- Latest update on this issue is that the change of not flushing if filter closed does not in itself fix the originally reported problem. > input filter hangs in combination with mod_proxy > ------------------------------------------------ > > Key: MODPYTHON-76 > URL: http://issues.apache.org/jira/browse/MODPYTHON-76 > Project: mod_python > Type: Bug > Components: core > Versions: 3.2, 3.1.4 > Environment: Linux, Apache 2.024 and unreleased Apache 2.0.x svn version. > Reporter: Martijn Faassen > > Input filters hang when mod_proxy is in use. Other behavior seen is infinite > calls of the input filter function even though the data has already > been processed. > In Apache 2.0.24, this problem seems to be fundamental; I have no way to get > rid of the hang, except perhaps in the case of an input filter that > does not change the size of the passed-through data. > In svn Apache, the problem goes away as soon as I remove the filter.flush() > in apache.py's FilterDispatch handler. svn Apache does according to its > changelog contain a fix to mod_proxy's handling of input filters. > For my application, use of mod_proxy is essential, as mod_python is > essentially proxying another web server process. > Output filters do not seem to be affected by the presence of filter.flush(), > and in fact filter.flush() is important to make sure memory use remains small > when handling large amounts of data being outputted by the server. > All of this is rather hairy and I don't know quite what to blame; part of > this seems indeed due to Apache itself, but perhaps not everything. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
