Changeset 2136 for draft-ietf-httpbis/latest

Timestamp:

20/01/13 02:23:53 (10 years ago)

Author:

fielding@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p4-conditional.html (modified) (1 diff)
• p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p4-conditional.html

@@ -700 +700 @@
          those modifications.
       </p>
-      <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
+      <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
+         those representations have identical representation data. For example, if the origin server sends the same validator for a
+         representation with a gzip content coding applied as it does for a representation with no content coding, then that validator
+         is weak. However, two simultaneous representations might share the same strong validator if they differ only in the representation
+         metadata, such as when two different media types are available for the same representation data.
+      </p>
+      <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
          a server compares two validators. Weak validators are only usable in contexts that do not depend on exact equality of a representation's
          payload body. Strong validators are usable and preferred for all conditional requests, including cache validation, partial

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -274 +274 @@
 </t>
 <t>
+   Likewise, a validator is weak if it is shared by two or more
+   representations of a given resource at the same time, unless those
+   representations have identical representation data. For example, if the
+   origin server sends the same validator for a representation with a gzip
+   content coding applied as it does for a representation with no content
+   coding, then that validator is weak. However, two simultaneous
+   representations might share the same strong validator if they differ only
+   in the representation metadata, such as when two different media types are
+   available for the same representation data.
+</t>
+<t>
    A "use" of a validator occurs when either a client generates a request
    and includes the validator in a precondition or when a server