Normally i keep my cookiejar policy to "Ask for confirmation", then I went to gmail, confirmed all the domains it was popping up and then gmail was working. After inspecting the kioslave code I realized that the general policy applies only if there is no present policy for the domain already, so setting it to "reject all cookies" should still accept the gmail cookies I need. In fact what happens is that a redirect loop is detected and the page is not loaded when I set it on "Reject cookies", but it works perfectly, and nothing pops up when i set the general policy to ask for confirmation. Other websites such as plus.google.com, facebook.com and others, work fine with the reject cookies policy Reproducible: Always Steps to Reproduce: 1. Set general cookie policy to ask for confirmation 2. Open gmail and facebook, and confirm all the cookies 3. Set general policy to reject 4. Open gmail and facebook again Actual Results: gmail page is not loaded, and an error is shown, while facebook works Expected Results: Both should work.
So what do your domain specific policies look like?
accept for gmail
(In reply to comment #2) > accept for gmail If you mean accept for "gmail.com", then it is useless because all the cookies for gmail.com come from "mail.google.com", "accounts.google.com" and "accounts.youtube.com". At least that is what I see here ; so unless you accept for the domain ".google.com" and probably ".youtube.com" or specifically for the hosts listed above, what you are trying to do above will not work.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!