I've recently been porting a Chrome extension to Safari, and encountered this kind of error (bug, feature, etc.)
So, in global page i have a XMLHTTP request to a secure page which is available only after you login.
Example:
it seems that global page somewhat has it's own cookies, so a secure page thinks i'm new
ps: in Chrome i can load that page and it thinks i'm acting on behalf of logged in user, so i guess there are some restrictions in Safari
pps: i heard there's a Block third-party cookies option in Safari, but even if i checked it to "Never block" it still doesn't work
I had that problem with Safari 5.1.2 for Windows, but after upgrading to the current version (5.1.7) the problem disappeared. Maybe they fixed it on some intermediate version. It is also working for me on a Safari 5.1.3 for Mac OS X.