Does this cache header even make sense?

Discussion in 'Server Operation' started by talkingnews, Mar 11, 2011.

  1. talkingnews

    talkingnews New Member

    Just a quick random question:

    Here's a header:

    11/03/2011 15:25:56.005 Cache-Control: no-cache, x-wms-content-size=4129462, max-age=86399, user-public, must-revalidate, proxy-public, proxy-revalidate

    Doesn't some of this cancel each other out? I'm trying to work out why my browser/ISP is getting a cached version. Provider says it shouldn't be caching, but it is, and surely user-public, proxy-public cancels out no-cache?

    Or at least, that's what I think from having read the docs.
     
  2. falko

    falko Super Moderator ISPConfig Developer

    I'm not sure about user-public and proxy-public, but max-age=86399 tells browsers to cache content for 86399 seconds (however, not all browsers support max-age).

    If you don't want your content to be cached, remove the max-age; in addition to that, set an Expires header with a date in the past.
     

Share This Page