Bug 255591 - facebook doesn't remember rekonq
Summary: facebook doesn't remember rekonq
Status: RESOLVED WORKSFORME
Alias: None
Product: rekonq
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.6.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Andrea Diamantini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-29 15:57 UTC by Martin Tlustos
Modified: 2011-03-21 22:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2010-10-29 15:57:18 UTC
Version:           0.6.1 (using KDE 4.5.2) 
OS:                Linux

I have enabled a security feature on facebook which alerts me if facebook is approached from a new/unknown application (like a cellphone, a new browser etc.), so that I can check whether someone else has hacked into my account. Now, every time I connect to facebook using rekonq, it alerts me anew, although I click the "don't ask on this computer" button...
Maybe something can be done about it?

Reproducible: Always




OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc
Comment 1 Martin Tlustos 2010-11-09 16:07:18 UTC
As it seems rekonq by default rejects cookies, even when you select accepting them by defaul. I had to change the policy to ask me every time and then choose accept the cookies. Now it works...
Comment 2 Alexander van Loon 2011-01-15 16:02:55 UTC
I’m having this problem as well, a related problem to be exact. Firefox would always restore the Facebook start page for me and rekonq does not because it forgets the login. If I’m correct this is intended behavior in rekonq according to the comments in bug #256319. If the cookie policy is what is causing this bug, then maybe we should file a new bug, because rekonq’s default policy isn’t good considering that other browsers do remember logins.
Comment 3 Felix Rohrbach 2011-02-12 20:53:27 UTC
Did you enable the option "Configure rekonq->Network->Cookies->Treat all cookies as session cookies"? Somehow a group of users had this option enabled without knowing about it causing problems like this one...