• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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