Hello,
A few months ago, I wrote to this group because
external redirects for requests from internal
redirects were not working while redirects from normal
requests worked fine. I was running in registry mode
and was told that that was probably the source of the
problem. However, I have changed
Tom Schindl wrote:
> Hi Geoff,
>
> Geoffrey Young wrote:
>
>>Tom Schindl wrote:
>>
>>
>>>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
On Mar 22, 2006, at 2:49 PM, Michael Greenish wrote:
It's been a while since I set up the server but I
think I did it because setting up the apache config
file was easier. And the redirect works under normal
circumstances, but not when coming from an internal
redirect. What is the difference?
Hi Geoff,
Geoffrey Young wrote:
>
> Tom Schindl wrote:
>
>>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 poin
Tom Schindl wrote:
> 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 settin
>
> It's been a while since I set up the server but I
> think I did it because setting up the apache config
> file was easier. And the redirect works under normal
What's the big deal, in my idea Registry is only helpful if you want to
speed up your CGI-Scripts not for new development and many ti
> 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
>
It's been a while
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 documen
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,
grean
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
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
Hello,
I am attempting an external redirect after an internal
redirect and it isn't working.
Below are code excerpts:
use strict;
use DBI;
use Apache2::RequestRec();
use APR::Table();
use CGI;
$CGI::POST_MAX=1024 * 1024; # max 1M posts
$CGI::DISABLE_UPLOADS = 0; # change to 1 to disable
uploa
12 matches
Mail list logo
