web.config power
So I have been trying to figure out how make sure that when we deploy projects out to production that we don't have to do as much setup, since all of our servers are IIS. I figured I would look at using web.configs more and what I can really do with them.
So inside each of our assets folders where we keep the images, css, and javascript files I created a web.config that contains the following.
Now the urlCompression node will turn on the gziping of files that are static since I really don't need it to compress the dynamic files at the moment.
The staticContent will allow tell the content to be cached by the client browser up to 30 days.
0 responses to “web.config power”