in reply to CGI cookie problem

Running this from the command line, I see what looks like a correct cookie being printed:
Set-Cookie: CGISESSID=1a0d5dbd88aafd8d35e41b93f72a16b0; path=/; expire +s=Thu, 04-Mar-2004 16:10:51 GMT; secure Date: Thu, 04 Mar 2004 15:11:12 GMT Content-Type: text/html; charset=ISO-8859-1
Are you, by any chance, blocking cookies in your browser?

If you have mozilla, install the live http headers extension. It should help you see exactly what headers the site is sending you, and determine if the cookie is or isn't present.

If you're using IE, I don't know how to help you, although I see that google showed some adverts for tools that appear like they might be useful when I searched for "live http headers".

Replies are listed 'Best First'.
Re: Re: CGI cookie problem
by qadwjoh (Scribe) on Mar 04, 2004 at 15:32 UTC
    Thats what I though aswell, but I looked in my cookies folder and saw other cookies being set by other sites...

    A
      I've figured out what the problem is, but not how to fix it...

      The cookie is set if I access the site by the URL http://mymachine.mydomain.mycompany.com, but not when I access it by http://sitename.

      I've tried setting the domain in the cookie to 'mymachine' and also 'mydomain.mycompany.com' and 'mymachine.mydomain.mycompany.com' but to no avail...

      How do I set a cookie for users who don't want to specify the entire URL?

      A

        So it seems you've made use of 'cookie domain'. Read up CGI.pm's docs for waht that does (actually it denotes to what server the browser shall be allowed to send that cookie) and how to use it.

        Have a nice day
        All decision is left to your taste