![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1630 for draft-ietf-httpbis/experiment/p4-conditional.html
- Timestamp:
- Mar 28, 2012, 9:18:53 AM (8 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/experiment/p4-conditional.html (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/experiment/p4-conditional.html
r1627 r1630 896 896 </div> 897 897 <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a> <a id="example.entity.tag.vs.conneg" href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></h3> 898 <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p 3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (<a href="p3-payload.html#header.accept-encoding" title="ERROR: Anchor 'header.accept-encoding' not found in p3-payload.xml.">Appendix ERROR: Anchor 'header.accept-encoding' in Part3 not found in source file 'p3-payload.xml'.</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>):898 <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 10.13</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>): 899 899 </p> 900 900 <div id="rfc.figure.u.6"></div> … … 1123 1123 as if it were the payload of a 200 response. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields. 1124 1124 </p> 1125 <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 1 1.2</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 2001125 <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200 1126 1126 response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag, Expires, 1127 1127 or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response. … … 1245 1245 <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References 1246 1246 </h2> 1247 <table> 1247 <table> 1248 1248 <tr> 1249 1249 <td class="reference"><b id="Part1">[Part1]</b></td> … … 1254 1254 <td class="reference"><b id="Part2">[Part2]</b></td> 1255 1255 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), March 2012. 1256 </td>1257 </tr>1258 <tr>1259 <td class="reference"><b id="Part3">[Part3]</b></td>1260 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2012.1261 1256 </td> 1262 1257 </tr> … … 1428 1423 </ul> 1429 1424 </li> 1430 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">1.2</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3"> 4.1</a>, <a href="#Part2"><b>8.1</b></a><ul>1425 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">1.2</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">4.1</a>, <a href="#Part2"><b>8.1</b></a><ul> 1431 1426 <li><em>Section 6.1</em> <a href="#rfc.xref.Part2.2">1.2</a></li> 1432 <li><em>Section 11.2</em> <a href="#rfc.xref.Part2.3">4.1</a></li> 1433 </ul> 1434 </li> 1435 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">2.3.3</a>, <a href="#rfc.xref.Part3.2">2.3.3</a>, <a href="#Part3"><b>8.1</b></a><ul> 1436 <li><em>Appendix </em> <a href="#rfc.xref.Part3.1">2.3.3</a></li> 1437 <li><em>Appendix </em> <a href="#rfc.xref.Part3.2">2.3.3</a></li> 1427 <li><em>Section 9</em> <a href="#rfc.xref.Part2.3">2.3.3</a></li> 1428 <li><em>Section 10.2</em> <a href="#rfc.xref.Part2.5">4.1</a></li> 1429 <li><em>Section 10.13</em> <a href="#rfc.xref.Part2.4">2.3.3</a></li> 1438 1430 </ul> 1439 1431 </li>
Note: See TracChangeset
for help on using the changeset viewer.
