1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
update
Click on the red underlined text to get to the source
... a fixed-length subset of that defined by RFC 1123std3 [8] (an update to
RFC 822std11(-> 2822prop) [9 ...
... The response to a HEAD request MAY be cacheable in the sense that the
information contained in the response MAY be used to update a
previously cached entity from that resource. If the new field values
...
... cache entry, the
cache MUST update the entry to reflect any new field values given in
the response.
...
...
Note: this rule allows an origin server to use a 304 (Not
Modified) or a 206 (Partial Content) response to update any header
associated with a previous response for the same entity ...
... entity-tag of the new response matches that of an existing
entry, the new response SHOULD be used to update the header fields of
the existing entry, and the result MUST be returned to the client ...
...
A request intended to update a resource (e.g., a PUT) MAY include an
If-Match header field to signal that the request method ...
... database
gateways, it may be the last-update time stamp of the record. For
virtual objects, it may be the last time the internal state ...
... TRACE or OPTIONS request
containing a Max-Forwards header field MUST check and update its
value prior to forwarding the request. If the received value is zero
(0), the recipient MUST NOT forward the request; instead, it MUST
...