1. Diigolet uses cookies authroization if available (available means that 3rd party cookies are allowed) 2. If cookies are not available, diigolet gracefully falls back to http authorization. 3. The advantage of cookies auth over http auth is that your sign in status can be remembered so you don't have to type your username and password the next time you open the browser.
In Safari, Diigolet works *without* third party cookies and *without* re-entering credentials; browser can be quit then re-opened and Diigolet works immediately.
Persistence of authority without third party cookies, and through multiple browsing sessions, is most easily tested using the Guest Account in Mac OS X 10.5.x.
The problem was finally solved.
1. Diigolet uses cookies authroization if available (available means that 3rd party cookies are allowed)
2. If cookies are not available, diigolet gracefully falls back to http authorization.
3. The advantage of cookies auth over http auth is that your sign in status can be remembered so you don't have to type your username and password the next time you open the browser.
Key to this is:
> Use https://secure.diigo.com/sign-in to sign in
Persistence of authority without third party cookies, and through multiple browsing sessions, is most easily tested using the Guest Account in Mac OS X 10.5.x.
To Top