Bug 121197

Summary:	Fails to handle dyndns.org cookies
Product:	[Applications] konqueror	Reporter:	Georg Wittenburg <georg.wittenburg>
Component:	kcookiejar	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Georg Wittenburg 2006-02-02 01:38:37 UTC

Version:            (using KDE KDE 3.5.1)
Installed from:    Debian testing/unstable Packages

Hi!

When logging into dyndns.org with default policy set to reject and a site policy set to "accept", the login seems to succeed, but when trying to navigate the forms I get immediately bumped back to the login screen.

When setting the default policy to "ask for confirmation" everything works fine, but no questions are asked at any point.

Given that no questions are asked, I'd expect the behaviour of ((default policy := reject) && (site policy of dyndns.org := accept)) to match the behaviour of ((default policy := ask) && (site policy of dyndns.org := accept)). However, the behaviour differs as described above.

Thanks for looking into this.

   Georg

Comment 1 Eric Kjeldergaard 2006-09-01 16:24:58 UTC

This includes a solution ;)  The domain for dyndns.org cookies is .www.dyndns.org and using that instead of .dyndns.org.  So some notable behaviours:

With policy set to "Ask" this occurs:  I go to dyndns.org and login where Konqy prompts about the cookies from .dyndns.org.  Clicking on "Details" shows that the domain of the cookie(s) is .www.dyndns.org .  Accepting causes Konqy to add the ".dyndns.org Accept" line.  Everything works fine.
I then set the policy to "Reject".  The ".dyndns.org Accept" line is still in my policy (removing/readding it doesn't change things).  Trying to modify a form results in dyndns.org's login page being displayed and a message regarding cookies is at the bottom.  This would be everything not working fine.  I then add ".www.dyndns.org Accept" to my rules.  After adding that line, everything works as expected.

Comment 2 Dawit Alemayehu 2007-09-03 09:56:40 UTC


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