Hyatt mentioned today that this Maciej Stachowiak, who I’m guessing is another Safari developer at Apple (at least he probably worked there when this was posted), just fixed the cookie bug I keep complaining about! Apparently previously Safari was handling cookies according to the old Netscape cookie spec, instead of by the RFC, which states that the cookie path “Defaults to the path of the request URL that generated the Set-Cookie response, up to, but not including, the right-most /.”
I just hope he didn’t make it so a cookie set at /foo/bar.php also gets set at /. (should be /foo .)
UPDATE 3/17: Of course he didn’t. See the comments.
Maciej Stachowiak
A cookie set at /foo/bar.php will get a path of /foo by default, as you say. (Note that this is not the RFC behavior either - the RFC calls for /foo/. And no one implements the RFC, either server or client side, as far as I can tell).
steve
All of us running code with sloppy cookie handling thank you. Now we just have to wait for the version with your fix to get leaked!
Pleae leave a comment!