Cache Problems

In addition to the above issue, if I view from an incognito window on any of the posts, ONE of the posts flashes up as FOUC and remnants of the featured image then appear in the header.

I’ve tried this with JS cache + minifications, and CSS cache + minifications both activated, deactivated, and running from a full reset.

How do I stop this, please?

**edit**

I fixed this one by turning OFF ‘Load CSS Async’.

• This reply was modified 2 years, 10 months ago by deeveearr.

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

Report sent:

Report number: JPEZEXYG

Report date: 05/31/2022 02:10:22

if you disable cache login user , how does that widget do ?

Hi @qtwrk

It makes no difference.

I adjusted a couple of settings yesterday, and disabling ‘cache logged in user’ was one of them.

if you disable cache login user , please check the http response header as login user , and make sure you see x-litespeed-cache-control: no-cache

Hi @qtwrk

Where are these HTTP response headers?

Anyway, a further development this evening – my popular posts grids and pages started working again with cached logged in users set to ON!

Knowing where to find the HTTP headers might help in the future though!

• This reply was modified 2 years, 10 months ago by deeveearr.

I found out how to view the HTTP headers, and the only one mentioning Litespeed was:

x litespeed-tag: b45_

This was with the ‘cache login user’ turned OFF.

I turned it back on now, and the images are sticking again with it remaining off, and also with it turned to ON.

So what exactly is the problem?

Hi @qtwrk

Would it not be better rather than playing with the normal settings, to either exclude or force a few of the selectors and scripts in one of the many positions provided in the Litespeed Cache plugin?

Bear in mind that this would mean three widgets (one for the front page placed in a grid format, one for the post sidebar, placed in a list format, and one for the page sidebar placed in a list format) that would need forcing or excluding.

This was with the ‘cache login user’ turned OFF.

could you please share me the full list of response header ?

and actually , if you don’t see x-litespeed-cache: header, that means the page is NOT cached at all , something else might be in the way

Hi @qtwrk

Oh it’s definitely cached, as all of the speed tests, plus Quic Cloud say so.

Ok then, where and how do I find the response headers?

you can follow this guide

Hi @qtwrk

That guide is nothing short of useless.

Please explain in simple terms, where and how do I find the response headers, and do I have to enable or disable Quic Cloud?

THIS is what I got following the guide:

x-content-security-policy: img-src *; media-src * data:;
x-content-type-options: nosniff
x-frame-options: ALLOWALL
x-permitted-cross-domain-policies: none
x-powered-by: midlandsmaidens.com
x-qc-cache: hit
x-qc-pop: EU-GB-LCY-109
x-xss-protection: 1; mode=block

• This reply was modified 2 years, 10 months ago by deeveearr.

this is where it displays the response header , I grabbed from the video

Hi @qtwrk

Please note the above reply.