in reply to CGI::Application header problem

Look at what headers actually get sent, via Mozilla Live HTTP Headers for example, and via telnet your.host 80, and by running your script from the command line.

Maybe you get/got a cached page, and something else broke your application?

If you have automated tests, these will spot if something like this happens as they do not use caching.

Replies are listed 'Best First'.
Re^2: CGI::Application header problem
by morgon (Priest) on Dec 27, 2010 at 19:13 UTC
    I have traced the response/request with firebug and it is reproducible that when commenting out the one line that adds the header the authentication works and the cookie is set, whereas when I set the header no cookie is set and hence the client cannot log in.

      So, does the cookie header get sent in the reply or not?

      Do not trust the browser to show you this.