Cool Chris.. I didnīt know about Non-Parsed-Headers.. And, looking for the
subject in MSDN, I finally found the document that refers to the IIS bug...:
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q176113
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Christopher J. Crane
Sent: Tuesday, September 25, 2001 3:56 PM
To: chris devers
Subject: Re: Headers...
how about instead, a possilbe workaround would be to set the cookie and then
print out an HTML page with a metarefresh in the header and set it for "0"
and then the new URL, it will cause a small, possilbly undetectable delay,
but without anything else on the page to load it should go really fast.
----- Original Message -----
From: "Chris Devers" <[EMAIL PROTECTED]>
To: "Christian Azambuja Pagot" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, September 25, 2001 2:35 PM
Subject: RE: Headers...
> On Tue, 25 Sep 2001, Christian Azambuja Pagot wrote:
>
> > Ok..
> > I will try to explain my problem again (sorry, my english is not that
> > good...)
>
> That's okay...
>
> > ======
> > Case 1
> > ======
> > I have a one-line script that consists of:
> >
> > ##### begin #######################################
> > print "Location: http://www.wherever1.com\n";;
> > ##### end #########################################
> >
> > It works perfectly... it will cause a redirection in the browser.
>
> ...ok.
>
> > ======
> > Case 2
> > ======
> >
> > ##### begin #######################################
> > print "Set-Cookie: logged=1\n";
> > ##### end #########################################
> >
> > It works perfectly... it will set a cookie in the browser.
>
> ...ok.
>
> > ======
> > Case 3
> > ======
> >
> > ##### begin #######################################
> > print "Set-Cookie: logged=1\n";
> > print "Location: http://www.wherever1.com\n";;
> > ##### end #########################################
> >
> > Well... nothing happens here... No redirection occurs, neither cookies
> > are set... I inverted the order of the lines.. but the problem
> > persisted.. I read about the syntax of the http headers.. and it seem
> > to be correct.. at first sight. Actually I have no idea about what
> > could be causing that..
> >
> > I am running the script in a Win2K.. with IIS5... and I am using
> > ActivePerl..
>
> So the headers can't be sent together for you. As someone noted yesterday,
> the problem might be that IIS doesn't like doing this. I forget what the
> workaround was, but seem to remember that sending Non-Parsed Headers (nph)
> could help address the problem, becuase doing so allows you to force the
> behavior you're trying to get, at the expense of having to make sure that
> all the right headers make it out.
>
> As Lee noted, CGI.pm's cookie handling routines (among others) might be
> useful here. Alternatively, you can try to get your code working on a
> non-IIS server (Apache, iPlanet, etc) to see if the script itself is fine.
>
>
>
> --
> Chris Devers [EMAIL PROTECTED]
>
> _______________________________________________
> Perl-Win32-Web mailing list
> [EMAIL PROTECTED]
> http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
>
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
