Litespeed caching prevented saving settings

[devjaiba]

Describe the bug
When using Litespeed, the plugin settings were not being saved correctly due to caching.

Steps to reproduce

• Open the plugin settings in WordPress.
• Make changes and save.
• Observe that the changes are not saved when Litespeed caching is active.

Workaround / Fix Applied
Added the following to Litespeed exclusions:

Do Not Cache URIs:
/wp-json/pressidium-cookie-consent/v1/settings
/wp-json/pressidium-cookie-consent/v1/*

Do Not Cache Query Strings:
rest_route=/pressidium-cookie-consent/v1/settings

After applying these exclusions, the settings could be saved as expected.

Environment:
Browser: Chrome
Plugin version: 1.8.0

Expected behavior
Settings should be saved without having to manually add cache exclusions in Litespeed.

[over-engineer]

Hey, @devjaiba!

Thank you for bringing this up.

When using Litespeed, the plugin settings were not being saved correctly due to caching.

Small note: the plugin settings do get saved in the database, but when retrieved, an outdated version is displayed due to the LiteSpeed Cache plugin still serving stale data.

According to LiteSpeed’s own documentation, POST requests aren’t cached, which is why saving works, but GET requests, including REST API calls, are.

Steps to reproduce

• Open the plugin settings in WordPress.
• Make changes and save.
• Observe that the changes are not saved when Litespeed caching is active.

Let me expand on the steps to reproduce for future use:

• Install and activate the LiteSpeed Cache plugin.

For its caching functionality to work, you need to either have a LiteSpeed web server or be using QUIC.cloud CDN.

• Navigate to wp-admin → LiteSpeed Cache → Dashboard, and click Enable QUIC.cloud Services
• Follow the directions to connect your WordPress site to my.quic.cloud (this might require updating your DNS settings)
• Go to wp-admin → LiteSpeed Cache → Dashboard. In Cache Status, both Public Cache and Private Cache should
  be on. In QUIC.cloud CDN, both CDN in Use and DNS Verified should be checked
• Head to wp-admin → Cookie Consent
• Change any setting and click Save
• Refresh the page and note that the old settings are still appearing

Settings should be saved without having to manually add cache exclusions in Litespeed.

I do agree that integrating with LiteSpeed’s hooks to mark certain GET REST API requests as non-cacheable would be a valuable improvement. However, I see this more as an “enhancement” rather than a bug, since it’s about adding an additional third-party integration.

Thanks again for pointing this out! We’ll look into implementing it for the upcoming version.

[over-engineer]

Implementation note: This should be relatively easy to implement by hooking into the litespeed_control_set_nocache action provided by the LiteSpeed Cache plugin (docs reference).