Changeset 1138 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 22/02/11 20:45:17 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r1120 r1138 353 353 } 354 354 @bottom-center { 355 content: "Expires August 2 1, 2011";355 content: "Expires August 26, 2011"; 356 356 } 357 357 @bottom-right { … … 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2011-02- 17">404 <meta name="dct.issued" scheme="ISO8601" content="2011-02-22"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.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."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: August 2 1, 2011</td>430 <td class="left">Expires: August 26, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 485 485 <tr> 486 486 <td class="left"></td> 487 <td class="right">February 17, 2011</td>487 <td class="right">February 22, 2011</td> 488 488 </tr> 489 489 </tbody> … … 511 511 in progress”. 512 512 </p> 513 <p>This Internet-Draft will expire on August 2 1, 2011.</p>513 <p>This Internet-Draft will expire on August 26, 2011.</p> 514 514 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 515 515 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 857 857 header fields". The following payload header fields are defined by HTTP/1.1: 858 858 </p> 859 <div id="rfc.figure.u.12"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a> 860 <a href="#header.content-md5" class="smpl">Content-MD5</a> ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 6.8</a> 861 <a href="#abnf.dependencies" class="smpl">Content-Range</a> ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> 862 </pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h2> 859 <div id="rfc.table.u.1"> 860 <table class="tt full left" cellpadding="3" cellspacing="0"> 861 <thead> 862 <tr> 863 <th>Header Field Name</th> 864 <th>Defined in...</th> 865 </tr> 866 </thead> 867 <tbody> 868 <tr> 869 <td class="left">Content-Length</td> 870 <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td> 871 </tr> 872 <tr> 873 <td class="left">Content-MD5</td> 874 <td class="left"><a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 6.8</a></td> 875 </tr> 876 <tr> 877 <td class="left">Content-Range</td> 878 <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td> 879 </tr> 880 </tbody> 881 </table> 882 </div> 883 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="payload.body" href="#payload.body">Payload Body</a></h2> 863 884 <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 864 885 safe and proper transfer of the message. … … 885 906 </p> 886 907 <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p> 887 <div id="rfc.figure.u.13"></div><pre class="inline"> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 6.5</a> 888 <a href="#header.content-language" class="smpl">Content-Language</a> ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 6.6</a> 889 <a href="#header.content-location" class="smpl">Content-Location</a> ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 6.7</a> 890 <a href="#header.content-type" class="smpl">Content-Type</a> ; <a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section 6.9</a> 891 <a href="#abnf.dependencies" class="smpl">Expires</a> ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> 892 <a href="#abnf.dependencies" class="smpl">Last-Modified</a> ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> 893 </pre><h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="representation.data" href="#representation.data">Representation Data</a></h2> 908 <div id="rfc.table.u.2"> 909 <table class="tt full left" cellpadding="3" cellspacing="0"> 910 <thead> 911 <tr> 912 <th>Header Field Name</th> 913 <th>Defined in...</th> 914 </tr> 915 </thead> 916 <tbody> 917 <tr> 918 <td class="left">Content-Encoding</td> 919 <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 6.5</a></td> 920 </tr> 921 <tr> 922 <td class="left">Content-Language</td> 923 <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 6.6</a></td> 924 </tr> 925 <tr> 926 <td class="left">Content-Location</td> 927 <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 6.7</a></td> 928 </tr> 929 <tr> 930 <td class="left">Content-Type</td> 931 <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section 6.9</a></td> 932 </tr> 933 <tr> 934 <td class="left">Expires</td> 935 <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 936 </tr> 937 <tr> 938 <td class="left">Last-Modified</td> 939 <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td> 940 </tr> 941 </tbody> 942 </table> 943 </div> 944 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="representation.data" href="#representation.data">Representation Data</a></h2> 894 945 <p id="rfc.section.4.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred 895 946 to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by … … 899 950 a two-layer, ordered encoding model: 900 951 </p> 901 <div id="rfc.figure.u.1 4"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) )952 <div id="rfc.figure.u.12"></div><pre class="text"> representation-data := Content-Encoding( Content-Type( bits ) ) 902 953 </pre><p id="rfc.section.4.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload 903 954 body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown … … 1001 1052 a request for an in-line image. 1002 1053 </p> 1003 <div id="rfc.figure.u.1 5"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></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>1054 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></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> 1004 1055 <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] ) 1005 1056 … … 1025 1076 </div> 1026 1077 <p id="rfc.section.6.1.p.6">The example</p> 1027 <div id="rfc.figure.u.1 6"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic1078 <div id="rfc.figure.u.14"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 1028 1079 </pre><p id="rfc.section.6.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in 1029 1080 quality". … … 1034 1085 </p> 1035 1086 <p id="rfc.section.6.1.p.10">A more elaborate example is</p> 1036 <div id="rfc.figure.u.1 7"></div><pre class="text"> Accept: text/plain; q=0.5, text/html,1087 <div id="rfc.figure.u.15"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 1037 1088 text/x-dvi; q=0.8, text/x-c 1038 1089 </pre><p id="rfc.section.6.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then … … 1042 1093 to a given type, the most specific reference has precedence. For example, 1043 1094 </p> 1044 <div id="rfc.figure.u.1 8"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */*1095 <div id="rfc.figure.u.16"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1045 1096 </pre><p id="rfc.section.6.1.p.15">have the following precedence: </p> 1046 1097 <ol> … … 1053 1104 which matches that type. For example, 1054 1105 </p> 1055 <div id="rfc.figure.u.1 9"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,1106 <div id="rfc.figure.u.17"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1056 1107 text/html;level=2;q=0.4, */*;q=0.5 1057 1108 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p> 1058 <div id="rfc.table.u. 1">1109 <div id="rfc.table.u.3"> 1059 1110 <table class="tt full left" cellpadding="3" cellspacing="0"> 1060 1111 <thead> … … 1102 1153 to a server which is capable of representing documents in those character sets. 1103 1154 </p> 1104 <div id="rfc.figure.u. 20"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>1155 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a> 1105 1156 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> 1106 1157 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) … … 1109 1160 example is 1110 1161 </p> 1111 <div id="rfc.figure.u. 21"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.81162 <div id="rfc.figure.u.19"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1112 1163 </pre><p id="rfc.section.6.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is 1113 1164 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 1124 1175 <p id="rfc.section.6.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. 1125 1176 </p> 1126 <div id="rfc.figure.u.2 2"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>1177 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> 1127 1178 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> 1128 1179 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = … … 1132 1183 </p> 1133 1184 <p id="rfc.section.6.3.p.4">Examples of its use are:</p> 1134 <div id="rfc.figure.u.2 3"></div><pre class="text"> Accept-Encoding: compress, gzip1185 <div id="rfc.figure.u.21"></div><pre class="text"> Accept-Encoding: compress, gzip 1135 1186 Accept-Encoding: 1136 1187 Accept-Encoding: * … … 1176 1227 in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. 1177 1228 </p> 1178 <div id="rfc.figure.u.2 4"></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-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>1229 <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-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a> 1179 1230 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> 1180 1231 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = … … 1185 1236 languages specified by that range. The quality value defaults to "q=1". For example, 1186 1237 </p> 1187 <div id="rfc.figure.u.2 5"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.71238 <div id="rfc.figure.u.23"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1188 1239 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>) 1189 1240 </p> … … 1214 1265 is primarily used to allow a representation to be compressed without losing the identity of its underlying media type. 1215 1266 </p> 1216 <div id="rfc.figure.u.2 6"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></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>1267 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></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> 1217 1268 <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a> 1218 1269 </pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 2.2</a>. An example of its use is 1219 1270 </p> 1220 <div id="rfc.figure.u.2 7"></div><pre class="text"> Content-Encoding: gzip1271 <div id="rfc.figure.u.25"></div><pre class="text"> Content-Encoding: gzip 1221 1272 </pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding 1222 1273 and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control … … 1235 1286 that this might not be equivalent to all the languages used within the representation. 1236 1287 </p> 1237 <div id="rfc.figure.u.2 8"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></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>1288 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></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> 1238 1289 <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a> 1239 1290 </pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the … … 1241 1292 field is 1242 1293 </p> 1243 <div id="rfc.figure.u.2 9"></div><pre class="text"> Content-Language: da1294 <div id="rfc.figure.u.27"></div><pre class="text"> Content-Language: da 1244 1295 </pre><p id="rfc.section.6.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean 1245 1296 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1249 1300 simultaneously in the original Maori and English versions, would call for 1250 1301 </p> 1251 <div id="rfc.figure.u. 30"></div><pre class="text"> Content-Language: mi, en1302 <div id="rfc.figure.u.28"></div><pre class="text"> Content-Language: mi, en 1252 1303 </pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple 1253 1304 linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly … … 1263 1314 would contain the same representation that is enclosed as payload in this message. 1264 1315 </p> 1265 <div id="rfc.figure.u. 31"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>1316 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a> 1266 1317 <a href="#header.content-location" class="smpl">Content-Location-v</a> 1267 1318 <a href="#header.content-location" class="smpl">Content-Location-v</a> = … … 1308 1359 body in transit, but is not proof against malicious attacks. 1309 1360 </p> 1310 <div id="rfc.figure.u.3 2"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>1361 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a> 1311 1362 <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = <base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>> 1312 1363 </pre><p id="rfc.section.6.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the payload body. Only origin servers or user … … 1342 1393 the media type is that which would have been sent had the request been a GET. 1343 1394 </p> 1344 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></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>1395 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></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> 1345 1396 <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a> 1346 1397 </pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 2.3</a>. An example of the field is 1347 1398 </p> 1348 <div id="rfc.figure.u.3 4"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-41399 <div id="rfc.figure.u.32"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1349 1400 </pre><p id="rfc.section.6.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section 4.2</a>. 1350 1401 </p> … … 1710 1761 environments. 1711 1762 </p> 1712 <div id="rfc.figure.u.3 5"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>1763 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a> 1713 1764 <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 1714 1765 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this … … 1770 1821 </p> 1771 1822 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 1772 <div id="rfc.figure.u.3 6"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v1823 <div id="rfc.figure.u.34"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v 1773 1824 <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v 1774 1825 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q=" … … 1838 1889 1839 1890 <a href="#core.rules" class="smpl">word</a> = <word, defined in [Part1], Section 1.2.2> 1840 </pre> <div id="rfc.figure.u.3 7"></div>1891 </pre> <div id="rfc.figure.u.35"></div> 1841 1892 <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used 1842 1893 ; Accept-Charset defined but not used
Note: See TracChangeset
for help on using the changeset viewer.