Source: https://trac.ietf.org/trac/httpbis/export/1431/draft-ietf-httpbis/latest/p4-conditional.html
Timestamp: 2019-12-07 09:54:11
Document Index: 12454465

Matched Legal Cases: ['art1', 'art3', 'art3', 'art1', 'art1', 'art1', 'art1', 'art 1', 'art5', 'art 5', 'art1', 'art3']

Expires: March 4, 2012 J. Mogul
C.12 Since draft-ietf-httpbis-p4-conditional-10
C.13 Since draft-ietf-httpbis-p4-conditional-11
C.14 Since draft-ietf-httpbis-p4-conditional-12
C.15 Since draft-ietf-httpbis-p4-conditional-13
C.16 Since draft-ietf-httpbis-p4-conditional-14
C.17 Since draft-ietf-httpbis-p4-conditional-15
C.18 Since draft-ietf-httpbis-p4-conditional-16
The ABNF rules below are defined in [Part1] :
Consider a resource that is subject to content negotiation (Section 5 of [Part3] ), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (Section 6.3 of [Part3] ):
Note: Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings (Section 6.2 of [Part1] ) apply only during message transfer and do not require distinct entity-tags.
A 304 response MUST include a Date header field (Section 9.3 of [Part1] ) unless its omission is required by Section 9.3.1 of [Part1] . If a 200 response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag, Expires, Last-Modified, or Vary, then those same header fields MUST be sent in a 304 response.
[Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., and J. Reschke, Ed., “HTTP/1.1, part 1: URIs, Connections, and Message Parsing”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), September 2011.
[Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., and J. Reschke, Ed., “HTTP/1.1, part 5: Range Requests and Partial Responses”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), September 2011.
<http://tools.ietf.org/wg/httpbis/trac/ticket/89>: "If-* and entities"
<http://tools.ietf.org/wg/httpbis/trac/ticket/101>: "Definition of validator weakness"
<http://tools.ietf.org/wg/httpbis/trac/ticket/269>: "ETags and Quotes"
<http://tools.ietf.org/wg/httpbis/trac/ticket/304>: "If-Range should be listed when dicussing contexts where L-M can be considered strong"
ETag header field 2.3, 5.2
ETag 2.3, 5.2
Part1 1.2, 1.2, 1.2, 1.2, 1.2, 2.3.3, 4.1, 4.1, 6, 7, 8.1
Section 1.2.2 1.2
Section 3.2.3 1.2
Section 6.1 1.2
Section 6.2 2.3.3
Section 9.3 4.1
Section 9.3.1 4.1
Section 12 7
Part3 2.3.3, 2.3.3, 8.1
Section 6.3 2.3.3