Search results

Current version of Nginx caching was implemented with minimum functionality. Other functions will be added according to customers' feedback. Now you may add any cookies to exclusion list. I see you're telling about reverse behavior, it's not implemented yet.

Yes, something like that but without having to create Nginx config manually of course. :) I can't tell exact time now. I believe we'll do it this year, but it's not a top priority.

Plesk Nginx caching doesn't allow serving requests with cookies from cache by default, because cookies suggests interaction with server backend. However, you may add a list of "safe" cookie names to appropriate field if you're absolutely sure using someone's cached answer for request with these...

I see response headers only. Could you please provide request headers for this bypassed request?

"" means the same as 0 in this case. Empty string returns false in if expression.

Shopping cart usually uses cookies. Requests with cookies are not served from cache by default.

It shouldn't bypass proxy with these caching settings. Need more info. Could you please provide more info, for example your vhost Nginx config (in PM)? You're wrong. The main purpose of caching is always to reduce system load and increase responsibility by using upstream (and PHP) only once per...

Not completely. Nginx caching may be faster, but WP caching plugins are more flexible and integrated to WordPress. In the current state, Nginx cache is intended to be used mainly as a simple short-term cache. But we're planning to improve it for support of HTTP PURGE method to make it possible...

Thank you for your feedback and sorry for making you wait an answer for a long time, As I've already said, we'll review Roundcube package to get rid of unnecessary restarts. Sorry for inconvenience, but please be patient, it could take some time. We're building our packages using unified build...

If you're using such cache for each new host, you may create custom template for new vhosts with cache definition.

Proxy_cache doesn't require the separate cache location for each domain but this is desired behavoir. You may place cache path definition to the very beginning of virtual host file (before 'server' directive), it will be in http context (as on your example above) and define unique zone name and...

You may use proxy_cache, it provides the same capabilities in proxy environment as fastcgi_cache in FPM.

Updates with security fixes and features: The update you’ve mentioned doesn’t have any new features (for reference, new features are marked by [+], not by , as per the Changelog legend), so we’re not entirely sure what exactly we keep doing. Are you talking about the small non-security...