Changeset 716 for draft-ietf-httpbis/latest
- Timestamp:
- 22/10/09 11:13:10 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r714 r716 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- 14">409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-22"> 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 17, 2010</td>441 <td class="header left">Expires: April 25, 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 14, 2009</td>494 <td class="header right">October 22, 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 17, 2010.</p>518 <p>This Internet-Draft will expire in April 25, 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> … … 1299 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. 1300 1300 </p> 1301 <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 1301 <p id="rfc.section.5.7.p.5"> <a href="p2-semantics.html#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section 6.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> describes how clients may process the Content-Location header field. 1302 </p> 1303 <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 respond 1302 1304 to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple 1303 1305 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>. 1304 1306 </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>1307 <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> 1308 <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> 1307 1309 <div id="rfc.iref.c.10"></div> 1308 1310 <div id="rfc.iref.h.8"></div> … … 2027 2029 <ul> 2028 2030 <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" 2031 </li> 2032 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>>: "Clarify rules for determining what entities a response carries" 2029 2033 </li> 2030 2034 <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" … … 2198 2202 </ul> 2199 2203 </li> 2200 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">4.1</a>, <a class="iref" href="#Part2"><b>9.1</b></a><ul class="ind"> 2204 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">4.1</a>, <a class="iref" href="#rfc.xref.Part2.2">5.7</a>, <a class="iref" href="#Part2"><b>9.1</b></a><ul class="ind"> 2205 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part2.2">5.7</a></li> 2201 2206 <li class="indline1"><em>Section 9.9</em> <a class="iref" href="#rfc.xref.Part2.1">4.1</a></li> 2202 2207 </ul> -
draft-ietf-httpbis/latest/p3-payload.xml
r714 r716 36 36 <!ENTITY deflate-coding "<xref target='Part1' x:rel='#deflate.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 37 37 <!ENTITY gzip-coding "<xref target='Part1' x:rel='#gzip.coding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 38 <!ENTITY response-representation "<xref target='Part2' x:rel='#identifying.response.associated.with.representation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 38 39 ]> 39 40 <?rfc toc="yes" ?> … … 1466 1467 if the desire is to identify the source of that particular 1467 1468 entity. 1469 </t> 1470 <t> 1471 &response-representation; describes how clients may process the Content-Location header field. 1468 1472 </t> 1469 1473 <t> … … 3068 3072 </t> 3069 3073 <t> 3074 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/110"/>: 3075 "Clarify rules for determining what entities a response carries" 3076 </t> 3077 <t> 3070 3078 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/154"/>: 3071 3079 "Content-Location base-setting problems"
Note: See TracChangeset
for help on using the changeset viewer.