Hi,
I am a little confused about the best approach.
I have recently updated my site, and don't want old pages loading. But also don't want each and every page to load fresh each time the uses visits it.
I have read that quote"
<meta http-equiv=" pragma" content=" no-cache" >
forces caches (both proxy and browser) to submit the request to the origin server for validation before releasing a cached copy, every time. This is useful to assure that authentication is respected (in combination with public), or to maintain rigid object freshness, without sacrificing all of the benefits of caching. unquote"
So in english, if I use this, it won't always load a new page, only when a new page is required?
If I use
<meta HTTP-EQUIV="Expires" CONTENT="Mon, 01 Jan 1996 23:59:59 GMT"> ie: date in the past:
Do this mean it will always load a new page and never use the cache for items such as navigation bars?
Assistance to best approach would be appreicated.
I am a little confused about the best approach.
I have recently updated my site, and don't want old pages loading. But also don't want each and every page to load fresh each time the uses visits it.
I have read that quote"
<meta http-equiv=" pragma" content=" no-cache" >
forces caches (both proxy and browser) to submit the request to the origin server for validation before releasing a cached copy, every time. This is useful to assure that authentication is respected (in combination with public), or to maintain rigid object freshness, without sacrificing all of the benefits of caching. unquote"
So in english, if I use this, it won't always load a new page, only when a new page is required?
If I use
<meta HTTP-EQUIV="Expires" CONTENT="Mon, 01 Jan 1996 23:59:59 GMT"> ie: date in the past:
Do this mean it will always load a new page and never use the cache for items such as navigation bars?
Assistance to best approach would be appreicated.
