![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 697 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 25/09/09 14:43:16 (13 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p3-payload.html (modified) (14 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r690 r697 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- 05">409 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-25"> 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 9, 2010</td>441 <td class="header left">Expires: March 29, 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 5, 2009</td>494 <td class="header right">September 25, 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 9, 2010.</p>518 <p>This Internet-Draft will expire in March 29, 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 request-header field "Accept"can be used to specify certain media types which are acceptable for the response. Accept1012 <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. Accept 1013 1013 headers can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of 1014 1014 a request for an in-line image. … … 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 request-header field "Accept-Charset"can be used to indicate what character sets are acceptable for the response. This1114 <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. This 1115 1115 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. … … 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 request-header field "Accept-Encoding"is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) that are acceptable in the response.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>) that 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 request-header field "Accept-Language"is similar to Accept, but restricts the set of natural languages that are preferred1188 <p id="rfc.section.5.4.p.1">The "Accept-Language" request-header field is similar to Accept, but restricts the set of natural languages that are preferred 1189 1189 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. 1190 1190 </p> … … 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 entity-header field "Content-Encoding"is used as a modifier to the media-type. When present, its value indicates what1239 <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 1240 additional content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order 1241 1241 to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document … … 1260 1260 <div id="rfc.iref.h.6"></div> 1261 1261 <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 entity-header field "Content-Language"describes the natural language(s) of the intended audience for the enclosed entity.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 enclosed entity. 1263 1263 Note that this might not be equivalent to all the languages used within the entity-body. 1264 1264 </p> … … 1286 1286 <div id="rfc.iref.h.7"></div> 1287 1287 <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 entity-header field "Content-Location"<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 location1288 <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 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 1290 1290 multiple entities associated with it, and those entities actually have separate locations by which they might be individually … … 1308 1308 <div id="rfc.iref.h.8"></div> 1309 1309 <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a> <a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2> 1310 <p id="rfc.section.5.8.p.1">The entity-header field "Content-MD5", as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body.1310 <p id="rfc.section.5.8.p.1">The "Content-MD5" entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body. 1311 1311 (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious 1312 1312 attacks.) … … 1346 1346 <div id="rfc.iref.h.9"></div> 1347 1347 <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 entity-header field "Content-Type"indicates the media type of the entity-body sent to the recipient or, in the case of1348 <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 of 1349 1349 the HEAD method, the media type that would have been sent had the request been a GET. 1350 1350 </p> … … 1776 1776 <div id="rfc.iref.c.12"></div> 1777 1777 <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2> 1778 <p id="rfc.section.B.1.p.1">The Content-Dispositionresponse-header field has been proposed as a means for the origin server to suggest a default filename1778 <p id="rfc.section.B.1.p.1">The "Content-Disposition" response-header field has been proposed as a means for the origin server to suggest a default filename 1779 1779 if the user requests that the content is saved to a file. This usage is derived from the definition of Content-Disposition 1780 1780 in <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>.
Note: See TracChangeset
for help on using the changeset viewer.
