So I propose the following documentation patch many people may not grasp
that they need to look into the sources to find out that their filter
will always return HTTP-Status OK to their clients although they return
SERVER_ERROR ;-)
Tom
Geoffrey Young wrote:
>
> Tom Schindl wrote:
>
>>Hi,
>>
>>s
Well I figured out that the test I was running was on an old version of
mod_perl. I'll give it a try on the 2.0.2-release as fast as possible
from the code it looks like 2.0.2 doesn't return OK in this situation.
Tom
Tom Schindl wrote:
> Geoffrey Young wrote:
>
>>Tom Schindl wrote:
>>
>>
>>>Hi,
Geoffrey Young wrote:
>
> Tom Schindl wrote:
>
>>Hi,
>>
>>solved it myself $f->r->status() how stupid I haven't seen this before,
>>works like a charme but one more question, what is a filter supposed to
>>return on ERROR why does one have to set the status one self and return
>>Apache2::Const::S
Tom Schindl wrote:
> Hi,
>
> solved it myself $f->r->status() how stupid I haven't seen this before,
> works like a charme but one more question, what is a filter supposed to
> return on ERROR why does one have to set the status one self and return
> Apache2::Const::SERVER_ERROR from the filter
Hi,
solved it myself $f->r->status() how stupid I haven't seen this before,
works like a charme but one more question, what is a filter supposed to
return on ERROR why does one have to set the status one self and return
Apache2::Const::SERVER_ERROR from the filter handller isn't setting the
reques
Hi,
I'm on the way to release a new version of my AxKit-Port to Apache2
named Apache2::TomKit and are facing the problem that I need to set the
HTTP-Status to SERVER_ERROR when the transformation fails but I have the
feeling that this is not possible any more in this situation.
Any suggestions?
