• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Nginx microcache configuration for high traffic sites

Where would you put that code? Little confused there.

But going back to the overall function, I don't understand why Plesk would add a cache that simply won't work on 99% of websites. Is it just marketing? "Hey we do microcaching (you just can't use it without a degree in computer science).

Those nginx configurations can be used on servers running without Plesk (basic LEMP stack)
Both of them cache everything by default, and then you can add the list of cookies or location you do not want to cache.
But in Plesk, it's the opposite, the nginx configuration begin with :
Code:
        set $cache_cookie $http_cookie;

        if ($cache_cookie !~ "^\s*$") {
                set $no_cache 1;
        }
So it require to browse our own website and to list all cookies which can be cached.
 
Any solution for this on Plesk? Default should be to cache everything and add cookies not to cache. Or at least have the option. There is a whole Bypass section which is kind of superfluous as Bypass is the default behaviour.

Still would like to know why I'm still getting the BYPASS with no cookies set.
 
i will research this topic. Can you confirm that goal is to serve static files by nginx cache without requests to apache?
 
Back
Top