Same here, we already reported this issue months ago.
This issue occurs across multiple of our websites when using Complianz in combination with LiteSpeed Cache. The bug has been known since the end of last year, and each time it’s promised that it will be addressed. According to support, it should have been fixed in the latest update (7.4.5), but that turned out not to be the case.
After a lengthy back-and-forth, it eventually became clear that the Complianz development team is still working on it and that the issue has not actually been resolved. It’s unbelievable that this problem has been known for over four months, yet it appears that no real attention is being given to it—despite it being reported in multiple topics here, by us and other users.
Additionaly, all the recommendations provided by Complianz for making adjustments or exclusions in LiteSpeed have not resolved the issue.
