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,
>>>
>>>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
>>>request-status automatically? E.g. if there's an untrapped error.
>>
>>
>>this is a bug in the filter implementation that someone just needs to get
>>around to fixing.  grep for BAD_REQUEST in modperl_filter.c for the details.
>>
>>--Geoff
>>
>>
> 
> 
> I'll take a look but my C-knownledge is far from good.
> 
> Tom

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to