Delete after X minutes not working
-
Are you checking the Privacy tab in Safari?
If so, Safari doesn't reflect the true current state of cookies when deleted by an outside program. (i.e…. Cookie)
It will still list all cache cookies and databases. History display's the same behaviour.
You can test this by restarting Safari, which will force it to update its cookie references.If it's not this that you're seeing. Try toggling the Timer OFF/ON to see if that helps.
-
Looks like there may still be a problem. It works intermittently. 3.0.18 version, Macbook Pro, Mountain Lion, Safari (everything up-to-date). See these screenshots taken while I was on a single web page for 30 minutes.
They show a 5 min delete period and 247 cookies. 12 are Favorites. -
I also find that this seems to work sometimes but not others.
I understand I cannot verify it by looking in Safari, so I try to validate by seeing if my cookie set by a site to save a login sessions stays or goes.
Is there a better way we can do this so the developer can get the best possible information to work from?
Best
soren -
I am on 10.8.4.
What I have found is that if I have the Cookie window open (as opposed to just having the Cookie icon in the menu bar), it works fine. Cookies disappear after a minute as planned.
However, if that window is closed, it seems to forget about deleting them..
Different question (maybe): I have 8 databases listed that I cannot delete. They belong to extensions from Chrome and Safari. Is that normal? They are not favorites, but "Remove" does nothing.
Best
Soren -
Cookie is working fine on Mavericks DP5, I haven't yet tested DP6, but I assume it will still work just fine.
The Extensions are "locked" by checking the preference (on the Preferences tab, - these are all Extension settings, and removing them may cause issues with the relevant extension):
"Treat all Browser Extensions as Favourites" -
This is still happening. It runs for a while, then quits deleting after X minutes. Mine is set to 5 mins.
I can get it to work again by deleting the cookie .plist file.Please look into this because it is basically making Cookie no longer useful. It is a wonderful app, when it is working right. I need it to work because I never close Safari. I am running on Mavericks.
-
I too am having the same issue with Safari on Mavericks. Actually I have noticed this as a problem for quite some time in previous OS and cookie versions. I am running the current 3.0.20 cookie.
Also to let you know. When bringing cookie to foremost app sometimes the cookie list will not refresh. I actually have to highlight a browser choice and then all the sudden the list of cookies will refresh.
-
I think "Delete after X minutes" is not working because deletion with [u]running Safari[/u] is not working.
My Test:
- open url: http://www.bvg.de/index.php/en/index.html
- enter in fields:
From: "foo"
To: "bar" - Hit Search
- open url: http://www.bvg.de/index.php/en/index.html
Verify: Your last search
From: foo
To: bar
So the site remembers my last search, I guess by setting a cookie.
-
Close the tab, but keep safari open (have a another tab open)
-
Now go into Cookie App or via cookie menu item drop down and delete all unwanted cookies (checked settings option: unwanted are all non favorites).
-
open url: http://www.bvg.de/index.php/en/index.html
Verify: "Your last search"
From: foo
To: bar
expected: No display of last search
Now go into Safari settings-->privacy delete specific cookie "bvg.de"
- open url: http://www.bvg.de/index.php/en/index.html
Verify: No display of last search
So the site cannot remember my last search, cause I deleted the cookie via Safaris builtin cookie management.
In contrast: Cookie.app is not able to delete that cookie, even if I wait some hours. Safari seems to cache the cookie and Cookie.app is not able to edit that cache. Don't take me wrong, but that would be exactly that what I would expect from Cookie.app it should do. Might not be the fault of Cookie.app cause it uses the NSHTTPCookieStorage. But in the end I would expect when deleting a cookie in NSHTTPCookieStorage, that Safari invalidates it in its cache. Maybe the SweetP developers can push Apple to look at this issue, or find another hack that does manage the Safari cookie cache issue.
My System:
OSX 10.9.1
Cookie 3.0.26
Safari 7.0.1
A bigger safari plugin to mention: Glims 1.0.42Can anyone reproduce this?
@SweetP can you?Cheers Pete
-
Interesting:
I have found another site, where the test above reproducible deletes the cookies successfully.
http://sweetpproductions.com/support
Instead submitting a search, I simply logged in and observed, if the deletion of cookies with Cookie.app invalidates my login. And indeed it does.
In contrast to sweetpproductions.com a login test with Facebook, keeps me logged in after deletion with Cookie.app.
So what is the difference between the sweetpproductions.com cookie and the bvg.de/facebook.com cookie?
Any thoughts?Cheers
Pete -
Sorry Russell,
your answer was a bit to short for me. But you wrote it was just a quick look, so I guess you will come back. However, your short answer left me with the following questions:Do you mean to remove the browser cache with Cookie.app? That option is already checked here. And also I already tried deleting the cache separately via the menu drop down. The bvg.de site still knows what I have searched before.
And what about Facebook? I am not able to invalidate a login session with Cookie.app. Can you test this?
Another Question: Is it possible to delete Safaris cookies from within a Safari Extension? The idea would be to delete Safaris cookies from within Safari, not just via NSHTTPCookieStorage, which does not delete cookies if Safari keeps running, at least in some cases (bvg.de/facebook).
If that is possible, one could create a Safari extension, that could communicate with Cookie.app and then do the delete job correctly. But I think I am two steps ahead. There are still some questions left open from my post before. Can you please reproduce all 3 of my tests bvg.de, sweetproductions.com and facebook.com?What is a "cache cookie"? (I have not googled this so far.)
Regards Pete
EDIT:
I repeated the test on sweetproductions.com. Right now I am logged in, but the cookie is not visible in Cookie.app. And also "delete unwanted" does not invalidate the login. I think to get this situation, one has to keep Safari running longer. Personally I keep Safari and my osx-session open for days or even weeks. I just close the lid of my mac-laptop when I stop working each day.
EDIT2:
Restarting Cookie.app helped in that situation. After restart of Cookie.app the before empty cookie listing was full of cookies again, which then could be deleted. That invalidated the login on sweetproductions.com. I did not hinder bvg.de to remember my last search. Actually bvg.de is not listed in Cookie.app but in Safari->Settings->Privacy->cookielist I can see it. -
Hmm ok,
it is really sad to see, that session cookies can be used to track users like me, that do not often close the browser. I tested this with google chrome, same there.
I (quickly) searched the web for options to use APIs or privat functions to edit those RAM-only session cookies. I had no luck.Do you think SIMBL could help in the Safari case?
Besides that, I could imagine a browser extension which greasemonkey-like adds user-code (javascript) to all open sites and deletes the cookie within the site context by using standard web methods.
I understand, why you and Cookie.app cannot address this issue atm. But it would be really cool if such happens somewhen in future. However, I guess the browser companies have to be convinced first, that this is an issue.
Best wishes,
Pete
