Closed (duplicate)
Project:
Boost
Version:
7.x-1.0-beta1
Component:
Cookie issues
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Aug 2012 at 17:05 UTC
Updated:
25 Sep 2012 at 16:54 UTC
1) Load site in Safari as anonymous (boost sends cached page with login boxes)
2) Log in (successful session message in log, but boost returns cached page with login boxes)
3) Refresh in Safari (Boost continues sending cached page)
4) Load another page of the site in Safari--drupal correctly sends logged-in page
I'm sure this is actually a bug in Safari, but how do we work around this? This happens in Safari on Windows and on iPhone. My iPhone users think they can't log in to the site.
Comments
Comment #1
skinSame things with Chrome and other browser.
Comment #2
bgm commentedCan you test with the latest dev? This bug should be fixed.
Comment #3
bgm commentedif I recall correctly, this was the issue with the fix: #1616356: Boost Module problem in logged in user
Comment #4
skinThanks, I'm going to instal the latest Dev and make some tests, I'll report here if I solve the problem.
Comment #5
skinWith the latest dev everything works smooth.
Thanks
Comment #6
bgm commentedThanks for the feedback. I needed more feedback before releasing a new beta :)
Closing issue.
Comment #7
fibigerg commentedHello,
I have a similar problem as above. I'm using http://drupal.org/project/fboauth module, i like the module. (I think it's the best fb login module.) There is a problem with one click login on my page. I have a FB login link on homepage, user is logged in when he clicks the link. That works very well. But until hitting CTRL+F5, the cached pages are served to the user. Can you help me fix the problem?
Is there any hook, i should run on FB login to stop loading cached pages? After normal log in with form there is no problem and non-cached pages are loading.
Thank you!
Comment #8
fibigerg commentedI solved the problem, it was acctualy quite easy.
Just added boost_set_cookie() call to to function fboauth_login_user. It seems working.
Comment #9
fibigerg commentedOk, so I solved this problem, but run into another one. Browser sometimes render the page from local cache, after the user login. How can I prevent this from happening?
Thanks