Rather than asking a complex PHP-My SQL application like Word Press to do some extra work for caching, we will ask light-weight Nginx to cache Word Press content on its end.Nginx has built-in support for but it doesn’t have mechanism to purge cached content built-in. Without this 3rd party module, cache won’t be updated if you create/edit any post/page in Word Press.Our server has 32GB RAM by the way, so 6.3GB is close to 20% No matter how you are using Word Press, i.e.
This line tells Nginx to use old (stale) cached version of page if PHP crashes.
This is something not possible with Word Press caching plugins.
The most recent version of TLS is 1.2, but there are still modern browsers and libraries that use TLS 1.0.
So, we’ll add this line to our config then: That was easy, now on to something more complicated (which I made easy for you): The cipher suites are the hard core of SSL/TLS.
Researching what cipher suites to use, what not to use and in what order takes a huge amount of time to research. First you need to configure Nginx to tell the client that we have a preferred order of available cipher suites: All of these suites use forward secrecy, and the fast cipher AES is the preferred one.
You’ll lose support for all versions of Internet Explorer on Windows XP. If you want an explanation, read the DHE handshake and dhparam part on the Mozilla wiki. Create the DH parameters file with 2048 bit long safe prime: Note that Java 6 doesn’t support DHParams with primes longer than 1024 bit.If you have installed Nginx by following our guide, then support for selectively.But Nginx cannot automatically find out which page to purge and when to purge?Always test your Nginx configuration and then reload it.Nginx out-of-the-box is already performing quite well, and as far as I know, is the only web server with forward secrecy (FS) enabled by default (more on FS support in servers and clients here).If you expect more traffic, increase the cache size accordingly.