Guest page caching
- Thread starter JoyFreak
- Start date
arn
Well-known member
Yeah... I'm not sure it's the best long term solution. But it isolates the problem.
- Seeing as how the logout page is always the forum index, you could exclude in .htaccess that page alone in terms of unsetting the 304 response.
- I need to read more into it, but the Xenforo team might be able to figure out a better solution. It seems your browser, when it gets sent back to forum index, asks the web server if the page has been modified, and returns that it hasn't, even though you were previously logged in, and now you are logged out. The browser is then serving its local cached page (with you logged in). There may be some combination of header settings that could avoid this cc @Chris D
arn
arn
Well-known member
@Mr. Jinx
Can you try this? Remove the .htaccess unset that you set before.
Xenforo already sets no-cache headers, so that logged in page shouldn't be cached by your browser anyway. But this adds these, so maybe it'll be more complete.
assuming your forum lives at:
This adds those headers to root directory only.
If your forum lives in a subdircetory like https://xenforo.com/community/ it'll have to be different.
arn
Can you try this? Remove the .htaccess unset that you set before.
Xenforo already sets no-cache headers, so that logged in page shouldn't be cached by your browser anyway. But this adds these, so maybe it'll be more complete.
assuming your forum lives at:
Code:
<FilesMatch "^(/)?$">
Header set Cache-Control "no-cache, no-store, must-revalidate"
Header set Pragma "no-cache"
Header set Expires 0
</FilesMatch>This adds those headers to root directory only.
If your forum lives in a subdircetory like https://xenforo.com/community/ it'll have to be different.
arn
arn
Well-known member
Well in theory the no cache is already in place when your are logged in. So that page shouldn’t have been cached by your browser already.
So we have to pinpoint exactly why it’s not already working on some browsers.
If the latest htaccess change works we could see if there’s a header that’s missing on the current xf logged in pages.
arn
Will this be fixed in the nearby future as it seems to be a general problem?
Btw, the correct FilesMatch command will not fix the problem as it also appears on other forum pages as soon as you navigate there after logging out.
Will setting a max-age for specific file type using
?
be overwritten by
if the latter one is applied for all files?
In this case, the problem would be even worse.[/CODE]
Btw, the correct FilesMatch command will not fix the problem as it also appears on other forum pages as soon as you navigate there after logging out.
Will setting a max-age for specific file type using
Code:
Header set Cache-Control "max-age=xxxxxxx"be overwritten by
Code:
RequestHeader unset If-Modified-SinceIn this case, the problem would be even worse.[/CODE]
Mr. Jinx
Well-known member
That does not seem to be the case:
Although we do see more people reporting the issue in this topic, it is not widespread.
And I don't agree with 'it is not consistently reproducable'. I can reprocude it every time and offered XF to take a look, but they say it is a server issue.
Anyway, I stopped playing with guest page caching as a result of this.
Hristo Avramov
Active member
Did someone test if this issue still happens in xf 2.2?
JoyFreak
Well-known member
I didn't use litespeed at the time of this thread but that was on 2.1.
I tend to get this error when I try to log in:
I've tried reloading the page and it never works. It works if I clear the cache for my site and then reload it again. My cache program is part of Godaddy's website security. When I disable caching I don't have the issue so this error message is definitely related to caching. And based on what I've read here it's not just one web caching program since I don't use Litespeed nor Nginx, and it still happens.
Alright, it happened again. I'll describe the exact steps that led to it.
I started a thread, but before hitting the post button to post it, I just clicked on my username to log out. Then I hit the back button to go back to the previous page and then tried to log in again and I got the security error message. I've done this multiple times and each time the error message comes up. So there's at least one reliable way to reproduce the problem just in case the developers here are wondering how to do it. I'm sure there are other scenarios where this error comes up.
I started a thread, but before hitting the post button to post it, I just clicked on my username to log out. Then I hit the back button to go back to the previous page and then tried to log in again and I got the security error message. I've done this multiple times and each time the error message comes up. So there's at least one reliable way to reproduce the problem just in case the developers here are wondering how to do it. I'm sure there are other scenarios where this error comes up.
Similar threads
- Poll
