If-Modified-Since
To accommodate client-side caching of documents, the client can use
the If-Modified-Since header with the GET method.
When using this option, the client requests the server to send the
requested information associated with the URL only if it has been
modified since a client-specified time.
If the document was modified, the server will give a status code of 200 and returns the document in the entity-body of its reply. If the document was not modified, the server will give a response code of 304 (Not Modified).
An example If-Modified-Since header might read:
If-Modified-Since: Fri, 02-Jun-95 02:42:43 GMT
If the server returns a code of 304, the document has not been
modified since the specified time. The client can use the cached
version of the document. If the document is newer, the server will
send it along with a 200 (OK) code. Servers may also include a
Last-Modified header
with the document, to let the user know when the last change was made
to the document.
Another related client header is
If-Unmodified-Since,
which says to only send the document if it hasn’t been changed
since the specified date. This is useful for ensuring that the data
is exactly the way you wanted it to be. For example, if you GET a
document from a server, make changes in a publishing tool, and PUT it
back to the server, you can use the
If-Unmodified-Since header to verify that the
changes you made are accepted by the server only if the previous one
you were looking at is still there.
If the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access