Safari may well be abiding by its preference setting to not accept cookies while other WebKit based clients may not have such a setting and be setting cookies in there. If it doesn't grow, then start reading your email (especially if you have the loading of remote images enabled in Mail.app), or use 3rd party software, and watch to see if cookies suddenly start showing up. Just clear your cookie store and watch it as you surf and do nothing else.
#Enable cookies safari 5.1 code
Since code doesn't normally do things for "no rhyme or reason" I suspect that affected users may be able to test this out easily.
#Enable cookies safari 5.1 mac
See, even if Safari is abiding by the setting to not accept cookies, that may not be the case with other applications such as Mail.app, the Mac App Store, 3rd-party software, and others.
#Enable cookies safari 5.1 upgrade
(Did you like how they sneakily increased the price of the upgrade by nearly 3.5% with that easily-overlooked 99 cents – so much for the downward pressure on prices exerted by the App Store.)Īssuming that someone took the time to see that cookies that they tested were not being set in Safari when purposely browsing and looking for them, it is not unlikely or impossible that what is occurring is that the cookies are being set by other WebKit-based clients.
If so, that's not an extra $40 but an extra $30. I can't see why it's too much to ask or expect OS vendors to support officially the reinstallation of their OS from scratch on a new disk, without going through "install the old one and go back online" hoops.Īs for numeracy, I too have heard that the USB sticks will be $60. The fact that there's a workaround is not enough. On the literacy front, I'm looking for confirmation that Apple _officially endorses_ standalone installation. But only just, since I'm rarely delighted to be addressed as both a prick and a fool.) But you, Sir, are both illiterate and innumerate, characteristics which cannot. In that respect, it can at least be adopted or shrugged off at will. Interestingly (or perhaps not), pretension is an attitude. It’s easy: just visit Apple’s official OS X Feedback page.įollow on Twitter for the latest computer security news.įollow on Instagram for exclusive pics, gifs, vids and LOLs! So, if you’re a 10.6.8 user, why not report this bug to Apple? I did. Wrongly managed, they represent a potentially significant privacy risk, since cookies are used for a variety of tasks from post-login session authentication to long-term user identification.
You need to be able to rely on your browser to do the right thing with cookies. (As I mentioned before, I’m waiting until I can purchase an official, bootable, installable distribution of Lion before I’ll go near it.) Nevertheless, this is cold comfort to those of us who can’t, or won’t, spend the $30 needed to upgrade to Lion. Apple seems to have fixed the underlying fault, since Block cookies: always works as you would expect.
Interestingly, this bug does not seem to appear on OS X 10.7, better known as Lion. To view cookies in 5.1 you need to use Develop|Show Web Inspector|Resources|Cookies.) (Note that the Privacy tab of the Preferences pane no longer shows you the actual cookies which are set, as it did in Safari 5.0.5. In Safari 5.1, Apple’s terminology does an about-face, so that you need to Block cookies: always – a command which somehow sounds even stronger than never allowing them – but the bug persists, at least on OS X 10.6.8. There’s no obvious rhyme or reason to the cookies which sneak through when they aren’t supposed to – in my tests (I visited /startpage, and ) a mixture of session, short-term and long-life cookies appeared in the mix. Some, but not all, cookies, are stored and transmitted by the browser, even when you’ve insisted that Safari allow no cookies at all. Upgrade to OS X 10.6.8, however, and even though the Safari version and build number remain the same, the browser’s behaviour does not. Cookies would neither be stored nor transmitted by the browser. On OS X 10.6.7, setting the Safari 5.05 (build 6533.21.1) option Accept cookies: Never would do just that. It’s therefore rather a worrying sort of bug when a browser doesn’t deal with cookies precisely as you’d expect. Websites use cookies to keep track of your browsing during and between sessions, so that cookies and browsing privacy go hand-in-hand. The problem is that even if you tell Safari to block all cookies, it doesn’t. This issue has also popped up on Apple’s own Support Communities forum. For the past few weeks, it looks as though Safari on OS X 10.6.8 has not been handling website cookies correctly, as a Naked Security reader from Toronto pointed out recently.
0 kommentar(er)
