When I have normal cache ENABLED the site does not authenticate. I seems to get stuck in a cycle trying to connect with facebook and go back to the Callback URL. Same problem for aggressive cache.
It works fine with cache DISABLED.
When I have normal cache ENABLED the site does not authenticate. I seems to get stuck in a cycle trying to connect with facebook and go back to the Callback URL. Same problem for aggressive cache.
It works fine with cache DISABLED.
Comments
Comment #1
lennart commentedSorry. Titled it wrong.
Comment #2
lennart commentedAm I the only one with the cache problem?
Comment #3
PGiro commentedSame for me using IE (haven't tested the other) on beta4 : works without cache, keeps going back to the same page with cache.
If I go to the front page while this is happening, I get to step 1 of registration.
I'll post a fiddler report of what is going this weekend
Comment #4
aon commentedI am having this as well. Disabling caching under the performance section worked for me.
Comment #5
lennart commentedWould it be possible to make Facebook Connect work with cache enabled?
For most busy sites disabling cache is not a viable option.
Comment #6
lennart commentedChanging title to reflect category status.
Comment #7
LaNets commentedHello,
Today i spent a few hours on the cache problem, but for the moment I have not found a solution yet.
I'll try to explain the problem I encountered.
When the user validates the FB pop up login window, we got a refresh of the current page.
Under normal circumstances, the hook_init is triggered and the user is identified.
If the cache is enabled, the page header is changed. Drupal
will set 304 headers, so browsers can use their own internal caching
mechanisms and avoid unnecessary HTTP round-trips when applicable.
Because of the browser cache, the hook_init is no longer triggered.
The function facebook_onload js function causes a refresh loop of the page.
I hope a solution to circumvent this problem would be quickly found.
Comment #8
lennart commentedYour efforts are very much appreciated.
Comment #9
LaNets commentedHello,
I commited a new dev version that works with the cache enabled, but didn't do a lot of testing.
You can test by downloading the latest version on the CVS repository.
Comment #10
lennart commentedThanks a lot! It works now!
Tested in Google Chrome and IE6
Comment #11
drutube commentedI'm not sure this is working in the 5.x version which was uploaded recently.
I just installed and note that there wasn't an issue with the cache as described in this thread before the isntall. However the exact behaviour described above -- recycling endlessly -- occurred upon logging out of the session. I overwrote the new module folder with the old or previous and the recycling stopped.
I'll try to test more later and realize this is not a very helpful post. If anyone else experiences the same please try to drop back a version and see if it doesn't fix.
BIG NOTE. I'M TALKING ABOUT THE 5.X VERSION only
Comment #12
EvanDonovan commented"[T]he exact behaviour described above -- recycling endlessly -- occurred upon logging out of the session."
When I installed the 5.x-beta2, I was no longer even able to log in using Facebook Connect. Instead it kept reloading the page, going back and forth between facebook.com and our site.
Comment #13
EvanDonovan commentedOn beta1, my Drupal session stays logged in even after I delete all my session cookies (using the Web Developer toolbar in Firefox). Facebook, on the other hand, is logged out. I don't understand how this is possible.
Comment #15
gunwald commentedI know, this is a very old report, but I have the same problem. With cache enabled I run in a loop and although the user actually gets logged in some times, he can not see that, because the page keeps coming from cache. What am I supposed to do?
I am using the latest beta for Drupal 7.