[help-cgicc] question about expires vs max-age

[Jim Hull]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My apologies if this has already been brought up. In the course of bug
testing some of our cgi's designed with cgicc, we found that IE would not
store a perm cookie created by cgicc, and only keep it session specific. I
tracked down the issue to be in that cgicc sends Max-Age and not expires.
I understand the differences between the two, and actually mozilla seems
to do the right thing. IE, however does not. I have since wrote my own
cookie header for us to use that sets 'expires' and now IE is fine. I
suppose my question is, why does IE not store a cookie when Max-Age is
used, and why does cgicc not have a 'setExpires' method to HTTPCookie to
allow browser compatability ?

I am not subscribed to the mailing list, so I would appreciate it if you
would leave me on the cc :) thanks.


                        Jim

- -----
Without a functioning immune system you get a disease called death.

                                -  Professor Richard Boyd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD4DBQE+tswUdygyS8O4zQ0RAnPIAJIDP+y1/Hy9rMRI/3uhqHDbARqRAJ9/2R0l
njpaUNeXl1qVL3aIK+NY/w==
=ZKBT
-----END PGP SIGNATURE-----