JoyFreak
Well-known member
It’s not worth the hassle for what it’s worth.+1
Used both redis and memcached.
Currently disabled guest caching.
It’s not worth the hassle for what it’s worth.+1
Used both redis and memcached.
Currently disabled guest caching.
+1
Used both redis and memcached.
Currently disabled guest caching.
Did someone manage to fix it ?
So it seems on the latest version it's still present. I am really wondering from where the problem comes and why for few people only.
The reasons have been explained: the behaviour isn't consistent with how the guest page caching works. The software cannot be responsible for a server response triggered with a HTTP code that the software itself never uses in that context; if you're seeing 304 not modified and it is missing the XF cache-hit headers it quite simply is not coming from XF.
It is not what we would describe as a "widespread issue" because, at best, we've had a handful of reports for it and it is not consistently reproducible on most installations that we've seen.
If anyone has a consistent reproduction case they are more than welcome, as ever, to submit a ticket with those details. Perhaps even the very customer you speak of absolutely should enable it and they can then report the issue to us if they do encounter it.
What if I cant stop apache in shared hosting?If you often testing something, you should do "redis-cli flushall" or better set
'persistent' => false, in config.php
Then stop apache, do a "sync" and then start your apache, the problem is gone. (here)
Not worth all the hassle.Do you suggest carrying on with guest page caching if I have this small problem? Because the guest page caching speeds the site for unregistered users.
I didn’t upgrade, mine was a install, so definitely nothing to do with that.My hosting company allowed me to test on another server. I know most likely the servers are setup in the same way but there are some differences between the servers. The same problem occurs.
Did someone test if this problem also occurs with fresh install of xf 2.
My website got upgraded from xf 1.5 to xf 2. May be this is the link between all of us who have this problem.
Welcome to the group!I'm having the same problem here.
We use essential cookies to make this site work, and optional cookies to enhance your experience.