Ignore:
Timestamp:
14/09/13 23:59:24 (7 years ago)
Author:
fielding@…
Message:

rephrase misused SHOULDs; addresses #472

File:
1 edited

Legend:

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

    r2394 r2398  
    682682         data is available prior to the response header fields being sent and the digest does not need to be recalculated every time
    683683         a validation request is received. However, if a resource has distinct representations that differ only in their metadata,
    684          such as might occur with content negotiation over media types that happen to share the same data format, then the origin server <em class="bcp14">SHOULD</em> incorporate additional information in the validator to distinguish those representations.
     684         such as might occur with content negotiation over media types that happen to share the same data format, then the origin server
     685         needs to incorporate additional information in the validator to distinguish those representations.
    685686      </p>
    686687      <p id="rfc.section.2.1.p.6">In contrast, a "weak validator" is representation metadata that might not change for every change to the representation data.
Note: See TracChangeset for help on using the changeset viewer.