in reply to Re: Re: Re: Warn people who have perlmonks in a URL?
in thread Warn people who have perlmonks in a URL?
No it doesn't.
Mea culpa. I should know better than to test on just one (lame) platform before making a statement like that. It was, unfortunately, the only platform I had immediately available. Sigh.
Uncle Bill seems to have done it his own way, once again.
I agree that the behavior seems to be broken and I'm anything but a defender of the evil empire, but I bet Hanlon's Razor applies in this case. It looks like it may have originated with a poorly chosen example in the original Netscape cookie spec. The example given is:
A domain attribute of "acme.com" would match host names "anvil.acme.com" as well as "shipping.crate.acme.com".That example is not valid, however, according to the spec it appears in. The very next paragraph begins:
Only hosts within the specified domain can set a cookie for a domain and domains must have at least two (2) or three (3) periods in them to prevent domains of the form: ".com", ".edu", and "va.us".And that indicates that "acme.com" is not a valid cookie domain attribute.
-sauoq "My two cents aren't worth a dime.";
|
|---|