Use 'Etag:' header contents for validation

VERIFIED FIXED

Status

()

Core
Networking: Cache
P3
normal
VERIFIED FIXED
18 years ago
17 years ago

People

(Reporter: Scott Furman, Assigned: Scott Furman)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

18 years ago
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
(Assignee)

Updated

18 years ago
Blocks: 14050
(Assignee)

Comment 1

18 years ago
Created attachment 3432 [details] [diff] [review]
Implementation of entity-tag validation
(Assignee)

Comment 2

18 years ago
The fix for this bug is pretty trivial.  I've added a patch attachment
containing the fix.

Comment 3

18 years ago
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
(Assignee)

Comment 4

18 years ago
The header is actually If-None-Match, not If-Match, so don't blindly apply the
first patch given.
(Assignee)

Updated

18 years ago
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

18 years ago
Fix checked into nsHTTPChannel.cpp rev 1.115

Comment 6

17 years ago
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.