I'm just curious -- is it worthwhile to do all this work for static files when you could just set the expiration date way in the future and try to only serve those files once?
Jamie
· 1 year ago
Thanks for the comment Jamie!
Setting a far in the future expiration date for existing static files would keep them from being downloaded a second time, but what about newly added static file? For example, a site that is frequently updated with new images would benefit from those images being served from NginX.
Also, setting the expiration date ahead is good for users who have previously visited your site, but what about first time users? Or users who have cleared out their temporary internet files? What if the site was dugg? You would be receiving a large spike in traffic from users who need to download all that static content. In those cases, your performance will benefit greatly from NginX's ability to quickly serve static files.
Warren
· 1 year ago
I've put nginx in front of apache2 and it all works just fine. The only thing is that I can't really tell if nginx is actually serving up the static files ? Thanks for the article by the way !
Vito Botta
· 5 months ago
Hi, I found this post by Googling. I've got a similar setup working, with nginx as front end to apache for a Wordpress blog (among other things). It is working fine for the static files such as images, stylesheets, and javascripts, but I am also trying to make nginx serve directly the static html files created by WP Super Cache. Have you got any tips to get this working? Thanks in advance
moltar
· 4 weeks ago
@Vito: i'm pretty sure that is impossible, because web server is unaware of the static HTML files.
All Comments
Setting a far in the future expiration date for existing static files would keep them from being downloaded a second time, but what about newly added static file? For example, a site that is frequently updated with new images would benefit from those images being served from NginX.
Also, setting the expiration date ahead is good for users who have previously visited your site, but what about first time users? Or users who have cleared out their temporary internet files? What if the site was dugg? You would be receiving a large spike in traffic from users who need to download all that static content. In those cases, your performance will benefit greatly from NginX's ability to quickly serve static files.
I've got a similar setup working, with nginx as front end to apache for a Wordpress blog (among other things).
It is working fine for the static files such as images, stylesheets, and javascripts, but I am also trying to make nginx serve directly the static html files created by WP Super Cache.
Have you got any tips to get this working?
Thanks in advance