A cookie named, for instance, "site/sub", will not properly save. Change the name to "site-sub" and it will register properly. In my specific case, the cookie isn't secure, and is set to expire one month from set time. The slash-named cookie was working several several nightlies ago (and still works in other mainstream browsers). Currently broken in r40023.
Does it also work in Safari? Cookie parsing is not something that WebKit handles, so if this broke recently it likely broke as the result of installing a software update, and should also be broken in stock Safari.
I will craft a generic, public test case this afternoon and post my results this evening. Thanks for the idea.
http://thadenpierce.org/testcookie.php Load the page, then refresh. If the cookie is set, it should report a '1'. Works in latest Firefox, but broken in Webkit nightly *and* Safari. Good call. So, then. To whom should I submit this one?
You should file a bug report at <http://bugreport.apple.com/>.
Thank you.