Bug 182806

Summary:	Site-specific cookie rejection policy is forgotten
Product:	[Applications] konqueror	Reporter:	Maarten ter Huurne <maarten>
Component:	kcookiejar	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adawit, vornne, zahl
Priority:	NOR
Version:	4.2.0
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maarten ter Huurne 2009-02-02 00:38:46 UTC

Version:           unknown (using 4.2.00 (KDE 4.2.0) "release 82.1", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.25.20-0.1-default

I have the default cookie policy set to "ask". I follow several RSS/Atom feeds using Akregator and some of them try to set cookies; when I get the cookie acceptance dialog for those sites I answer "reject".

The problem is that after some time, I get the prompt again for the same site. I'm not sure exactly how long, but approximately after one week, so a lot longer than the refresh interval of the feed (which is typically 30 minutes).

I think Konqueror has the same problem, but unlike for Akregator, I'm not 100% sure I've seen a prompt for the same site twice in Konqueror. Since it seems the problem is located in shared code that deals with cookies, I filed this bug on kio/http, although I'm not sure if the KIO slave actually manages cookies or whether that is a separate module. Please reassign if I guessed wrong.

I've had this problem in KDE 4.1 and in 4.2.0 it's still present. I haven't run 4.0. I did run 3.5 for a long time and never got this problem then.

I have Akregator running all the time (inside Kontact) and also have lots of Konqueror windows open. Maybe there is some kind of race condition between different processes trying to access the cookie policy administration?

Comment 1 Maarten ter Huurne 2009-02-06 03:15:38 UTC

Today I noticed that some cookie policies were forgotten shortly after I opened a URL from Konversation. The Konversation version I'm using is still using the libs from KDE 3.5 and also opens the Konqueror from KDE3 when I click a URL. But if I open Konqueror from the plasma panel, it's always the KDE4 Konqueror. Akregator is also the KDE4 version.

Is it possible that the cookie policy administration of KDE3 and KDE4 are somehow conflicting?

Comment 2 Maarten ter Huurne 2009-02-06 03:35:40 UTC

I wrote "some cookie policies were forgotten" in the previous comment. Closer inspection (Konqueror's configuration dialog) shows that only a single one survived, all others were lost.

Comment 3 Steven Schwartfeger 2009-02-10 03:46:09 UTC

This might not be the same problem that I have, but I will add it anyway.

I set the default policy to "Reject all"; then when I want to enable them for a site I change to "Ask", click "Allow for this domain", then set back to "Reject all". It works until I close and reopen konqueror, after that it seems to have forgotten it, as in this report - if I look at the site policy settings, the whole domain has been added (for example "kde.org"), if I change it to the exact site ("bugs.kde.org") it works.

To summarise, clicking "Allow for this domain" adds a rule for the whole domain; but that doesn't work, only rules for a full site name do.

Comment 4 Maarten ter Huurne 2009-03-19 13:28:14 UTC

Today I noticed that only the cookie policy is forgotten, not the cookies themselves: I was logged in to a forum and when I refreshed the page, Konqueror asked whether I wanted to accept cookies from that site, but I was still logged in (which is implemented with a cookie).

Comment 5 A. Spehr 2009-03-21 19:47:53 UTC

Try what is in bug #183720 and see if that helps.

Comment 6 David Faure 2009-03-25 11:36:22 UTC

#3 is the Qt-4.4 bug. The rule for the whole domain should be ".kde.org", but Qt-4.4 turned that into "kde.org". That part is fixed with Qt-4.5.

Comment 7 Dawit Alemayehu 2010-08-18 10:55:48 UTC

Most probably this report is caused by the same issue reported in bug# 196975. Can you please read that bug report and let us know if that is your issue ? Thanks.

Comment 8 Maarten ter Huurne 2010-08-18 17:21:30 UTC

Most likely it is indeed that same bug. It would explain things like all but one policy being forgotten (that one being the one filtered and then modified).

I'll close this bug and reopen it if the problem still occurs with 4.5.1.

*** This bug has been marked as a duplicate of bug 196975 ***