My site just got Boost and i've got this strange issue - as i (and my users) surf site as logged in user i see some pages just as i was anonymous user. Firstly i was thinking it is random, but now i think it is certain urls that are not properly displayed.
It's very strange and confusing for my users - they just see login block and "log in to post comments" strings, after clicking certain links on site. Those URLs are:
http://basoofka.net (home page - when i log in i go to http://basoofka.net/node?destination=node and i'm logged in, but when i click on logo - i see site as anon again)
http://basoofka.net/event/2010/01/07/month
http://basoofka.net/contact
http://basoofka.net/forum/* (any forum view)
If i click on some menu items, and, without giving my account/pass, i'm suddenly logged in. These urls include:
http://basoofka.net/node
http://basoofka.net/tracker
http://basoofka.net/user/* (any user profile page)
http://basoofka.net/node/* (any node)
http://basoofka.net/taxonomy/term/* (any term)
Any ideas why this is happening and how to get rid of it?
Some thiongs i've tried:
- http://drupal.org/node/305071#comment-999958 (i see cookies, .htaccess triple checked)
- http://drupal.org/node/305071#comment-2209484
- http://drupal.org/node/305071#comment-1004476 :
1)
root@sd124:/home/palik/public_html/basoofka.net/cache/normal/basoofka.net# ls -R | grep logout
root@sd124:/home/palik/public_html/basoofka.net/cache/normal/basoofka.net#
so no, logout page is not cached as far i see
2) don't know how to check it, firebug shows sth like this for homepage:
Date Thu, 07 Jan 2010 06:16:07 GMT
Server Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny3 with Suhosin-Patch
Last-Modified Thu, 07 Jan 2010 05:52:44 GMT
Accept-Ranges bytes
Content-Length 15431
Content-Type text/html; charset=utf-8
Content-Encoding gzip
X-Cache HIT from cache
X-Cache-Lookup HIT from cache:3128
Via 1.0 cache:3128 (squid/2.6.STABLE13)
Age 113
Nagłówki zapytania
Host basoofka.net
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7
Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language pl,en-us;q=0.7,en;q=0.3
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-2,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Proxy-Connection keep-alive
Referer http://basoofka.net/
Cookie SESS594c929fa1f36c4d7653f9e4fac2f0fb=d5e48244fde255a214a8228c57ea48db; __utma=45819319.668723455.1262817284.1262840770.1262843937.3; __utmz=45819319.1262817284.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); boost-gzip=true; __adtaily_ui=Zu3H3AmGkB; SESS17ec8c90470ce790bd03f910c8b4bfde=362ce21bc1f4af0235ff4ce11b008f91; Drupal_l10n_client=0; has_js=1; __utmb=45819319.100.10.1262843937; __utmc=45819319
If-Modified-Since Thu, 07 Jan 2010 05:52:44 GMT
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedtry the latest dev; did more changes to the login cookie that gets set.
Comment #2
millions CreditAttribution: millions commentedThis is happening to me also, I have 1.18 released on 1/24/10
Comment #3
Ela CreditAttribution: Ela commentedSame here..
Parts of pages, specifically these that were visited before logging in after log in show as if though I was a visitor.
Also, logging in from certain pages redirects to a weird url that tends to change from time to time. Sometimes it redirects to a blog page, and it will continue to do so.. then it will change and redirect to a different page (always same one), and then it will change and redirect to a page that do not exist (again, always same one) in which case, I get page does not exist after loggin in.(no longer can reproduce this problem)Just curious.. should these settings be on:
Aggressive setting of the boost cookie
Set/Remove the boost cookie in the boost_init function.
and
Follow RFC2616 14.9.4
I am using the latest dev version.
Comment #4
Ela CreditAttribution: Ela commentedComment #5
mikeytown2 CreditAttribution: mikeytown2 commentedThis looks like squid is caching where it shouldn't be. Is squid setup correctly?
Comment #6
Ela CreditAttribution: Ela commentedin my case there is no squid..
Comment #7
Ela CreditAttribution: Ela commentedI'm just looking around and playing to see what I can spot... and definitely only the pages that were visited before logging in are the only ones that show as if though I was a visitor, if I visit them after logging in. Other pages show they way they should when logged in...
Also, If I refresh the page that shows the view a visitor would see, then it refreshes to the way it should look when logged in.
That's fine by me, but members might not think of that... If this page is for example a page that a member can edit, he/she will not see an edit tab on the page, unless they refresh it..
Comment #8
mikeytown2 CreditAttribution: mikeytown2 commented@Ela
Can I get very specific details like headers & URL's so I can have a better understanding of what's going on in your case?
Comment #9
Ela CreditAttribution: Ela commentedI will email you my site url from your profile page :)
Comment #10
Ela CreditAttribution: Ela commentedIt's sent :)
Also .. noticed that the destination URL after loggin in get's fixed, changed after running cron.(I can no longer reproduce this problem)I have applied a rule to change user log in destination to user account page, so that partially fixes the problem for me anyway... but if the destination was going to be a page that does not exist then a error of page does not exist would still appear, in addition to being redirected to the user account page.. I hope this makes sense.. :)
Comment #11
digi24 CreditAttribution: digi24 commentedI have also experienced this phenomenon. Unfortunately I cannot exclude that other modules or sitewide changes might be responsible, which we have installed while upgrading the modules (eg. memcache and its session manager - just testing #585748).edit: cannot reproduce anymore, everything seems fine now
Comment #12
joeytheman CreditAttribution: joeytheman commentedsubscribing
Comment #13
Ela CreditAttribution: Ela commentedI can confirm after playing around a bit that this is the case. Each page that was visited before logging in shows as if though logged out if visited after logging in.
This causes a bit of confusion.. a user has to log in again in order to view the page as it should appear OR refresh the page.
Any update on this?
Comment #14
mikeytown2 CreditAttribution: mikeytown2 commentedUnder Boost advanced settings turn on Aggressive setting of the boost cookie. Let me know if this fixes your issue.
Also have a look at this
#197786: Some servers / browsers will cache pages even when header Cache-control: no-cache is set
Comment #15
Ela CreditAttribution: Ela commentedHi there :)
I do have "Aggressive setting of the boost cookie" turned on when experiencing this.. Any other possible settings?
Comment #16
mikeytown2 CreditAttribution: mikeytown2 commentedturn it off, see if that changes anything. Otherwise look at this patch for core http://drupal.org/node/197786#comment-1794074
Comment #17
Ela CreditAttribution: Ela commentedok.. going to test changing the setting or the patch in an hour or so and will report back :)
Comment #18
Ela CreditAttribution: Ela commentedHi :)
Turning off the cookie setting did not work.. So I tried the patch.. did not work.. cleaned the browser cache, still the same. Then I tried turning on or off the cookie setting for boost with the patch.. same results, none of it worked.
Please let me know if you have any other tips.
Comment #19
mikeytown2 CreditAttribution: mikeytown2 commentedEla, after looking closer, your apache doesn't have mod_headers enabled. Each cached page has Cache-Control: max-age=1209600 (2 weeks) which is the drupal default for all non php objects going though apache (static html in this case). Enable/Install mod_headers on your server and you should be good to go!
Comment #20
Ela CreditAttribution: Ela commentedHi Mike,
Thank you for looking into this.
I'm sorry for my lack of knowledge.. could you point me in the right direction on how to do that?
Comment #21
Ela CreditAttribution: Ela commented... deleted
Comment #22
mikeytown2 CreditAttribution: mikeytown2 commentedTry this in your httpd.conf file
Restart apache to let the changes take effect
Comment #23
mikeytown2 CreditAttribution: mikeytown2 commentedActually, could you test out these rules before you add in mod_headers to your httpd.conf file? Replace your
FilesMatch
section with this; its at the top of the boost rules.Comment #24
Ela CreditAttribution: Ela commentedI contacted my host regarding the Install of mod_headers and they said that they have been applying these changes to servers but did not do it on mine yet. They should change it tonight. :)
I will also try the rules change you provided above and report back within an hour or so, this way we know if this works before the change is applied to the server.
Comment #25
Ela CreditAttribution: Ela commentedI must be missing something.. I can not find FilesMatch section in the boost.rules.inc ... am I looking in the wrong place?
(((edit)))): I found FilesMatch string section in the boost.admin.inc towards the bottom of the file.. I'll wait for your instructions on how to proceed..
Comment #26
mikeytown2 CreditAttribution: mikeytown2 commentedgoes in you .htaccess file
Comment #27
Ela CreditAttribution: Ela commentedFound it :) Sorry for the confusion.
I applied the change, but it did not make any difference when it comes to this issue :(
I will try additional things, if you want me to.
mod_headers should be there on the server tonight and I will as well report back on that :)
Comment #28
mikeytown2 CreditAttribution: mikeytown2 commentedEla, your browser is caching the pages for 2 weeks. You need to test this in a different browser or clear your browsers history. This means you will have intermittent reports of this still being broken for the next 2 weeks.
Comment #29
Ela CreditAttribution: Ela commentedHi.. I cleaned the history and in addition also went to pages that were not visited by me before, then logged on, went to same pages.. same issue.
Comment #30
mikeytown2 CreditAttribution: mikeytown2 commentedCan you attach your .htaccess file? Looking at this you still have
Cache-Control: max-age=1209600
set in your headers;ExpiresActive Off
is supposed to clear that, yet it's not working.Comment #31
Ela CreditAttribution: Ela commentedHi.
Thank you for your continuous effort to help in solving this!! :)
This is the code from my .htaccess before applying the change that you mentioned above. (I changed it back, since I did not see the difference after applying the change)
(edited to remove web address)
Comment #32
Ela CreditAttribution: Ela commented... I realized now that you wanted me to post the file with the settings applied.. Do you want me to apply them again and repost?
Comment #33
mikeytown2 CreditAttribution: mikeytown2 commentedYes, Apply them and repost; it should be what your server is currently using.
Comment #34
azinck CreditAttribution: azinck commentedI'd encourage Ela to make absolutely sure this is a Boost problem. I'm seeing the same thing and had initially attributed it to Boost but now am convinced it's a block caching problem. I have a custom module I wrote that, despite having set its cache=BLOCK_NO_CACHE is still getting cached by the block cache. And I still see the problem with Boost disabled. Only disabling the block cache fixes it. So now I need to track down why Drupal's not honoring my block cache directives.
I'm on Pressflow 6.15, Cacherouter using APC, and Boost 1.18
Comment #35
Ela CreditAttribution: Ela commentedOK.. Uploaded the following .htaccess file to the server:
Comment #36
Ela CreditAttribution: Ela commented@azinck
I'm not absolutely sure, we are trying to figure this out..
I am using blockcache_alter module, Mike do you think they might conflict in any way?
Comment #37
mikeytown2 CreditAttribution: mikeytown2 commentedEla,
New htaccess settings appear to be working. Test for the bug, it should be gone.
Comment #38
Ela CreditAttribution: Ela commentedHi Mike..
I deleted history, cookies, cache etc on IE, went back to the site, went to few pages, logged in, went again to same pages and they again look as if though I was not logged in. So, on my end it does not seem like the problem is gone..
If you'd like to log in to test it, that would be great.
Comment #39
mikeytown2 CreditAttribution: mikeytown2 commentedTry this in your htaccess file; Key point is to add in
FileETag None
Comment #40
mikeytown2 CreditAttribution: mikeytown2 commentedIf the above doesn't work try this
This as well
Comment #41
Ela CreditAttribution: Ela commentedHi Mike .. I applied the new settings.. cleaned the history, etc, got to the site, went through few pages, logged in.. same thing if visiting the pages that visited before logging in.. all other pages are fine, as long as I did not visit them before logging in..
((((((EDIT))))))) Did not see the post right above.. will try the other settings as well and report back
Comment #42
Ela CreditAttribution: Ela commentedWOW!!! hehe :)
The setting
WORKS!!
YEY!! :)
Do you still want me to test the last code or leave as is since this one works?
Ah.. this is great news!
Comment #43
Ela CreditAttribution: Ela commentedHi again.. Additional couple of questions.....
Once the mod_headers are installed on the server.. will it have any difference?
.. and Do I keep this setting to apply in the future for the htaccess file once let's say there is a new version of boost and htaccess needs to be updated?
Comment #44
mikeytown2 CreditAttribution: mikeytown2 commentedI'll be putting this into the rules, as this is the fix. So when boost 1.19 comes out, you should be safe even if mod_headers isn't there.
Comment #45
Ela CreditAttribution: Ela commentedGreat.. Thank You so much!! I am so happy that you were able to figure this out!!! WOW! :)
Comment #46
mikeytown2 CreditAttribution: mikeytown2 commentedComment #47
Serious_1 CreditAttribution: Serious_1 commentedcan someone point me in the direction of Drupal 101 or Drupal for DUMMIES? lol
just had this dumped in my lap.
have no idea how to put it together but this forum seems to be addressing my biggest current issue!
looking forward to being part of this community!
thanks for what everyone has done in developing this product.
can't wait to learn how it works!
Serious_1
Comment #48
mikeytown2 CreditAttribution: mikeytown2 commented@Serious_1
How did you put in the boost .htaccess rules before? Do the same thing but replace the filesmatch part with this
Comment #49
mikeytown2 CreditAttribution: mikeytown2 commented@Serious_1
First question is are you using the boost module?
Go to admin/build/modules on your site and see if it's checked, or even listed. If not this your barking up the wrong tree.
If you are in fact using Boost and you don't know about the .htaccess files (which is in the same directory as index.php) then you probably need to pay someone to help you. That someone will not be me, too busy to help.
You can probably find what your looking for in here
http://drupal.org/forum
Comment #50
Serious_1 CreditAttribution: Serious_1 commentedThank You!
Comment #51
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted
also did some minor changes as well.
http://drupal.org/cvs?commit=342406
Comment #53
kone23 CreditAttribution: kone23 commentedHi there,
I'm re-opening this thread because I'm having a similar but not identical issue on a drupal website. The difference is that I have mod_headers enabled .
So I run a drupal 6 locally on MAMP. I am using boost 6.x-1.x-dev.
I hope someone will be able to advise. Please ask for specific details if you need any.
Thank you in advance
Comment #54
kone23 CreditAttribution: kone23 commentedHas anybody experienced the same issue ?
Does anybody know what I could have set up wrong ?
Comment #55
mikeytown2 CreditAttribution: mikeytown2 commentedhappens if boost is disabled as well with core
#197786: Some servers / browsers will cache pages even when header Cache-control: no-cache is set
Here's the patch
http://drupal.org/node/197786#comment-1565612
Using firefox right?
Comment #56
kone23 CreditAttribution: kone23 commentedHi,
Thanks for replying :) I tried the patch but it did not help. I'm still having the same problem.
Here is a list of modules I use for login, maybe there is a compatibility issue somewhere
login destination
login toboggan
FYI: it happens with safari, firefox and chrome
Thanks
Comment #57
mikeytown2 CreditAttribution: mikeytown2 commentedGet firecookie
https://addons.mozilla.org/en-US/firefox/addon/6683/
Let me know if the DRUPAL_UID cookie is set when this error happens.
You can also try tweaking the "Aggressive setting of the boost cookie" Setting
Comment #58
kone23 CreditAttribution: kone23 commentedOK,
I got it to work by disabling the "Aggressive setting of the boost cookie" Setting and setting the document root to its value.
Thanks so much mikeytown2. Boost is what I needed, stoked.
Comment #59
ressa CreditAttribution: ressa commentedSadly, my host don't have mod_headers installed, so is there any chance that 6.x-1.19 will be released any time soon? The latest official release (6.x-1.18) is now close to one year old, from 2010-Jan-25...
In the meantime, is it safe to use the dev version on a production server, or will it crash? 8o)
Comment #60
mikeytown2 CreditAttribution: mikeytown2 commentedit's fairly safe; I use it at work for some large websites.
Comment #61
ressa CreditAttribution: ressa commentedThanks, I have put it online now, and it has Boosted the web site a lot, Yslow times:
Before Boost - around 0.9 seconds, sometimes more
With Boost - around 0.3 seconds, every time!
I think the Yslow program itself also takes up resources, if I try browsing the site with a plain vanilla browser like Konqueror, the pages show up instantly. What an amazing module 8o)
Comment #62
interestingaftermath CreditAttribution: interestingaftermath commentedI'm also experiencing this issue. I am on the latest dev, with mod_headers installed and I've tried it with Aggressive Cookies on and off. It seems more prominent in IE8 than Firefox/Chrome but I can't be sure.
Log in, browse to some pages, continue browsing and then you'll appear to be logged out. Continue browsing and you'll stay logged out until (it seems) that when you go to a page that previously worked, it will work. Hard refreshing on the pages that appear to log you out "fixes" the issue.
EDIT: With Core caching set to Normal and Boost caching set to Core & Boost I cannot cause the error. Weird... will report back
Comment #63
mikeytown2 CreditAttribution: mikeytown2 commented@interestingaftermath
Would you mind testing out this core patch?
#197786: Some servers / browsers will cache pages even when header Cache-control: no-cache is set
Here's the patch in the big issue queue: #86.
Comment #64
ChrisLaFrancis CreditAttribution: ChrisLaFrancis commentedSubscribe.
Comment #65
ChrisLaFrancis CreditAttribution: ChrisLaFrancis commentedActually, adding these lines from comment #40 to Apache's configuration files seems to have done the trick:
Not sure if it's related, but I should mention that I've had the patch from this comment applied for a while, but that alone didn't seem to help.
Comment #66
NPC CreditAttribution: NPC commentedSubscribing
Comment #67
hanamizuki CreditAttribution: hanamizuki commentedI'm suffering the same problem...don't know why but "ExpiresDefault A1" didn't save me. I'm not using dev version, is it the reason?
Comment #68
bgm CreditAttribution: bgm commented@hanamizuki, please test the dev version and regenerate the .htaccess rules.
Can anyone else confirm whether this issue is fixed or not in dev?
Thanks
Comment #69
Priyanka Singh CreditAttribution: Priyanka Singh commented#39 worked for me.I am using boost v.6x-1.18.
Thanks you so much @mikeyTown2
### BOOST START ###
AddDefaultCharset utf-8
FileETag None
ExpiresActive Off
Header set Expires "Sun, 19 Nov 1978 05:00:00 GMT"
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"