Konqueror resets cookie default policy
Jump to:
Project: | Linux software |
Component: | Code |
Category: | bug report |
Priority: | normal |
Assigned: | Unassigned |
Status: | closed |
Related pages: | #85: Konqueror |
Description
In konqueror > settings > Configure Konqueror > web browsing > cookies > default policy, I usually set the policy as "ask for confirmation".
However, it seems that in certain circumstances (reboot?) the setting is lost. Once, I found it as "reject all cookies" and found dozens and dozens of unwanted cookies which I deleted one by one. Another time, it was somehow reset to "reject all cookies" and I found about it rapidly because I couldn't log in my own sites.
This has happened many time with several users on my machine.
Comments
#1
Here is a list of konqueror / cookie related issues:
https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=a...
#2
Bug 232861 - Konqueror doesn't respect cookie site policies
https://bugs.kde.org/show_bug.cgi?id=232861
#3
Bug 187792 - cookie Ask setting ignored
https://bugs.kde.org/show_bug.cgi?id=187792
fixed in SVN on 2009-12-18
I'm still using Kubuntu 9.10. Hopefully this will be fixed in Kubuntu 10.04.
#4
Bug 86701 - cookie policies are ignored
https://bugs.kde.org/show_bug.cgi?id=86701
not the same, because the policies are followed... it's just that they are reset.
#5
Bug 80630 - Konqueror HTML Settings tool should allow permanent change of cookie policy
https://bugs.kde.org/show_bug.cgi?id=80630
#6
I asked here:
http://kubuntuforums.net/forums/index.php?topic=3111896.0
#7
Ah! I think I know what triggers the bug.
When a dialog pop up asks for a policy for a specific domain, setting the policy for the domain changes the global policy instead!!
#8
I think the bug was BTCATM (Between the chair and the monitor). I simply chose the wrong option when the dialog pop up came up, asking for how to handle cookies from a specific domain. I chose "all cookies" instead of "all cookies from this domain"!!
I'll pay more attention next time and if I find there is a legitimate bug somewhere, I'll update this ticket.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.