This means the when the documentation holds information about situation where one has to use $r->status(), I would propose that in should add the use case of filters.
This has nothing TODO with your problem I only wanted to point out that
not all cases where setting $r->status manually are documented there.
Why are you running this as a registry script? You are referencing so
many things only available in mod_perl that you could simply wrap
your whole code inside "sub handler { }" and you don't have to set
$r->status() manually which may be the problem.
Tom
Michael Greenish wrote:
> I am working in modperl::registry (not writing my own
> handlers) and I found this recipe on the modperl
> website:
>
> http://perl.apache.org/docs/2.0/user/coding/cooking.html#Sending_Cookies_in_REDIRECT_Response__ModPerl__Registry_
>
> And, sorry Tom, but I don't understand your response.
>
>
> thanks,
>
> greanie
>
> --- Tom Schindl <[EMAIL PROTECTED]> wrote:
>
>
>>Fred Moyer wrote:
>>
>>>Michael Greenish wrote:
>>>
>>>>use strict;
>>>
>>>[..]
>>>
>>>
>>>># redirect
>>>>$r->headers_out->set( Location => $redirectURL );
>>>>$r->status( REDIRECT );
>>>
>>>>return REDIRECT;
>>>
>>>I see a few things here that catch my eye but what
>>
>>stands out the most
>>
>>>is the use of the same return code for the browser
>>
>>and apache. why are
>>
>>>you using $r->status? Is it one of the reasons
>>
>>listed here?
>>
>>This doesn't help but:
>>
>>To the list you definately have to add Filters where
>>one mp2 or Apache i
>>don't know doesn't care about the resturn value of
>>the filter-handler.
>>
>>Tom
>>
>>
>>
> http://perl.apache.org/docs/2.0/api/Apache2/RequestRec.html#C_status_
>
>>>
>>Tom
>>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
signature.asc
Description: OpenPGP digital signature
