[
http://issues.apache.org/jira/browse/MODPYTHON-77?page=comments#action_12360898
]
Boyan Boyadjiev commented on MODPYTHON-77:
--
WinXP, Win2K, Win2K3: Patched mod_python/3.2.6-dev-20051217 with diff from
grahamd_20051105.tar.gz is working fine. The
Anyone know if there are any technical reasons why input/output filters
as they exist at the moment, applying only to body content and not
headers, can not be specified in a .htaccess files?
Specifically, the SetInputFilter, SetOutputFilter, AddInputFilter and
AddOutputFilter directives of Apache
Graham Dumpleton wrote:
Anyone know if there are any technical reasons why input/output filters
as they exist at the moment, applying only to body content and not
headers, can not be specified in a .htaccess files?
Specifically, the SetInputFilter, SetOutputFilter, AddInputFilter and
AddOutputFi
This sounds like a good idea, but it's probably better to push this off to
3.3 just to veer on the side of caution.
My $0.02
Grisha
On Tue, 20 Dec 2005, Graham Dumpleton wrote:
Anyone know if there are any technical reasons why input/output filters
as they exist at the moment, applying onl
Jorey Bump wrote ..
> Graham Dumpleton wrote:
> > Anyone know if there are any technical reasons why input/output filters
> > as they exist at the moment, applying only to body content and not
> > headers, can not be specified in a .htaccess files?
> >
> > ...
> >
> > So, does anyone know why this
Grisha wrote ..
>
> This sounds like a good idea, but it's probably better to push this off
> to
> 3.3 just to veer on the side of caution.
>
> My $0.02
>
> Grisha
Grisha, do you remember why the following warning is present in
directive_PythonInputFilter() and directive_PythonOutputFilter() o
