Ignore:
Timestamp:
Jan 19, 2013, 6:23:53 PM (7 years ago)
Author:
fielding@…
Message:

note that simultaneous use of the same validator for different representation data would also make it weak; addresses #401

File:
1 edited

Legend:

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

    r2133 r2136  
    700700         those modifications.
    701701      </p>
    702       <p id="rfc.section.2.1.p.8">A "use" of a validator occurs when either a client generates a request and includes the validator in a precondition or when
     702      <p id="rfc.section.2.1.p.8">Likewise, a validator is weak if it is shared by two or more representations of a given resource at the same time, unless
     703         those representations have identical representation data. For example, if the origin server sends the same validator for a
     704         representation with a gzip content coding applied as it does for a representation with no content coding, then that validator
     705         is weak. However, two simultaneous representations might share the same strong validator if they differ only in the representation
     706         metadata, such as when two different media types are available for the same representation data.
     707      </p>
     708      <p id="rfc.section.2.1.p.9">A "use" of a validator occurs when either a client generates a request and includes the validator in a precondition or when
    703709         a server compares two validators. Weak validators are only usable in contexts that do not depend on exact equality of a representation's
    704710         payload body. Strong validators are usable and preferred for all conditional requests, including cache validation, partial
Note: See TracChangeset for help on using the changeset viewer.