Changeset 712
- Timestamp:
- 08/10/09 10:01:43 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r704 r712 407 407 <meta name="DC.Creator" content="Reschke, J. F."> 408 408 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-0 2">409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-08"> 410 410 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 411 411 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 439 439 </tr> 440 440 <tr> 441 <td class="header left">Expires: April 5, 2010</td>441 <td class="header left">Expires: April 11, 2010</td> 442 442 <td class="header right">HP</td> 443 443 </tr> … … 492 492 <tr> 493 493 <td class="header left"></td> 494 <td class="header right">October 2, 2009</td>494 <td class="header right">October 8, 2009</td> 495 495 </tr> 496 496 </table> … … 516 516 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 517 517 </p> 518 <p>This Internet-Draft will expire in April 5, 2010.</p>518 <p>This Internet-Draft will expire in April 11, 2010.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1296 1296 <a href="#header.content-location" class="smpl">Content-Location-v</a> = 1297 1297 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 1298 </pre><p id="rfc.section.5.7.p.4">The value of Content-Location also defines the base URI for the entity.</p> 1299 <p id="rfc.section.5.7.p.5">The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of 1298 </pre><p id="rfc.section.5.7.p.4">The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of 1300 1299 the resource corresponding to this particular entity at the time of the request. Future requests <em class="bcp14">MAY</em> specify the Content-Location URI as the request-target if the desire is to identify the source of that particular entity. 1301 1300 </p> 1302 <p id="rfc.section.5.7.p. 6">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond1301 <p id="rfc.section.5.7.p.5">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond 1303 1302 to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple 1304 1303 entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. 1305 1304 </p> 1306 <p id="rfc.section.5.7.p. 7">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p>1307 <p id="rfc.section.5.7.p. 8">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p>1305 <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p> 1306 <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p> 1308 1307 <div id="rfc.iref.c.10"></div> 1309 1308 <div id="rfc.iref.h.8"></div> … … 1817 1816 <p id="rfc.section.C.2.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section 2.1</a>) 1818 1817 </p> 1819 <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.5</a>) 1818 <p id="rfc.section.C.2.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 5.7</a>) 1819 </p> 1820 <p id="rfc.section.C.2.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.5</a>) 1820 1821 </p> 1821 1822 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 2024 2025 <ul> 2025 2026 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>>: "Updated reference for language tags" 2027 </li> 2028 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/154">http://tools.ietf.org/wg/httpbis/trac/ticket/154</a>>: "Content-Location base-setting problems" 2026 2029 </li> 2027 2030 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>>: "Content Sniffing" … … 2071 2074 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 2072 2075 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 2073 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a> </li>2076 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C.2</a></li> 2074 2077 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.10"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 2075 2078 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> … … 2150 2153 <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 2151 2154 <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 2152 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a> </li>2155 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C.2</a></li> 2153 2156 <li class="indline1">Content-MD5 <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 2154 2157 <li class="indline1">Content-Type <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r704 r712 1459 1459 <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref> 1460 1460 </artwork></figure> 1461 <t>1462 The value of Content-Location also defines the base URI for the1463 entity.1464 </t>1465 1461 <t> 1466 1462 The Content-Location value is not a replacement for the original … … 2750 2746 </t> 2751 2747 <t> 2748 Remove base URI setting semantics for Content-Location due to poor 2749 implementation support. 2750 (<xref target="header.content-location"/>) 2751 </t> 2752 <t> 2752 2753 Remove reference to non-existant identity transfer-coding value tokens. 2753 2754 (<xref target="no.content-transfer-encoding"/>) … … 3075 3076 </t> 3076 3077 <t> 3078 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/154"/>: 3079 "Content-Location base-setting problems" 3080 </t> 3081 <t> 3077 3082 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/155"/>: 3078 3083 "Content Sniffing"
Note: See TracChangeset
for help on using the changeset viewer.