Changeset 300 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 31/07/08 20:18:42 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r299 r300 1525 1525 </pre><p id="rfc.section.10.4.p.5"> </p> 1526 1526 <dl class="empty"> 1527 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the re quest.1527 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response. 1528 1528 It is therefore possible for a response to contain header fields for both Location and Content-Location. 1529 1529 </dd> … … 2298 2298 </li> 2299 2299 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119</a>>: "Description of CONNECT should refer to RFC2817" 2300 </li> 2301 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/125">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/125</a>>: "Location Content-Location reference request/response mixup" 2300 2302 </li> 2301 2303 </ul>
Note: See TracChangeset
for help on using the changeset viewer.