On Mon, Apr 30, 2001 at 07:54:24PM -0400, Robert Landrum wrote:
> >On Mon, Apr 30, 2001 at 03:46:03PM -0400, Geoffrey Young wrote:
> >> > From: will trillich [mailto:[EMAIL PROTECTED]]
> >> > Sent: Monday, April 30, 2001 3:31 PM
> >> > To: [EMAIL PROTECTED]
> >> > Subject: forbidden vs. cookie
> >> [snip]
> >> >  # this don't work so hot, neither:
> >> >                  $r->header_out(-cookie=>$cookie);
> >> >                  $r->header_out(-location=>$login_uri);
> >> >                  return REDIRECT;
> >> >  # neither header is sent.
> >>
> >> you probably want $r->err_headers_out instead of $r->headers_out
> >
> >example on p. 125 doesn't -- but since success is zero for me
> >their way, i also tried your method, this way for thoroughness:
> >
> >     # called as a "PerlAccessHandler", don't forget--
> >     $r->header_out(Cookie=>$cookie);
> >     $r->err_header_out(Cookie=>$cookie);
> 
> Shouldn't these be
> 
>       $r->header_out('Set-Cookie'=>$cookie);
>       $r->err_header_out('Set-Cookie'=>$cookie);

yep. i caught that right after i posted (as usual).

> >     $r->header_out(Location=>$login_uri);
> >     $r->err_header_out(Location=>$login_uri);
> >     return REDIRECT;

so that part works -- meaning, the Set-Cookie header is sent, and
so is the Location redirector.

        linux lynx ignores set-cookie in this case.
        mac netscape does too.

g*ddamb*stardfu*kers, is all i'd like to add on that subject, at
the moment. (ask me in a minute, and i'll be glad to repeat it.)

so i'll fall back to

        <META HTTP-EQUIV="Refresh" Content = "0;
        URL=http://stupid-frogging-browser-compatibility-garbage/crapola.html";>

and try that *(&%^(*)($@#*((* method instead.

(are we having fun yet? some of us sure aren't! grr...)

-- 
don't visit this page. it's bad for you. take my expert word for it.
http://www.salon.com/people/col/pagl/2001/03/21/spring/index1.html

[EMAIL PROTECTED]
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!

Reply via email to