Changeset 698 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 26/09/09 10:09:09 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r697 r698 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-09-2 5">409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-26"> 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: March 29, 2010</td>441 <td class="header left">Expires: March 30, 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">September 2 5, 2009</td>494 <td class="header right">September 26, 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 March 29, 2010.</p>518 <p>This Internet-Draft will expire in March 30, 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> … … 1010 1010 <div id="rfc.iref.h.1"></div> 1011 1011 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="header.accept" href="#header.accept">Accept</a></h2> 1012 <p id="rfc.section.5.1.p.1">The "Accept" request-header field can be used to specify certain media types which are acceptable for the response. Accept1013 headers can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of1014 a requestfor an in-line image.1012 <p id="rfc.section.5.1.p.1">The "Accept" request-header field can be used by user agents to specify response media types that are acceptable. Accept headers 1013 can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request 1014 for an in-line image. 1015 1015 </p> 1016 1016 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a> … … 1112 1112 <div id="rfc.iref.h.2"></div> 1113 1113 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2> 1114 <p id="rfc.section.5.2.p.1">The "Accept-Charset" request-header field can be used to indicate what character sets are acceptable for the response. This1115 field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability1114 <p id="rfc.section.5.2.p.1">The "Accept-Charset" request-header field can be used by user agents to indicate what response character sets are acceptable. 1115 This field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability 1116 1116 to a server which is capable of representing documents in those character sets. 1117 1117 </p> … … 1135 1135 <div id="rfc.iref.h.3"></div> 1136 1136 <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2> 1137 <p id="rfc.section.5.3.p.1">The "Accept-Encoding" request-header field is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) thatare acceptable in the response.1137 <p id="rfc.section.5.3.p.1">The "Accept-Encoding" request-header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) are acceptable in the response. 1138 1138 </p> 1139 1139 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> … … 1186 1186 <div id="rfc.iref.h.4"></div> 1187 1187 <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2> 1188 <p id="rfc.section.5.4.p.1">The "Accept-Language" request-header field is similar to Accept, but restrictsthe set of natural languages that are preferred1189 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>.1188 <p id="rfc.section.5.4.p.1">The "Accept-Language" request-header field can be used by user agents to indicate the set of natural languages that are preferred 1189 in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. 1190 1190 </p> 1191 1191 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a> … … 1237 1237 <div id="rfc.iref.h.5"></div> 1238 1238 <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a> <a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2> 1239 <p id="rfc.section.5.5.p.1">The "Content-Encoding" entity-header field is used as a modifier to the media-type. When present, its value indicates what 1240 additional content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order 1241 to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document 1242 to be compressed without losing the identity of its underlying media type. 1239 <p id="rfc.section.5.5.p.1">The "Content-Encoding" entity-header field indicates what content-codings have been applied to the entity-body, and thus what 1240 decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding 1241 is primarily used to allow a document to be compressed without losing the identity of its underlying media type. 1243 1242 </p> 1244 1243 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> … … 1260 1259 <div id="rfc.iref.h.6"></div> 1261 1260 <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a> <a id="header.content-language" href="#header.content-language">Content-Language</a></h2> 1262 <p id="rfc.section.5.6.p.1">The "Content-Language" entity-header field describes the natural language(s) of the intended audience for the en closed entity.1263 Notethat this might not be equivalent to all the languages used within the entity-body.1261 <p id="rfc.section.5.6.p.1">The "Content-Language" entity-header field describes the natural language(s) of the intended audience for the entity. Note 1262 that this might not be equivalent to all the languages used within the entity-body. 1264 1263 </p> 1265 1264 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a> … … 1286 1285 <div id="rfc.iref.h.7"></div> 1287 1286 <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a> <a id="header.content-location" href="#header.content-location">Content-Location</a></h2> 1288 <p id="rfc.section.5.7.p.1">The "Content-Location" entity-header field <em class="bcp14">MAY</em> be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location 1289 separate from the requested resource's URI. A server <em class="bcp14">SHOULD</em> provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has 1287 <p id="rfc.section.5.7.p.1">The "Content-Location" entity-header field is used to supply a URI for the entity in the message when it is accessible from 1288 a location separate from the requested resource's URI. 1289 </p> 1290 <p id="rfc.section.5.7.p.2">A server <em class="bcp14">SHOULD</em> provide a Content-Location for the variant corresponding to the response entity, especially in the case where a resource has 1290 1291 multiple entities associated with it, and those entities actually have separate locations by which they might be individually 1291 1292 accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. … … 1295 1296 <a href="#header.content-location" class="smpl">Content-Location-v</a> = 1296 1297 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a> 1297 </pre><p id="rfc.section.5.7.p. 3">The value of Content-Location also defines the base URI for the entity.</p>1298 <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 of1298 </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 1299 1300 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 1301 </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 respond1302 <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 1303 to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple 1303 1304 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 1305 </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>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> 1307 1308 <div id="rfc.iref.c.10"></div> 1308 1309 <div id="rfc.iref.h.8"></div> … … 1346 1347 <div id="rfc.iref.h.9"></div> 1347 1348 <h2 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a> <a id="header.content-type" href="#header.content-type">Content-Type</a></h2> 1348 <p id="rfc.section.5.9.p.1">The "Content-Type" entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of1349 the HEAD method, the media type thatwould have been sent had the request been a GET.1349 <p id="rfc.section.5.9.p.1">The "Content-Type" entity-header field indicates the media type of the entity-body. In the case of responses to the HEAD method, 1350 the media type is that which would have been sent had the request been a GET. 1350 1351 </p> 1351 1352 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
Note: See TracChangeset
for help on using the changeset viewer.