Nginx Cache Manager - WooCommerce Cache Rules

[UHLHosting]

Hi,

So we were glad to see Nginx Cache Manager working with Apache!

We have 1 production website where the customer already informed us about issues with their products not being visible in the cart after they were added to cart. We do not use other caching plugins that can interact with such cookies and the way they are cached.

The only issue is that the cache rules are not complete and WooCommerce has basically no rules at all for caching.

The rule found was:

./ea-nginx/server.conf.tt:    if ( $http_cookie ~ "wordpress_logged_in_[a-zA-Z0-9]+" ) {
        set $CPANEL_PROXY_CACHE off;
        set $CPANEL_SKIP_PROXY 1;
    }

What is my question in end to Cpanel, would the current caching solution should work with WooCommerce and if so, how come you folks made a rule to exclude logged in users, yet nothing for woocommerce cookies.

To remind you that I have tested this in both websites, and indeed my cart shows always the right amount of products, yet that is only when logged in.

Opening another browser in my case once the issue occurs, will always show cart 0 no matter how many products were added to it.

So first of all I have a question for all WordPress + WooCommerce users who use Apache + Nginx Cache Manager together, how do you solved your issues of caching WooCommerce cookies and if so please share the code used.

Second question is for Cpanel since I already have a ticket open and seems was escalated to LVL2 support, you realise how much could had been avoided, by properly informing users they need to add their own rules about properly caching WooCommerce, or just as in our case, the customers we have will come running to us telling us that products are not visible in cart, especially when Ajax was used. Searched in all forum about the similar issues, all I can say i maybe people here do not run WooCommerce since we have now a second WooCommerce site that has the very same issues. Products are visible in /cart yet not in the websites cart . This is clearly a Nginx Caching issue/conflict with WooCommerce cookies.

A few ressources:
Gist Code
Serverfault

 

[cPRex]

Hey there! What's the ticket number you have open? We definitely put some emphasis into WordPress as it is such a common piece of software, but we're happy to look into solutions for other CMS products as well.

 

[UHLHosting]

Hey there! What's the ticket number you have open? We definitely put some emphasis into WordPress as it is such a common piece of software, but we're happy to look into solutions for other CMS products as well.

Out ticket number is: 94424090
Please note that this is not another CMS, WooCommerce is just a plugin for WordPress to add shop functionality.

 

[cPRex]

Thanks for that - I'm following along with the ticket on my end now as well.

 

[UHLHosting]

Thanks for that - I'm following along with the ticket on my end now as well.

So how do you like the latest reply from support? When after 1 week of troubleshooting, they simply now tell me is not a cpanel issue. You folks make me sick, you know that? Slow by slow every time when you manage to pull such people, if he is a migration specialist, and he does not have motivation let him stay homesick. By the way I do wonder why you dont have a policy that one user will own the ticket, unless he really cannot, then others should take it. Everyone before this person was kind to look into the issue, if would not be cpanel issue I would say if id be using Engintron, or anything else beside cpanel, yet this is Nginx Proxy made by cpanael to work for all products. And is not!

 

[cPRex]

Due to the nature of some of the comments in your support ticket, I'm not able to make any further comments on this thread at this time.