[pubcookie-dev] safari problems

[Nathan Dors]

Interesting, isn't it. Safari (v60) seems to work
for me sometimes, per Sly's response, but not always.
It appears to be dependent on the URL you use
initially to go to the application:

   http://example.edu/testapp    [no ssl, no slash]
   http://example.edu/testapp/   [no ssl, slash]
   https://example.edu/testapp   [ssl, no slash]
*  https://example.edu/testapp/  [ssl, slash]

Only in the last (*) case, where the initial URL
matches the true target URL does it bounce me back
to the login server again. (Note: we may be missing
some template files in the beta3 release that would
normally result from the login server in this case.)

I've looked at this briefly now, thinking that it
may be a bug in Safari's handling of anti-caching
headers like Cache-Control and Pragma. But it seems
to be making a real request back to the application
server with the granting cookie after I log in. It's
definitely odd. It would probably help to watch the
entire HTTP dialogue. Unfortunately, my favorite
debugging tool, Achilles, doesn't like the way
Safari negotiates the SSL connection. Does anyone
have a good tool for OS X that can peer in on HTTPS
traffic?

-Nathan