We have been using the Nginx web server in the EGOCMS standard stack for several years now. It is characterised by the fast processing of static pages.
It can also be used as a proxy cache. For this, the configuration of the fastcgi setting must be adjusted. The Nginx then evaluates the header data of EGOCMS for caching.
Since EGOCMS prohibits caching after a login via the HTTP header, only pages without view permission end up in the Nginx.
Since EGOCMS knows about the release data of all pages, the HTTP Expires header is also sent correctly. Only if a page is changed after caching, it is not output directly. For this, the cache directory must be regularly emptied via a cron.
EGOCMS V18.8 can clear the Nginx cache directly.
In V20 it will be possible to empty the cache on client and language level.
A technical description of the configuration can be found in the Nginx Cache Tips&Tricks article. If you have any questions, please contact our support. We would also be happy to offer you a workshop on this topic.