Closed
Bug 21572
Opened 25 years ago
Closed 25 years ago
Implement HTTP 1.1 must-revalidate support
Categories
(Core :: Networking: Cache, defect, P3)
Core
Networking: Cache
Tracking
()
RESOLVED
FIXED
People
(Reporter: fur, Assigned: fur)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
From the HTTP 1.1 spec:
Because a cache MAY be configured to ignore a server's
specified expiration time, and because a client request MAY
include a max-stale directive (which has a similar effect),
the protocol also includes a mechanism for the origin server
to require revalidation of a cache entry on any subsequent
use. When the must-revalidate directive is present in a
response received by a cache, that cache MUST NOT use the
entry after it becomes stale to respond to a subsequent
request without first revalidating it with the origin
server. (I.e., the cache MUST do an end-to-end revalidation
every time, if, based solely on the origin server's Expires
or max-age value, the cached response is stale.) The
must-revalidate directive is necessary to support reliable
operation for certain protocol features. In all
circumstances an HTTP/1.1 cache MUST obey the
must-revalidate directive; in particular, if the cache
cannot reach the origin server for any reason, it MUST
generate a 504 (Gateway Timeout) response. Servers SHOULD
send the must-revalidate directive if and only if failure to
revalidate a request on the entity could result in incorrect
operation, such as a silently unexecuted financial
transaction. Recipients MUST NOT take any automated action
that violates this directive, and MUST NOT automatically
provide an unvalidated copy of the entity if revalidation
fails. Although this is not recommended, user agents
operating under severe connectivity constraints MAY violate
this directive but, if so, MUST explicitly warn the user
that an unvalidated response has been provided. The warning
MUST be provided on each unvalidated access, and SHOULD
require explicit user confirmation.
Assignee | ||
Comment 1•25 years ago
|
||
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
Assignee | ||
Comment 3•25 years ago
|
||
Fix checked into nsHTTPChannel.cpp rev 1.115
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•25 years ago
|
||
Fix checked into nsHTTPChannel.cpp rev 1.115
You need to log in
before you can comment on or make changes to this bug.
Description
•