• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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