Search results

Hmm, interesting. That said, the ad tags I had also do the same. Basically any script that sets cookies is likely to do this, no? Also... why is private cache not hitting? It seems to me if Gtag is adding the tag, then I've consented, I have the cookie, it ought to be serving a private cache to...

Done, at https://test.westeros.org/ Fresh OLS, fresh Mediawiki, the only enabled extensions are LiteSpeedCache and Gtag... and it will not cache in the browser when Gtag is enabled. As far as I can see, all Gtag does is insert the Google Analytics script. The code for the extension is a simple...

I'll give that one a try. I have a bunch of extensions from Mediawiki, which I supposed should not be an issue, but maybe one of them is.

Sorry, you mentioned a PHP function, so since I was new to 8.1 I figured I'd switch to some other version to see if that helps. If it's the server, well, I'm at a loss -- this is a vanilla OLS install. Have you yourself tested LS Enterprise + Mediawiki with Google Analytics?

Well, GTag doesn't change the scenario, anyways. I guess I'll switch around to another flavor of PHP and see if anything changes.

As we discussed earlier, I have disabled the GDPR and ads, so the only script setting cookies is GA, and that also doesn't successfully engage the cache. I am in the process of removing the Mediawiki GoogleAnalytics extension and replacing it with a newer one )Gtag) to see if that improves the...

Right. I have OLS, I have Mediawiki, I have GA via The reason I mention Varnish is that we use it on the main site we were hoping to move to LOS + LS cache (https://awoiaf.westeros.org), and it works fine, so perhaps it being primitive means it ignores whatever supposed plugin is causing this...

Okay, but how can a Google Analytics script cause this issue? Does no one using LS Cache use Google Analytics as well?

Thanks for helping me narrow it down. It seems like it must be a Mediawiki issue, then, since the script is being loaded via LocalSettings.php. OF course, now that I think of it, Varnish doesn't seem to have a problem with this script-related issue, for whatever reason. May have to look to...

Hah. Well, apparently they have it through a third party vendor and are contacting them. That said... I have disabled all ads and the consent, cleared all cookies, restarted my browser... and I am now just getting misses. The only cookie being set is from Google Analytics. So it seems like the...

Sure: https://www.mediawiki.org/wiki/Extension:LiteSpeedCache Oh, you probably mean the GDPR code. That came from our ad guys, I have contacted them.

I will contact them and ask! Thanks for the help!

Think this covers it: Server Configure > Cache Module Module Parameters storagePath $SERVER_ROOT/cachedata Virtual Host (subdomain) > Cache Module Module Parameters CacheRoot lscache CacheEngine On CacheIgnoreCacheControl On CacheLookup public on CacheLookup private on Virtual Host...

That is not the result I get, which is very confusing to me. What browser are you using? Maybe it's a Chrome thing. Or a me thing, for some reason? Edge also doesn't ever return a hit.

Right, I have reset things a lot, and I am glad I am getting hits on a vanilla Mediawiki... but I still don't know why it's not working when I have the other cookies in. I'm going to restore them... Here is the actual test site we're working on, that has been presenting these problems.

Does your Mediawiki have Google Analytics cookies being served from it? Mine does, and it does not seem to work when the site puts any cookies on besides the login cookie. I'm no longer looking for a malfunction, I'm now wondering how to adjust the plugin or LS Cache rules to ignore those other...

I think it does two things, doesn't it? Checks to see if there is LS Cache support (presence of header), and then whether it's actually working (presence of 'hit' rather than 'miss'). Those two sites, I can check a page, get a miss, and then on re-load get a hit after it has cached it. Ditto...

I did not realize that. But here is the other site, it doesn't show br encoding.

Interesting. Is there some way to tell the cache to ignore cookies, then? Because the other two sites that have working caches are working in the browser, not just check.lscache.io, and they have the same header. Here's one of the sites.

A small advance, but I don't really know why. I reset everything and re-did the Cache settings and htaccess, and now when I try check.lscache.io, I actually will get hits. Which is great.... But when I check with an actual browser, no caching. What would be the difference between these two...