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]
