asp.net - How much time would be good to set in expire header for a website? -


"Web pages are becoming more complex with more scripts, style sheets, images, and flash There may be a number of HTTP requests to load all the components in order to be loaded from time to time. These components are cacheable by using the explorer header, which avoids unnecessary HTTP requests on subsequent page views. Finally ending with header images. But they can be used on all page components, including scripts, style sheets, and flash.

As written in Yslow . < / P>

My question is, would it be good to set the end time for website with stylesheets, flash headers, javascript, images, PDFs, MS Excel files, PPTs etc.?

I want to set the equal end time

If your page resources (images / CSS / JS) do not usually change and are fixed, you set the ending header as 1 year can do.

Pages for this really depends on the content . If you have a lot of changes in the material, then you should make sure that your expired header is not large or your visitors will get the latest content.

If you want to think about a site, the content changes so often that the header ends on the page is too small. From the header, it seems that they use the maximum age of 60 seconds and the header currently expires at 1 minute.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -