Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]
-
First off, I'm on to Mojave 10.14.5 Developer Beta 1 (18F96h) that installs Safari 12.1.1, and I'm still experiencing the same thing with HSTS cookies.
I'm not sure how to determine if Safari is regenerating the HSTS cookies or Cookie is not ever deleting them. Maybe I'm being daft, and if so, I apologize.
Hereβs what Iβm doing. Before I close Safari, but after I use Cookie 5.9.6 to delete tracking cookies and non-favorites, these HSTS cookies are there under Manage Website Data. I then close the browser and use Cookie to remove the Cache. Remove Now is greyed out for Cache, Tracking Cookies and Non-Favorites. I then reopen Safari, and before I open any tabs, I check under Manage Website Data, and the HSTS Policy cookies are there. So how do I know if Cookie deleted them and Safari regenerated them or if Cookie never deleted them at all? Either way, they are still there and I canβt rely on Cookie to manage them for me.
It's probably no huge deal, but I would feel better knowing that I don't have some bit of info stored on my computer that could be theoretically used in some way by the likes of google, facebook, pinterest, etc. If I have to remember to deal with this manually, it won't be the end of the world. I will remain a proud Cookie user, and continue to use your other great products like SessionRestore and DesktopUtility. I'm a big fan of your work. Cheers!
-
I see the problem.
do you have the extra scripts installed?
if so, replace the contents ofclearSafariCache.shwith this:
#!/bin/sh
find /private/var/folders \! -name "*SafariTechnologyPreview*" -name "*com.apple.Safari*" -exec rm -r {} \; 2>/dev/null && /usr/bin/killall -KILL nsurlstoraged -
alternatively, if you could update to the Beta I just released, and let me know if it works for you that would be great:
https://sweetpproductions.com/products/cookie5/CookieBeta.dmg -
-
I'm sorry to report that I tried doing both...modifying the shell script file and then installing the beta, but neither succeeded in removing the HSTS Policy items.
P.S. I forgot to mention earlier that I also use ColorWell! Good stuff!
-
@SweetP said in Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]:
you still need to restart Safari after removing the cache. did you also do that?
Yes. As I said, I run Cookie before I close the browser, then check Manage Website Data and note that the HSTS items are there. I then close the browser, run Cookie again so that Remove Now is greyed-out out for Tracking Cookies, Non-Favorites and Cache, and then re-open the browser. Before opening any tabs, I check Manage Website Data, and note that the same pesky HSTS items are still there.
-
ok,
can you try changing the contents of the file
clearSafariCacheMojave.shto this:
#!/bin/sh/usr/bin/killall -KILL nsurlstoraged
find /private/var/folders \! -name "*SafariTechnologyPreview*" -name "*com.apple.Safari*" -exec rm -r {} \; 2>/dev/nullthen quit Safari and clear the cache
-
ok,
can you try changing the contents of the file
clearSafariCacheMojave.shto this:
#!/bin/sh/usr/bin/killall -KILL nsurlstoraged
find /private/var/folders \! -name "*SafariTechnologyPreview*" -name "*com.apple.Safari*" -exec rm -r {} \; 2>/dev/nullthen quit Safari and clear the cache
@SweetP said in Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]:
ok,
can you try changing the contents of the file
clearSafariCacheMojave.shto this:
#!/bin/sh/usr/bin/killall -KILL nsurlstoraged
find /private/var/folders \! -name "*SafariTechnologyPreview*" -name "*com.apple.Safari*" -exec rm -r {} \; 2>/dev/nullthen quit Safari and clear the cache
Fantastic, the HSTS items are gone!
Prior to getting your last message, I decided to delete all my Favorites and close all pinned tabs to eliminate those things from consideration. One of my Favorites was netflix.com, and prior to making the change to the shell script file, the only things under Manage Website Data were 5 HSTS items and a netflix.com Media Keys item. The Media Keys item is still there after the change to the shell script fyi.
-
@SweetP said in Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]:
nice one,
Ill get an official update sorted out
Super! Thanks for getting to the bottom of it!
Cheers!As an aside, I used SessionRestore to get all my pinned tabs back. Something for the wish list would be the ability to restore the tabs to their pinned state. Another great feature would be a way to bulk unpin and/or close pinned Safari tabs. Are these types of things programmatically possible, or does Apple preclude this type of tab management?
-
@SweetP said in Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]:
nice one,
Ill get an official update sorted out
Super! Thanks for getting to the bottom of it!
Cheers!As an aside, I used SessionRestore to get all my pinned tabs back. Something for the wish list would be the ability to restore the tabs to their pinned state. Another great feature would be a way to bulk unpin and/or close pinned Safari tabs. Are these types of things programmatically possible, or does Apple preclude this type of tab management?
@kitated said in Safari HSTS cookies not being deleted [Cookie v5.9.6, Safari v12.1 (14607.1.40.1.4), macOS 10.14.4 Beta (18E220a)]:
As an aside, I used SessionRestore to get all my pinned tabs back. Something for the wish list would be the ability to restore the tabs to their pinned state. Another great feature would be a way to bulk unpin and/or close pinned Safari tabs. Are these types of things programmatically possible, or does Apple preclude this type of tab management?
To be honest, theres no way of updating SessionRestore anymore...
The new Safari Extensions API's are worse than useless for anything other than adblockers... the old APIs also never had any hooks for knowing if a tab was pinned or not, otherwise I would have supported that years ago
