mod_wsgi removes all input/output filters

[Alexander Kolesen]

Hi,
Why should mod_wsgi remove all input/output filters except core filters?

[Graham Dumpleton]

On 29 August 2011 23:15, Alexander Kolesen <kole...@gmail.com> wrote:
> Hi,
> Why should mod_wsgi remove all input/output filters except core filters?

It only does this in the daemon process. This is because the
input/output filters are being applied in the Apache child process
that is proxying the request to the daemon process.

It was a side affect of trying to use the same Apache request handling
infrastructure on daemon side so didn't have to maintain two different
dispatching mechanisms to actual WSGI application. In the future I
will likely create a second one which works straight of data coming
off the proxy socket connection rather than trying to map it back to
Apache request object and bucket brigade.

Graham

[Graham Dumpleton]

BTW, worth pointing out is that if you ever use uWSGI with Apache, the
uWSGI module by default does actually cause Apache output filters to
be ignored. This is one of the tricks which sees it top mod_wsgi speed
if you do simple benchmarks. To get comparable configuration and
treatment of output filters by uWSGI you have to disable its use of
Apache's assbackwards mode and so enable passing of uWSGI output
through the Apache output filters.

Graham