Closed Bug 21569 Opened 25 years ago Closed 25 years ago

Use 'Etag:' header contents for validation

Categories

(Core :: Networking: Cache, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: fur, Assigned: fur)

References

Details

Attachments

(1 file)

HTTP 1.0 provides only the last-modified date to validate that a document has
not changed since last fetched (via use of an If-Modified-Since header added to
the request).  Last-Modified dates, however, only have resolution to one
second, which prevents correct caching of documents that can change more
than once per second.  HTTP 1.1 adds "entity tags" to support correct validation
of such documents and to support caching of documents for which
last-modified-date is not an appropriate validation mechanism.  HTTP 1.1
compliance mandates that clients make use of entity tags for validation if they
are present (via addition of an If-Match header to the request).

See this link for info on the use of entity tags in HTTP validation:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.4
Blocks: 14050
The fix for this bug is pretty trivial.  I've added a patch attachment
containing the fix.
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
The header is actually If-None-Match, not If-Match, so don't blindly apply the
first patch given.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fix checked into nsHTTPChannel.cpp rev 1.115
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: