Please read this:
https://docs.litespeedtech.com/lscache/devguide/advanced/#understanding-response-status-codes-200-and-304
Thanks for the link. I understand that this return code is telling the browser that the copy stored locally is valid and theres is no need to get anything from the server to save bandwitch and speed everything up.
But I was surprised that without changing plugin configuration, behavior has changed, because 200 OK was returned before.
No, this feature exists since many many years. Apparently you just never noticed.
both 200 and 304 could be normal , depends on your browser and the cache control header
Ok, I see. For me was strange because never saw this behavior until last update.
Cheers
It has nothing to do with the cache plugin. It is LiteSpeed LSWS feature.