From: Philipp Hanes <[EMAIL PROTECTED]> Date: Tue, 28 Jun 2005 17:33:30 -0400
> Here is the code I started with and have reverted back to: > ---------------------------------------------- > my $cookie = "Set-Cookie: " . > "$COOKIENAME=$cookieContent; " . > "Host=www.wpi.edu; " . > "expires=+1h\n"; > print $cookie; > ---------------------------------------------- One thing I notice is that the RFC mentions "Domain" and not "Host" http://www.faqs.org/rfcs/rfc2965.html Also, "Version" is required, according to that document. It's been a long time since I built cookies by hand, but perhaps the cookie is being rejected because it does not conform? You may have the right idea, though possibly the wrong standard. RFC2965 uses "Set-Cookie2:" instead of "Set-Cookie:", and has a "Max-Age" keyword that specifies relative time instead of "Expires". On the other hand, the original Netscape cookie spec (http://wp.netscape.com/newsref/std/cookie_spec.html) defines "Expires", but with an absolute date value: The date string is formatted as: Wdy, DD-Mon-YYYY HH:MM:SS GMT This is based on RFC 822, RFC 850, RFC 1036, and RFC 1123, with the variations that the only legal time zone is GMT and the separators between the elements of the date must be dashes. So maybe try (a) "Set-Cookie:" with an absolute "Expires" time, or (b) "Set-Cookie2:" with "max-age=3600"? -- Bob Rogers http://rgrjr.dyndns.org/ _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
