Ignore:
Timestamp:
05/11/13 01:09:07 (7 years ago)
Author:
fielding@…
Message:

clarify that content coding example is about strong entity tags; addresses #518

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2474 r2475  
    916916
    917917<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
    918                   <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
    919                      from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
    920                      (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
     918                  <p><b>Note:</b> Content codings are a property of the representation data, so a strong entity-tag for a content-encoded representation has
     919                     to be distinct from the entity tag of an unencoded representation to prevent potential conflicts during cache updates and
     920                     range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
    921921                  </p>
    922922               </div>
Note: See TracChangeset for help on using the changeset viewer.