Friday, March 26, 2010

Learning Cache Control

Update 3/26/2010 6:50 p.m.
  • The cache-control had been set to private by the host (thank you to http://www.seoconsultants.com/tools/headers for the great tool that I've been using for a few years now)
  • I added <% Response.CacheControl="public" %> to change it to public
  • Then I added <% Response.ExpiresAbsolute="5/31/2010" %>
  • According to the header check
  • #1 Server Response: http://www.uticahousekeeping.com/
    HTTP Status Code: HTTP/1.1 200 OK
    Cache-Control: public
    Date: Fri, 26 Mar 2010 22:45:38 GMT
    Content-Length: 3028
    Content-Type: text/html
    Expires: Mon, 31 May 2010 05:00:00 GMT
    Server: Microsoft-IIS/6.0
    X-Powered-By: ASP.NET
    MicrosoftOfficeWebServer: 5.0_Pub
    Set-Cookie: ASPSESSIONIDQCBDBCQQ=GFGHLLJCGKPEPJHJEJFBPNBG; path=/
But Google's PageSpeed tool still says:
The following resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers. Specify an expiration at least one month in the future for resources that should be cached, and an expiration in the past for resources that should not be cached:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one month in the future for the following resources:
Non-scoring information
The following resources are explicitly non-cacheable. Consider making them cacheable if possible:

So what am I missing? How do I fix this? Can anybody help me?

According to Google's PageSpeed tool:
The following resources are missing a cache expiration. Resources that do not specify an expiration may not be cached by browsers. Specify an expiration at least one month in the future for resources that should be cached, and an expiration in the past for resources that should not be cached:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one month in the future for the following resources:
Non-scoring information
The following resources are explicitly non-cacheable. Consider making them cacheable if possible:
So, I've searched and searched and found the following tutorials:

 
Using <% Response.CacheControl="public" %> didn't change the error in PageSpeed
Using <% Response.ExpiresAbsolute=#May 31,1996 13:30:15 GMT# %> caused an ASP error so the page wouldn't show up at all
Using <% Response.Expires=1440 %> didn't change the error in PageSpeed

 
When I contacted my website hosting company, IXWebHosting, their response was:
You are not able to change this value on a shared hosting environment.

 
Not the answer I was looking for...

 
Can anybody help??

No comments: