Yeah, and I got it towork, turns out I needed an absolute path too.
I saw that answer but since the reasn that was given is because it's in
Apache,
it didn't seem to apply. I guess the real reason is brower's are just too
brain
dead to handle it...
o _
/|/ | Jerrad Pierce \ | __|_ _|
/||/ http://pthbb.org . | _| |
\|| _.-~-._.-~-._.-~-._@" _|\_|___|___|
> -----Original Message-----
> From: ___cliff rayman___ [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 30, 2000 17:31
> To: Wim Kerkhoff; [EMAIL PROTECTED]
> Subject: Re: Wierd problem with redirect
>
>
> actually \n\r\ is really how it is supposed to be.
> i am sure you will find it in the RFC's.
> most browsers seem to be okay with \n's only.
>
> --
> ___cliff [EMAIL PROTECTED]
>
> Wim Kerkhoff wrote:
>
> > On 30-May-2000 Jerrad Pierce wrote:
> > > I'm running into an odd redirect ptoblem myself, I'm issuing:
> > >
> > > HTTP/1.1 302 Moved Temporarily\n\r
> > > Date: Tue 30 May 2000 18:18:07 GMT\n\r
> > > Server: Apache/1.311\n\r
> > > Set-Cookie: SESSION_ID=4177a0c9ae2b278decd6038901b28a2a; path=/;
> > > expires=Thu, 1-Jan-70 00:20:00 GMT;\n\r
> > > Location: /\n\r
> > >
> > > And the browser gets the cookie, but it does not redirect...
> > > It displayes the Locaiton as the document content
> >
> > Why are you tacking the \r onto each line? You don't need
> to do that, AFAIK.
> >
> > After the last line in the header, you always need to put a
> double newline, ie,
> > change your last line to:
> >
> > Location: /\n\n
> >
> > Regards,
> >
> > Wim Kerkhoff, Software Engineer
> > NetMaster Networking Solutions
> > [EMAIL PROTECTED]
>
>
>
>
