Boost has been brilliant for improving the performance on our site- our server was at limits before installation, now it is comfortable with room to spare.

I have minor gripe though- since installing boost, funny things seem to be happening with login/logout/sessions. Particularly the starting and ending of sessions- sometimes you login and it takes you straight back to the login page. THhn you press refresh and it appears to log you in then. (i.e. login page->enter details press ok->back to same page don't type anything press refresh->logged in).

Also when logging out now it sometimes just says 'Access denied'after you click logout- never used to do that before.

My suspician is boost, maybe boost interfering with cookies or something- has anybody experienced anything like this?
Chhers,
Chris.

CommentFileSizeAuthor
#1 boost-logout.patch574 bytesakalsey

Comments

akalsey’s picture

akalsey commented
Status: Active » Needs review
StatusFileSize
new boost-logout.patch574 bytes

The access denied issue on logout is because Boost is caching the logout page. Anonymous users can't access the logout page, so Boost caches the Access Denied page.

Attached is a patch that prevents Boost from caching the logout page.

drupdrips’s picture

drupdrips commented

That is true .. but you don't even need to patch. boost is flexible there for you to choose which pages you do not want boost to cache by going to boost admin page from: youdomain.com/admin/settings/performance/boost page , and there put in "logout" as one of the lines for a page that you don't want boost to create cached .html file for.

akalsey’s picture

akalsey commented

Agreed that the patch isn't strictly needed. However, since the logout page should never be cached, the module should ensure that it is not, rather than relying on the end user to add that to their config.

drupdrips’s picture

drupdrips commented

Agreed.

chrism2671’s picture

chrism2671 commented

I've tried this- let's see what happens!

drupdrips’s picture

drupdrips commented

Make sure to remove the old logout.html from the cache folder if it already existed/generated from prior to applying the patch.

akalsey’s picture

akalsey commented

Or simply run cron. That will toss out the old cache files unless you have a long minimum lifetime set.

wwwoliondorcom’s picture

wwwoliondorcom commented

Hi,

I have a login problem with the Admin, user 1 (me), my website asks me to login again on every page but no problem with other users.

I'm using persistent login module but I don't know if it is related.

Bye.

drupdrips’s picture

drupdrips commented

I bet it has something to do with it . Check the issues queue .. I remember seeing one raised with the PL issue, not sure if it would be related. But going by what you said, I don't think you would see this problem without the additional complexity of PL.

chrism2671’s picture

chrism2671 commented

I have experimented with turning off caching for logout however it sadly has not made any effect on the login/logout situation. Any other ideas?

I am also following the same issue on this thread http://drupal.org/node/305071 although I haven't had the time to action the most recent suggestions. Will report back when I do.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: Bizarre things happening to login » Logout page gets cached
Version: 5.x-1.0 » 5.x-1.x-dev
Component: Miscellaneous » Code

Better title.

christefano’s picture

christefano commented
Status: Needs review » Reviewed & tested by the community

Looks solid. I don't see why this isn't RTBC.

mikeytown2’s picture

mikeytown2 commented
Status: Reviewed & tested by the community » Closed (duplicate)

dup
#180703: /user/logout and /logout not cached

akalsey’s picture

akalsey commented
Status: Closed (duplicate) » Reviewed & tested by the community

Marking an issue with lots of discussion and a patch marked RTBC as a dupe is probably not the best idea. Despite the fact the other issue was created first, this one is more complete and the other should be marked as a dupe.

mikeytown2’s picture

mikeytown2 commented
Status: Reviewed & tested by the community » Closed (fixed)

Closing all 5.x issues; will only reevaluate if someone steps up #454652: Looking for a co-maintainer - 5.x

Reason is 6.x has 10x as many users as 5.x; also last 5.x dev was over a year ago. The 5.x issue queue needs to go.