The \n has two roles. First, \n acts as a line feed character. Second, it acts as a buffer release mechanism. In some systems (i.e. IE) the \n is assumed and automatically inserted, while in others the \n needs to be specifically added. This is why the \n can be critical.
Tal Cohen -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bob Rogers Sent: Tuesday, August 31, 2004 7:21 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Boston.pm] Setting cookies in different browsers From: "Alex Brelsfoard" <[EMAIL PROTECTED]> Date: Tue, 31 Aug 2004 14:26:35 -0500 (CDT) . . . The advice you guys gave me did indeed fix the problem for mozilla (haven't tested Safari yet) I really just needed teh \n Thanks much! So I guess the fact that it "... works beautifully in IE" means that IE happily accepts cookies with seriously malformed 'expires' attributes. (Not to mention IE's notorious disregard for 'Content-Type' headers, or the lack thereof.) BTW, isn't it supposed to be "\r\n"? Or is there some server magic that does the right thing in this particular case? -- Bob Rogers http://rgrjr.dyndns.org/ _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
