I think this is in the Guide somewhere, but the short answer is to
use 'err_header_out()' rather than 'header_out' for any type of
non-success result.
On Fri, 12 Apr 2002, Thomas K. Burkholder wrote:
Apologies if this is well-known - a generalized search failed to explain
the behaviour I'm seeing.
Using:
Apache/1.3.23 (Unix) Debian GNU/Linux mod_ssl/2.8.7 OpenSSL/0.9.6c
mod_perl/1.26
I'm using a perl handler in which I create a session and bind it to a
cookie if a session doesn't already exist, fetch some results from a
database, put the results in the session, then redirect to another page
that is responsible for pulling the results out of the session and
producing the html output. As a test case, I do exactly this:
$r-header_out(Set-Cookie = 'foo1=bar1');
$r-header_out(Location = $redir);
return REDIRECT;
I use curl to test with - the result does not contain the Set-Cookie
header. Is it expected behaviour that redirection should blow away
Set-Cookie headers, and I just have to find a different way to do this?
I'm pretty sure this isn't a caching issue since I'm using curl to
initiate the test.
Am I barking up the wrong tree?
Thanks in advance for any help-
//Thomas
Thomas K. Burkholder
--
Steve Reppucci [EMAIL PROTECTED] |
Logical Choice Software http://logsoft.com/ |
=-=-=-=-=-=-=-=-=-=- My God! What have I done? -=-=-=-=-=-=-=-=-=-=
