CODEWITHSUNDEEP
iiscontent-expiration
JohnDoe
JohnDoe

Reputation:

Content Expiration - IIS 6

If I set the content expiration for static files to something like 14 days and I decide to update some files later on, will IIS know to serve the updated files or will the client have to wait until the expiration date?

Or is it the other way around where the browser requests a new file if the modified date is different?

Sometimes I update a file on the server and I have to do a hard refresh (CTRL+F5) to see the difference. Currently I have it to expire after 1 day.

Upvotes: 3

Views: 1893

Answers (2)

Tom Ritter
Tom Ritter

Reputation: 101390

You want ETags

An ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource content at that URL ever changes, a new and different ETag is assigned. Used in this manner ETags are similar to fingerprints, and they can be quickly compared to determine if two versions of a resource are the same or not. [...]

Upvotes: 0

erikkallen
erikkallen

Reputation: 34411

The web browser, and any intermediate proxies, are allowed to cache the page until its expiration date. This means that IIS might not even be aware of the client viewing the page.

Upvotes: 2

Related Questions