Terry wrote:
> Just to further prove its not being cached, here's the header:
>
> GET /Pic.aspx?i=db1edbcd-2375-4bae-b33f-a53ced60deed HTTP/1.1
> Host: foo.domain.com
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
> rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
> Accept: image/png,image/*;q=0.8,*/*;q=0.5
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
> Referer: https://foo.domain.com/
> Cookie: com.domain.foo_SessionID=kua4ew454kjodsjpdlojdu55
> Cache-Control: max-age=0
>
This is a request header (GET, Host:, User-Agent, etc.), which specifies
the retrieved object should NOT come from a cache (Cache-Control:
max-age=0). The response to this request will not be returned by an
(RFC compliant) intermediary cache. The response to that same request,
minus the Cache-Control header would better show if the object is cacheable.
Chris
Received on Thu Aug 13 2009 - 21:51:16 MDT
This archive was generated by hypermail 2.2.0 : Fri Aug 14 2009 - 12:00:02 MDT