Saturday, 15 June 2013

How to use HTTP caching in nginx for html files? -


My current NGC configuration for HTTP content caching is something like this:

  location ~ * \. End of HTML $ $ -1; } Place ~ *. (Css | js | gif | jp? G | png) $ {168 h expired; Add_header Pragma public; Add_header cache-control "public, re-modify, proxy-modify"; }  

As you are seeing that I have disabled caching on HTML files because they are updated quite a bit, now I want to rename the original directory of my HTML files I want to update my configuration with HTML caching using scripts. From:

View / *. Htmls

to

view / randomString / *. Htmls

Therefore, it is basically happening that all my HTML files will be taken from a named name to a directory, which will be generated during each deployment of the web-app. Is this the right approach? Or is there a better way of achieving this goal?

To get a better understanding of how HTTP caching works, it's a good idea to read that section The idea is.

Instead of converting every URL with each release and breaking all the bookmarks, you can try the Anti-Tag Cache Validator (or). You can have your HTML files for al. You have to do NGNA to reincarnate them, all the files you have changed have to change the timestamp.

PS If you actually run a very busy thing, and want to avoid requests for checking with those ETDs. Can you set a long expiration date for your other files and URL to ? Randomstring can be changed by adding , as explained in


No comments:

Post a Comment