Changeset 2579 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

24/01/14 10:19:57 (9 years ago)

Author:

fielding@…

Message:

avoid repeating (and contradicting) the requirements and description already in the section on Vary

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -1278 +1278 @@
                   the user agent's preferences is better than sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response.
                </p>
-               <p id="rfc.section.3.4.1.p.5">An origin server <em class="bcp14">MAY</em> generate a <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.1.4</a>) in a response if it wishes to indicate what fields of request information were used in its selection algorithm. This informs
-                  recipients that sending more information might be useful in future requests. It also warns caches not to reuse that response,
-                  until reconfirmed by the origin server, for a request that contains different information in those fields.
+               <p id="rfc.section.3.4.1.p.5">A <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.1.4</a>) is often sent in a response subject to proactive negotiation to indicate what parts of the request information were used
+                  in the selection algorithm.
                </p>
             </div>