Example: assume you have a woocommerce site and bring “woocommerce_products_per_page” cookie which should vary from user to user, and you should not serve everyone with the same cache file.

There are two ways to accomplish this:

The more efficient option is a javascript-based solution. A javascript plugin would only need to store one copy of the page and would build the display based on the existence of the cookie.

If a rewrite rule-based answer is preferred, the site can be configured to vary on the cookie by adding the following rule to your site's .htaccess file:

<IfModule LiteSpeed>
CacheLookup on
RewriteRule .* - [E=Cache-Vary:woocommerce_products_per_page]
</IfModule>

When user visit woocommerce site with woocommerce_products_per_page=xxxxxxcookie will be created. Using the rewrite rule above, the cache will vary on that cookie. This means the cache will store two copies.