in reply to Re^2: CGI error: "Invalid header value contains a newline not followed by whitespace"
in thread CGI error: "Invalid header value contains a newline not followed by whitespace"

The correct code is:

print $q->redirect(
    -uri    => 'http://localhost/',
    -cookie => [ $set_session, $set_username ],
    );

[download]
  • Comment on Re^3: CGI error: "Invalid header value contains a newline not followed by whitespace"
  • Download Code

Replies are listed 'Best First'.
Re^4: CGI error: "Invalid header value contains a newline not followed by whitespace"
by MyMonkName (Acolyte) on Feb 04, 2012 at 21:08 UTC
    Not really. Per the documentation, apache will ignore cookie headers in a redirect request.
[reply]

      You say this because you've tried it? Or you say this because you trust the documentation?

      The documentation doesn't say that Apache ignores the cookie - it claims that browsers ignore cookies when they are redirected. It's wrong. They don't. (Though in some early versions of Safari there was a bug where it did. This was fixed though.)

      And if they did ignore cookies when redirecting, then why do you think that structuring your code slightly differently will change things? However your code works internally, if you're printing the same HTTP headers, restructuring the code won't change anything. Browsers don't see your code - they see the HTTP headers.

[reply]
        You are right, I meant browser, not apache. At any rate, on my platform, for whatever reason, your code does not result in my browsers (FF, Chrome) storing the cookies it sends. My "incorrect" code does, though; all the more reason to not trust documentation...

        --EDIT--

        Nevermind. Your code works actually! What can I say.

        In exactly what version of CGI.pm did this behaviour change remains an open question, though. I was using the code in my OP quite satisfactorily for at least a year and a half...

[reply]

In Section Seekers of Perl Wisdom