Bug 149881

Summary:	akregator does not respect my cookie rules ( management )
Product:	[Applications] akregator	Reporter:	Philippe ROUBACH <philippe.roubach>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	greg_g, kdenis
Priority:	NOR
Version:	4.12
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Philippe ROUBACH 2007-09-15 08:24:39 UTC

Version:           1.2.7 (using KDE 3.5.7, compiled sources)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.17-15mdv

i have cookie rules in konqueror according to delete all cookies when i close konqueror.

when akregator makes an update of the list of items or perhaps when i click on an item to get it (i don't know how akregator works) the result is i have cookies in konqueror and these cookies are not deleted.

it would be a good thing to have the ability to choose between
akregator settings or konqueror settings

Comment 1 Gregorio Guidi 2009-02-22 12:46:45 UTC

I happen to see this bug. Actually akregator does use the konqueror cookie settings, what happens is that cookies should expire at the end of the akregator session, but live until the end of the KDE session instead.

Normally, the removal of session cookies is triggered when the associated window is closed: see kdelibs/kioslave/http/kcookiejar/kcookieserver.cpp:105-106

connect(this, SIGNAL(windowUnregistered(qlonglong)),
        this, SLOT(slotDeleteSessionCookies(qlonglong)));

However, the HTML-part embedded into akregator does not set a window-id when exchanging cookies (the "window-id" property of the job is set to zero).
See kdelibs/kio/kio/job.cpp:416-419

if (ui() && ui()->window())
 {
     m_outgoingMetaData.insert("window-id", QString::number((long)ui()->window()->winId()));
 }

So, if I understand it correctly, embedded HTML -> no ui() -> no window-id -> no removal of cookies.

Comment 2 Philippe ROUBACH 2014-01-12 16:18:08 UTC

is there any plan to rewrite akregator ?

 since i use it , about 6 years , bugs are not fixed .

Comment 3 Denis Kurz 2016-09-24 19:39:57 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Philippe ROUBACH 2016-09-26 09:54:55 UTC

i use no more konqueror as akregator browser

Comment 5 Denis Kurz 2017-01-07 23:46:20 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.