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
... Internet standard and represents
a fixed-length subset of that defined by RFC 1123std3 (an update to RFC
822std11(-> 2822prop)). The second format is in common use, but is based on the
...
... The response to a HEAD request may be cachable 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)
response to update any header associated with a previous response
for the same 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 ...
... MUST NOT be performed if the representation does not exist.
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 request containing a Max-
Forwards header field SHOULD check and update its value prior to
forwarding the request. If the received value is zero (0), the
recipient SHOULD NOT forward the request; instead, it SHOULD respond
...