Geek asks and answers

YSlow recommendations. In IIS, why not enable Enable Content Expiration by default in

I just ran yslow against my website and I had a question about Expiry headers: YSlow gave me: Frade F on Add Expires headers. There are 20 static components with no future date. These are all css or js files.

Right now, when I go to IIS (6.0) and go to the http headers tab, Enable Content Expiration is not checked. From reading this , it looks like it's right, since the browser will cache the content. Therefore, I am embarrassed why complaining plaintively. Also, it looks like browsers will cache this date-modified data anyway, so is all this pointless ??

So if customization is not a problem, why is it not the default?

Someone might clarify.

+3
source share
2 answers

There is no contradiction here. What you need to do is set the expiration of the content in folders containing static content . For example, your images, css and script folders. You can set folder-based content expiration in IIS and other web servers.

+2
source

, "" ; , yslow, , . , ... Expires - , , .

.

0

More articles:


All Articles