Do I Need a Cache Manifest File If I Have a Cache-Control HTTP Header?

Forum Moderators: phranque

Message Too Old, No Replies

Do I Need a Cache Manifest File If I Have a Cache-Control HTTP Header?

Taryn_S

11:05 am on Oct 31, 2014 (gmt 0)

The HTTP response header for my site includes a Cache-Control "public, max-age=xxxxxxx", an ETag, and a Last-Modified date. If my pages are cached using this header, do I still need a cache manifest file? (Most of my pages will be updated on average once a week.) What experiences have you had using or not using the cache-manifest file?

phranque

1:13 am on Nov 1, 2014 (gmt 0)

welcome to WebmasterWorld, Taryn_S!

the Cache-Control header applies to caching of a requested resource by user agents and proxy servers.
the cache manifest file is specific to an application, not the current web page and its resources.

Taryn_S

1:33 pm on Nov 1, 2014 (gmt 0)

@phranque, thank you. Since my website pages are a requested resource by user agents and not an application, you are saying that I don't need a cache manifest file. I could never quite decide if simple web pages are considered to be an app or not. Maybe one day everything will be written in plain old gray (since there never seems to be a plain old black and white). Appreciate the help. Have a good day.