source: draft-ietf-httpbis/latest/p3-payload.html @ 1174

Last change on this file since 1174 was 1174, checked in by fielding@…, 9 years ago

generate HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 193.2 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 3: Message Payload and Content Negotiation</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
28}
29cite {
30  font-style: normal;
31}
32div.note {
33  margin-left: 2em;
34}
35dd {
36  margin-right: 2em;
37}
38dl {
39  margin-left: 2em;
40}
41
42ul.empty {
43  list-style-type: none;
44}
45ul.empty li {
46  margin-top: .5em;
47}
48dl p {
49  margin-left: 0em;
50}
51dt {
52  margin-top: .5em;
53}
54h1 {
55  font-size: 14pt;
56  line-height: 21pt;
57  page-break-after: avoid;
58}
59h1.np {
60  page-break-before: always;
61}
62h1 a {
63  color: #333333;
64}
65h2 {
66  font-size: 12pt;
67  line-height: 15pt;
68  page-break-after: avoid;
69}
70h3, h4, h5, h6 {
71  font-size: 10pt;
72  page-break-after: avoid;
73}
74h2 a, h3 a, h4 a, h5 a, h6 a {
75  color: black;
76}
77img {
78  margin-left: 3em;
79}
80li {
81  margin-left: 2em;
82  margin-right: 2em;
83}
84ol {
85  margin-left: 2em;
86  margin-right: 2em;
87}
88ol.la {
89  list-style-type: lower-alpha;
90}
91ol.ua {
92  list-style-type: upper-alpha;
93}
94ol p {
95  margin-left: 0em;
96}
97p {
98  margin-left: 2em;
99  margin-right: 2em;
100}
101pre {
102  margin-left: 3em;
103  background-color: lightyellow;
104  padding: .25em;
105}
106pre.text2 {
107  border-style: dotted;
108  border-width: 1px;
109  background-color: #f0f0f0;
110  width: 69em;
111}
112pre.inline {
113  background-color: white;
114  padding: 0em;
115}
116pre.text {
117  border-style: dotted;
118  border-width: 1px;
119  background-color: #f8f8f8;
120  width: 69em;
121}
122pre.drawing {
123  border-style: solid;
124  border-width: 1px;
125  background-color: #f8f8f8;
126  padding: 2em;
127}
128table {
129  margin-left: 2em;
130}
131table.tt {
132  vertical-align: top;
133}
134table.full {
135  border-style: outset;
136  border-width: 1px;
137}
138table.headers {
139  border-style: outset;
140  border-width: 1px;
141}
142table.tt td {
143  vertical-align: top;
144}
145table.full td {
146  border-style: inset;
147  border-width: 1px;
148}
149table.tt th {
150  vertical-align: top;
151}
152table.full th {
153  border-style: inset;
154  border-width: 1px;
155}
156table.headers th {
157  border-style: none none inset none;
158  border-width: 1px;
159}
160table.left {
161  margin-right: auto;
162}
163table.right {
164  margin-left: auto;
165}
166table.center {
167  margin-left: auto;
168  margin-right: auto;
169}
170caption {
171  caption-side: bottom;
172  font-weight: bold;
173  font-size: 9pt;
174  margin-top: .5em;
175}
176
177table.header {
178  border-spacing: 1px;
179  width: 95%;
180  font-size: 10pt;
181  color: white;
182}
183td.top {
184  vertical-align: top;
185}
186td.topnowrap {
187  vertical-align: top;
188  white-space: nowrap; 
189}
190table.header td {
191  background-color: gray;
192  width: 50%;
193}
194table.header a {
195  color: white;
196}
197td.reference {
198  vertical-align: top;
199  white-space: nowrap;
200  padding-right: 1em;
201}
202thead {
203  display:table-header-group;
204}
205ul.toc, ul.toc ul {
206  list-style: none;
207  margin-left: 1.5em;
208  margin-right: 0em;
209  padding-left: 0em;
210}
211ul.toc li {
212  line-height: 150%;
213  font-weight: bold;
214  font-size: 10pt;
215  margin-left: 0em;
216  margin-right: 0em;
217}
218ul.toc li li {
219  line-height: normal;
220  font-weight: normal;
221  font-size: 9pt;
222  margin-left: 0em;
223  margin-right: 0em;
224}
225li.excluded {
226  font-size: 0pt;
227}
228ul p {
229  margin-left: 0em;
230}
231ul.ind, ul.ind ul {
232  list-style: none;
233  margin-left: 1.5em;
234  margin-right: 0em;
235  padding-left: 0em;
236  page-break-before: avoid;
237}
238ul.ind li {
239  font-weight: bold;
240  line-height: 200%;
241  margin-left: 0em;
242  margin-right: 0em;
243}
244ul.ind li li {
245  font-weight: normal;
246  line-height: 150%;
247  margin-left: 0em;
248  margin-right: 0em;
249}
250.avoidbreak {
251  page-break-inside: avoid;
252}
253.bcp14 {
254  font-style: normal;
255  text-transform: lowercase;
256  font-variant: small-caps;
257}
258.comment {
259  background-color: yellow;
260}
261.center {
262  text-align: center;
263}
264.error {
265  color: red;
266  font-style: italic;
267  font-weight: bold;
268}
269.figure {
270  font-weight: bold;
271  text-align: center;
272  font-size: 9pt;
273}
274.filename {
275  color: #333333;
276  font-weight: bold;
277  font-size: 12pt;
278  line-height: 21pt;
279  text-align: center;
280}
281.fn {
282  font-weight: bold;
283}
284.hidden {
285  display: none;
286}
287.left {
288  text-align: left;
289}
290.right {
291  text-align: right;
292}
293.title {
294  color: #990000;
295  font-size: 18pt;
296  line-height: 18pt;
297  font-weight: bold;
298  text-align: center;
299  margin-top: 36pt;
300}
301.vcardline {
302  display: block;
303}
304.warning {
305  font-size: 14pt;
306  background-color: yellow;
307}
308
309
310@media print {
311  .noprint {
312    display: none;
313  }
314 
315  a {
316    color: black;
317    text-decoration: none;
318  }
319
320  table.header {
321    width: 90%;
322  }
323
324  td.header {
325    width: 50%;
326    color: black;
327    background-color: white;
328    vertical-align: top;
329    font-size: 12pt;
330  }
331
332  ul.toc a::after {
333    content: leader('.') target-counter(attr(href), page);
334  }
335 
336  ul.ind li li a {
337    content: target-counter(attr(href), page);
338  }
339 
340  .print2col {
341    column-count: 2;
342    -moz-column-count: 2;
343    column-fill: auto;
344  }
345}
346
347@page {
348  @top-left {
349       content: "Internet-Draft"; 
350  } 
351  @top-right {
352       content: "March 2011"; 
353  } 
354  @top-center {
355       content: "HTTP/1.1, Part 3"; 
356  } 
357  @bottom-left {
358       content: "Fielding, et al."; 
359  } 
360  @bottom-center {
361       content: "Expires September 14, 2011"; 
362  } 
363  @bottom-right {
364       content: "[Page " counter(page) "]"; 
365  } 
366}
367
368@page:first { 
369    @top-left {
370      content: normal;
371    }
372    @top-right {
373      content: normal;
374    }
375    @top-center {
376      content: normal;
377    }
378}
379</style><link rel="Contents" href="#rfc.toc">
380      <link rel="Author" href="#rfc.authors">
381      <link rel="Copyright" href="#rfc.copyrightnotice">
382      <link rel="Index" href="#rfc.index">
383      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
384      <link rel="Chapter" title="2 Protocol Parameters" href="#rfc.section.2">
385      <link rel="Chapter" title="3 Payload" href="#rfc.section.3">
386      <link rel="Chapter" title="4 Representation" href="#rfc.section.4">
387      <link rel="Chapter" title="5 Content Negotiation" href="#rfc.section.5">
388      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
389      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
390      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
391      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
392      <link rel="Chapter" href="#rfc.section.10" title="10 References">
393      <link rel="Appendix" title="A Differences between HTTP and MIME" href="#rfc.section.A">
394      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
395      <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C">
396      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
397      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
398      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.543, 2011-02-18 21:03:40, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
399      <link rel="schema.dct" href="http://purl.org/dc/terms/">
400      <meta name="dct.creator" content="Fielding, R.">
401      <meta name="dct.creator" content="Gettys, J.">
402      <meta name="dct.creator" content="Mogul, J.">
403      <meta name="dct.creator" content="Frystyk, H.">
404      <meta name="dct.creator" content="Masinter, L.">
405      <meta name="dct.creator" content="Leach, P.">
406      <meta name="dct.creator" content="Berners-Lee, T.">
407      <meta name="dct.creator" content="Lafon, Y.">
408      <meta name="dct.creator" content="Reschke, J. F.">
409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
410      <meta name="dct.issued" scheme="ISO8601" content="2011-03-13">
411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
412      <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
413      <meta name="description" 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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
414   </head>
415   <body>
416      <table class="header">
417         <tbody>
418            <tr>
419               <td class="left">HTTPbis Working Group</td>
420               <td class="right">R. Fielding, Editor</td>
421            </tr>
422            <tr>
423               <td class="left">Internet-Draft</td>
424               <td class="right">Adobe</td>
425            </tr>
426            <tr>
427               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
428               </td>
429               <td class="right">J. Gettys</td>
430            </tr>
431            <tr>
432               <td class="left">Intended status: Standards Track</td>
433               <td class="right">Alcatel-Lucent</td>
434            </tr>
435            <tr>
436               <td class="left">Expires: September 14, 2011</td>
437               <td class="right">J. Mogul</td>
438            </tr>
439            <tr>
440               <td class="left"></td>
441               <td class="right">HP</td>
442            </tr>
443            <tr>
444               <td class="left"></td>
445               <td class="right">H. Frystyk</td>
446            </tr>
447            <tr>
448               <td class="left"></td>
449               <td class="right">Microsoft</td>
450            </tr>
451            <tr>
452               <td class="left"></td>
453               <td class="right">L. Masinter</td>
454            </tr>
455            <tr>
456               <td class="left"></td>
457               <td class="right">Adobe</td>
458            </tr>
459            <tr>
460               <td class="left"></td>
461               <td class="right">P. Leach</td>
462            </tr>
463            <tr>
464               <td class="left"></td>
465               <td class="right">Microsoft</td>
466            </tr>
467            <tr>
468               <td class="left"></td>
469               <td class="right">T. Berners-Lee</td>
470            </tr>
471            <tr>
472               <td class="left"></td>
473               <td class="right">W3C/MIT</td>
474            </tr>
475            <tr>
476               <td class="left"></td>
477               <td class="right">Y. Lafon, Editor</td>
478            </tr>
479            <tr>
480               <td class="left"></td>
481               <td class="right">W3C</td>
482            </tr>
483            <tr>
484               <td class="left"></td>
485               <td class="right">J. Reschke, Editor</td>
486            </tr>
487            <tr>
488               <td class="left"></td>
489               <td class="right">greenbytes</td>
490            </tr>
491            <tr>
492               <td class="left"></td>
493               <td class="right">March 13, 2011</td>
494            </tr>
495         </tbody>
496      </table>
497      <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p>
498      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
499      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
500         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the
501         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
502         3 defines HTTP message content, metadata, and content negotiation.
503      </p> 
504      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
505      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
506         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
507      </p> 
508      <p>The changes in this draft are summarized in <a href="#changes.since.12" title="Since draft-ietf-httpbis-p3-payload-12">Appendix&nbsp;E.14</a>.
509      </p> 
510      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
511      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
512      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
513         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
514      </p>
515      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
516         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
517         in progress”.
518      </p>
519      <p>This Internet-Draft will expire on September 14, 2011.</p>
520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
522      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
523         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
524         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
525         BSD License.
526      </p>
527      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
528         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
529         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
530         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
531         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
532         it into languages other than English.
533      </p>
534      <hr class="noprint">
535      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
536      <ul class="toc">
537         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
538               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
539               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
540               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
541                     <li>1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
542                     <li>1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
543                  </ul>
544               </li>
545            </ul>
546         </li>
547         <li>2.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
548               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul>
549                     <li>2.1.1&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
550                  </ul>
551               </li>
552               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
553                     <li>2.2.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
554                  </ul>
555               </li>
556               <li>2.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
557                     <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
558                     <li>2.3.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
559                  </ul>
560               </li>
561               <li>2.4&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
562            </ul>
563         </li>
564         <li>3.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
565               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
566               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
567            </ul>
568         </li>
569         <li>4.&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
570               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
571               <li>4.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
572            </ul>
573         </li>
574         <li>5.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
575               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
576               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
577            </ul>
578         </li>
579         <li>6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
580               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
581               <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
582               <li>6.3&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
583               <li>6.4&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
584               <li>6.5&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
585               <li>6.6&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
586               <li>6.7&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
587               <li>6.8&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
588               <li>6.9&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
589            </ul>
590         </li>
591         <li>7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
592               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
593               <li>7.2&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
594            </ul>
595         </li>
596         <li>8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
597               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
598            </ul>
599         </li>
600         <li>9.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
601         <li>10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
602               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
603               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
604            </ul>
605         </li>
606         <li><a href="#rfc.authors">Authors' Addresses</a></li>
607         <li>A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
608               <li>A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
609               <li>A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
610               <li>A.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
611               <li>A.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
612               <li>A.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
613               <li>A.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
614               <li>A.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
615            </ul>
616         </li>
617         <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
618         <li>C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
619         <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
620         <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
621               <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
622               <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
623               <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
624               <li>E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
625               <li>E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
626               <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
627               <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
628               <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
629               <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
630               <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
631               <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
632               <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
633               <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
634               <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
635            </ul>
636         </li>
637         <li><a href="#rfc.index">Index</a></li>
638      </ul>
639      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
640      <p id="rfc.section.1.p.1">This document defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how the
641         payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and
642         the various selection algorithms that are collectively referred to as HTTP content negotiation.
643      </p>
644      <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
645         errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections on
646         entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
647         associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
648         and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
649      </p>
650      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
651      <p id="rfc.section.1.1.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
652      <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
653      </p>
654      <ul class="empty">
655         <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
656            be negotiated (including error responses).
657         </li>
658      </ul>
659      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
660      <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
661         in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
662      </p>
663      <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
664         protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
665         for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
666         all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
667      </p>
668      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
669      <p id="rfc.section.1.3.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rule expanded.
670      </p>
671      <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
672         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
673         and WSP (whitespace).
674      </p>
675      <h3 id="rfc.section.1.3.1"><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
676      <p id="rfc.section.1.3.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
677      </p>
678      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
679  <a href="#core.rules" class="smpl">word</a>           = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
680  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
681</pre><h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
682      <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
683      <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>   = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
684  <a href="#abnf.dependencies" class="smpl">partial-URI</a>    = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
685  <a href="#abnf.dependencies" class="smpl">qvalue</a>         = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a>&gt;
686</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
687      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
688      <p id="rfc.section.2.1.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
689      <p id="rfc.section.2.1.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence
690         of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
691         not all characters might be available in a given character set and a character set might provide more than one sequence of
692         octets to represent a particular character. This definition is intended to allow various kinds of character encoding, from
693         simple single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques.
694         However, the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information
695         to determine the exact mapping is not permitted.
696      </p>
697      <div class="note" id="rfc.section.2.1.p.3"> 
698         <p> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding". However, since HTTP and MIME
699            share the same registry, it is important that the terminology also be shared.
700         </p> 
701      </div>
702      <div id="rule.charset">
703         <p id="rfc.section.2.1.p.4">  HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
704            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
705         </p>
706      </div>
707      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
708</pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
709         Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
710      </p>
711      <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
712         token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
713         value of the charset parameter can be quoted.
714      </p>
715      <p id="rfc.section.2.1.p.8">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
716      </p>
717      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
718      <p id="rfc.section.2.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header field without charset parameter incorrectly to mean "recipient
719         should guess". Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.
720      </p>
721      <p id="rfc.section.2.1.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially
722         displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>.
723      </p>
724      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
725      <p id="rfc.section.2.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
726         are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
727         of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
728         directly, and only decoded by the recipient.
729      </p>
730      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
731</pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
732         mechanism will be required to remove the encoding.
733      </p>
734      <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span> 
735      </p>
736      <ul class="empty">
737         <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
738         </li>
739      </ul>
740      <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span> 
741      </p>
742      <ul class="empty">
743         <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
744         </li>
745      </ul>
746      <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span> 
747      </p>
748      <ul class="empty">
749         <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
750         </li>
751      </ul>
752      <p id="rfc.section.2.2.p.7">identity<span id="rfc.iref.i.1"></span><span id="rfc.iref.c.6"></span> 
753      </p>
754      <ul class="empty">
755         <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
756            header field, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header field.
757         </li>
758      </ul>
759      <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
760      <p id="rfc.section.2.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
761      <p id="rfc.section.2.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
762      </p>
763      <ul>
764         <li>Name</li>
765         <li>Description</li>
766         <li>Pointer to specification text</li>
767      </ul>
768      <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 6.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
769      </p>
770      <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
771      </p>
772      <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
773      </p>
774      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
775      <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
776      </p>
777      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
778  <a href="#media.types" class="smpl">type</a>       = <a href="#core.rules" class="smpl">token</a>
779  <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
780</pre><div id="rule.parameter">
781         <p id="rfc.section.2.3.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
782         </p>
783      </div>
784      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
785  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
786  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#core.rules" class="smpl">word</a>
787</pre><p id="rfc.section.2.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
788         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
789         of a media-type, depending on its definition within the media type registry.
790      </p>
791      <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
792      </p>
793      <p id="rfc.section.2.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
794         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
795      </p>
796      <p id="rfc.section.2.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
797         outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
798      </p>
799      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
800      <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
801      </p>
802      <p id="rfc.section.2.3.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
803         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
804         entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
805         in a character encoding that does not use octets 13 and 10 for CR and LF respectively, as is the case for some multi-byte
806         character encodings, HTTP allows the use of whatever octet sequences are defined by that character encoding to represent the
807         equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the payload
808         body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
809      </p>
810      <p id="rfc.section.2.3.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
811      </p>
812      <p id="rfc.section.2.3.1.p.4">The "charset" parameter is used with some media types to define the character encoding (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
813         to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character encodings other than "ISO-8859-1"
814         or its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;2.1.1</a> for compatibility problems.
815      </p>
816      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
817      <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message-body.
818         All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts.
819      </p>
820      <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. HTTP does
821         not use the multipart boundary as an indicator of message-body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
822         each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
823      </p>
824      <p id="rfc.section.2.3.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
825      </p>
826      <div class="note" id="rfc.section.2.3.2.p.4"> 
827         <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
828            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
829         </p> 
830      </div>
831      <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
832      <p id="rfc.section.2.4.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
833         other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
834         fields.
835      </p>
836      <p id="rfc.section.2.4.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
837         of subtags:
838      </p>
839      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
840</pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
841         by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
842      </p>
843      <div id="rfc.figure.u.8"></div> 
844      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
845</pre> <p id="rfc.section.2.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
846      </p>
847      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
848      <p id="rfc.section.3.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
849         in the form of header fields, and data, in the form of the sequence of octets in the message-body after any transfer-coding
850         has been decoded.
851      </p>
852      <div id="rfc.iref.p.1"></div>
853      <p id="rfc.section.3.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
854         because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
855         of the representation (e.g., the 206 status code).
856      </p>
857      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
858      <p id="rfc.section.3.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
859         header fields". The following payload header fields are defined by HTTP/1.1:
860      </p>
861      <div id="rfc.table.u.1">
862         <table class="tt full left" cellpadding="3" cellspacing="0">
863            <thead>
864               <tr>
865                  <th>Header Field Name</th>
866                  <th>Defined in...</th>
867               </tr>
868            </thead>
869            <tbody>
870               <tr>
871                  <td class="left">Content-Length</td>
872                  <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.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
873               </tr>
874               <tr>
875                  <td class="left">Content-MD5</td>
876                  <td class="left"><a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section&nbsp;6.8</a></td>
877               </tr>
878               <tr>
879                  <td class="left">Content-Range</td>
880                  <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.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
881               </tr>
882            </tbody>
883         </table>
884      </div>
885      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
886      <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.15"><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
887         safe and proper transfer of the message.
888      </p>
889      <div id="rfc.iref.r.1"></div>
890      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
891      <p id="rfc.section.4.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information
892         that reflects the state of that resource, as observed at some point in the past (e.g., in a response to GET) or to be desired
893         at some point in the future (e.g., in a PUT request).
894      </p>
895      <p id="rfc.section.4.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
896         identified by the effective request URI). The precise semantics of a representation are determined by the type of message
897         (request or response), the request method, the response status code, and the representation metadata. For example, the above
898         semantic is true for the representation in any 200 (OK) response to GET and for the representation in any PUT request. A 200
899         response to PUT, in contrast, contains either a representation that describes the successful action or a representation of
900         the target resource, with the latter indicated by a Content-Location header field with the same value as the effective request
901         URI. Likewise, response messages with an error status code usually contain a representation that describes the error and what
902         next steps are suggested for resolving it.
903      </p>
904      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
905      <p id="rfc.section.4.1.p.1">Representation header fields define metadata about the representation data enclosed in the message-body or, if no message-body
906         is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request with
907         the same effective request URI.
908      </p>
909      <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p>
910      <div id="rfc.table.u.2">
911         <table class="tt full left" cellpadding="3" cellspacing="0">
912            <thead>
913               <tr>
914                  <th>Header Field Name</th>
915                  <th>Defined in...</th>
916               </tr>
917            </thead>
918            <tbody>
919               <tr>
920                  <td class="left">Content-Encoding</td>
921                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a></td>
922               </tr>
923               <tr>
924                  <td class="left">Content-Language</td>
925                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a></td>
926               </tr>
927               <tr>
928                  <td class="left">Content-Location</td>
929                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;6.7</a></td>
930               </tr>
931               <tr>
932                  <td class="left">Content-Type</td>
933                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;6.9</a></td>
934               </tr>
935               <tr>
936                  <td class="left">Expires</td>
937                  <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
938               </tr>
939               <tr>
940                  <td class="left">Last-Modified</td>
941                  <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.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
942               </tr>
943            </tbody>
944         </table>
945      </div>
946      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
947      <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
948         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
949         the representation metadata header fields.
950      </p>
951      <p id="rfc.section.4.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
952         a two-layer, ordered encoding model:
953      </p>
954      <div id="rfc.figure.u.9"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
955</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
956         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
957         to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
958         of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type.
959      </p>
960      <p id="rfc.section.4.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
961         a given representation, with the result that some clients will examine a response body's content and override the specified
962         type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
963         escalation"). Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats
964         match multiple media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling
965         such "content sniffing" when it is used.
966      </p>
967      <p id="rfc.section.4.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
968         that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
969         that defined by the Content-Type.
970      </p>
971      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
972      <p id="rfc.section.5.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
973         processing. Often, the server has different ways of representing the same information; for example, in different formats,
974         languages, or using different character encodings.
975      </p>
976      <p id="rfc.section.5.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
977         which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
978         provides mechanisms for "content negotiation" — a process of allowing selection of a representation of a given resource, when
979         more than one is available.
980      </p>
981      <p id="rfc.section.5.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
982         based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
983         for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
984         "active content" pattern, where the server returns active content which runs on the client and, based on client available
985         parameters, selects additional resources to invoke. "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>) has also been proposed.
986      </p>
987      <p id="rfc.section.5.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
988         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
989         a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
990         to choose from is very large, agent-driven negotiation might not be appropriate.
991      </p>
992      <p id="rfc.section.5.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
993         be considered to be the "same information".
994      </p>
995      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
996      <p id="rfc.section.5.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven
997         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
998         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
999         pertaining to the request (such as the network address of the client).
1000      </p>
1001      <p id="rfc.section.5.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult
1002         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
1003         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
1004         improve the server's guess, the user agent <em class="bcp14">MAY</em> include request header fields (Accept, Accept-Language, Accept-Encoding, etc.) which describe its preferences for such a response.
1005      </p>
1006      <p id="rfc.section.5.1.p.3">Server-driven negotiation has disadvantages: </p>
1007      <ol>
1008         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
1009            complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
1010            to view it on screen or print it on paper?).
1011         </li>
1012         <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
1013            of responses have multiple representations) and a potential violation of the user's privacy.
1014         </li>
1015         <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
1016         <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
1017      </ol>
1018      <p id="rfc.section.5.1.p.4">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
1019         and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 9.9</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including aspects of the connection (e.g., IP address) or information
1020         within extension header fields not defined by this specification.
1021      </p>
1022      <div class="note" id="rfc.section.5.1.p.5"> 
1023         <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
1024         </p> 
1025      </div>
1026      <p id="rfc.section.5.1.p.6">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.
1027      </p>
1028      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
1029      <p id="rfc.section.5.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving
1030         an initial response from the origin server. Selection is based on a list of the available representations of the response
1031         included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
1032         from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the
1033         user selecting from a generated (possibly hypertext) menu.
1034      </p>
1035      <p id="rfc.section.5.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language,
1036         or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
1037         when public caches are used to distribute server load and reduce network usage.
1038      </p>
1039      <p id="rfc.section.5.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation.
1040         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
1041         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
1042         and used within HTTP/1.1.
1043      </p>
1044      <p id="rfc.section.5.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
1045         when the server is unwilling or unable to provide a varying response using server-driven negotiation.
1046      </p>
1047      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
1048      <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to the payload of messages.</p>
1049      <div id="rfc.iref.a.1"></div>
1050      <div id="rfc.iref.h.1"></div>
1051      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.accept" href="#header.accept">Accept</a></h2>
1052      <p id="rfc.section.6.1.p.1">The "Accept" header field can be used by user agents to specify response media types that are acceptable. Accept header fields
1053         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
1054         for an in-line image.
1055      </p>
1056      <div id="rfc.figure.u.10"></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>
1057  <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> ] )
1058 
1059  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
1060                   / ( <a href="#media.types" class="smpl">type</a> "/" "*" )
1061                   / ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> )
1062                   ) *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
1063  <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
1064  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> [ "=" <a href="#core.rules" class="smpl">word</a> ]
1065</pre><p id="rfc.section.6.1.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
1066         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
1067      </p>
1068      <p id="rfc.section.6.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
1069         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
1070         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</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 default value is q=1.
1071      </p>
1072      <div class="note" id="rfc.section.6.1.p.5"> 
1073         <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
1074            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
1075            be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
1076            in Accept. Future media types are discouraged from registering any parameter named "q".
1077         </p> 
1078      </div>
1079      <p id="rfc.section.6.1.p.6">The example</p>
1080      <div id="rfc.figure.u.11"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
1081</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
1082         quality".
1083      </p>
1084      <p id="rfc.section.6.1.p.9">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field
1085         is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then
1086         the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response.
1087      </p>
1088      <p id="rfc.section.6.1.p.10">A more elaborate example is</p>
1089      <div id="rfc.figure.u.12"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
1090          text/x-dvi; q=0.8, text/x-c
1091</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
1092         send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
1093      </p>
1094      <p id="rfc.section.6.1.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
1095         to a given type, the most specific reference has precedence. For example,
1096      </p>
1097      <div id="rfc.figure.u.13"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
1098</pre><p id="rfc.section.6.1.p.15">have the following precedence: </p>
1099      <ol>
1100         <li>text/html;level=1</li>
1101         <li>text/html</li>
1102         <li>text/*</li>
1103         <li>*/*</li>
1104      </ol>
1105      <p id="rfc.section.6.1.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
1106         which matches that type. For example,
1107      </p>
1108      <div id="rfc.figure.u.14"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
1109          text/html;level=2;q=0.4, */*;q=0.5
1110</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
1111      <div id="rfc.table.u.3">
1112         <table class="tt full left" cellpadding="3" cellspacing="0">
1113            <thead>
1114               <tr>
1115                  <th>Media Type</th>
1116                  <th>Quality Value</th>
1117               </tr>
1118            </thead>
1119            <tbody>
1120               <tr>
1121                  <td class="left">text/html;level=1</td>
1122                  <td class="left">1</td>
1123               </tr>
1124               <tr>
1125                  <td class="left">text/html</td>
1126                  <td class="left">0.7</td>
1127               </tr>
1128               <tr>
1129                  <td class="left">text/plain</td>
1130                  <td class="left">0.3</td>
1131               </tr>
1132               <tr>
1133                  <td class="left">image/jpeg</td>
1134                  <td class="left">0.5</td>
1135               </tr>
1136               <tr>
1137                  <td class="left">text/html;level=2</td>
1138                  <td class="left">0.4</td>
1139               </tr>
1140               <tr>
1141                  <td class="left">text/html;level=3</td>
1142                  <td class="left">0.7</td>
1143               </tr>
1144            </tbody>
1145         </table>
1146      </div>
1147      <p id="rfc.section.6.1.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
1148         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
1149      </p>
1150      <div id="rfc.iref.a.2"></div>
1151      <div id="rfc.iref.h.2"></div>
1152      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2>
1153      <p id="rfc.section.6.2.p.1">The "Accept-Charset" header field can be used by user agents to indicate what response character sets are acceptable. This
1154         field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability
1155         to a server which is capable of representing documents in those character sets.
1156      </p>
1157      <div id="rfc.figure.u.15"></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>
1158          <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a>
1159  <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
1160                         [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
1161</pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
1162         example is
1163      </p>
1164      <div id="rfc.figure.u.16"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1165</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
1166         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
1167         not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly
1168         mentioned.
1169      </p>
1170      <p id="rfc.section.6.2.p.6">If no Accept-Charset header field is present, the default is that any character set is acceptable. If an Accept-Charset header
1171         field is present, and if the server cannot send a response which is acceptable according to the Accept-Charset header field,
1172         then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code, though the sending of an unacceptable response is also allowed.
1173      </p>
1174      <div id="rfc.iref.a.3"></div>
1175      <div id="rfc.iref.h.3"></div>
1176      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2>
1177      <p id="rfc.section.6.3.p.1">The "Accept-Encoding" header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) are acceptable in the response.
1178      </p>
1179      <div id="rfc.figure.u.17"></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>
1180                     <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>
1181  <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>  =
1182                     #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
1183  <a href="#header.accept-encoding" class="smpl">codings</a>            = ( <a href="#content.codings" class="smpl">content-coding</a> / "*" )
1184</pre><p id="rfc.section.6.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
1185      </p>
1186      <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
1187      <div id="rfc.figure.u.18"></div><pre class="text">  Accept-Encoding: compress, gzip
1188  Accept-Encoding:
1189  Accept-Encoding: *
1190  Accept-Encoding: compress;q=0.5, gzip;q=1.0
1191  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
1192</pre><p id="rfc.section.6.3.p.6">A server tests whether a content-coding is acceptable, according to an Accept-Encoding field, using these rules: </p>
1193      <ol>
1194         <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it
1195            is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
1196         </li>
1197         <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
1198            field.
1199         </li>
1200         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
1201         <li>The "identity" content-coding is always acceptable, unless specifically refused because the Accept-Encoding field includes
1202            "identity;q=0", or because the field includes "*;q=0" and does not explicitly include the "identity" content-coding. If the
1203            Accept-Encoding field-value is empty, then only the "identity" encoding is acceptable.
1204         </li>
1205      </ol>
1206      <p id="rfc.section.6.3.p.7">If an Accept-Encoding field is present in a request, and if the server cannot send a response which is acceptable according
1207         to the Accept-Encoding header field, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
1208      </p>
1209      <p id="rfc.section.6.3.p.8">If no Accept-Encoding field is present in a request, the server <em class="bcp14">MAY</em> assume that the client will accept any content coding. In this case, if "identity" is one of the available content-codings,
1210         then the server <em class="bcp14">SHOULD</em> use the "identity" content-coding, unless it has additional information that a different content-coding is meaningful to the
1211         client.
1212      </p>
1213      <div class="note" id="rfc.section.6.3.p.9"> 
1214         <p> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings
1215            commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display
1216            messages sent with other content-codings. The server might also make this decision based on information about the particular
1217            user-agent or client.
1218         </p> 
1219      </div>
1220      <div class="note" id="rfc.section.6.3.p.10"> 
1221         <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
1222            not work and are not permitted with x-gzip or x-compress.
1223         </p> 
1224      </div>
1225      <div id="rfc.iref.a.4"></div>
1226      <div id="rfc.iref.h.4"></div>
1227      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2>
1228      <p id="rfc.section.6.4.p.1">The "Accept-Language" header field can be used by user agents to indicate the set of natural languages that are preferred
1229         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
1230      </p>
1231      <div id="rfc.figure.u.19"></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>
1232                    <a href="#header.accept-language" class="smpl">Accept-Language-v</a>
1233  <a href="#header.accept-language" class="smpl">Accept-Language-v</a> =
1234                    1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
1235  <a href="#header.accept-language" class="smpl">language-range</a>    =
1236            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
1237</pre><p id="rfc.section.6.4.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
1238         languages specified by that range. The quality value defaults to "q=1". For example,
1239      </p>
1240      <div id="rfc.figure.u.20"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
1241</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>)
1242      </p>
1243      <p id="rfc.section.6.4.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
1244      </p>
1245      <div class="note" id="rfc.section.6.4.p.7"> 
1246         <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1247         </p> 
1248      </div>
1249      <p id="rfc.section.6.4.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
1250         preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;8.1</a>.
1251      </p>
1252      <p id="rfc.section.6.4.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
1253         of linguistic preference available to the user. If the choice is not made available, then the Accept-Language header field <em class="bcp14">MUST NOT</em> be given in the request.
1254      </p>
1255      <div class="note" id="rfc.section.6.4.p.10"> 
1256         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
1257            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
1258            users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
1259            A user agent might suggest in such a case to add "en" to get the best matching behavior.
1260         </p> 
1261      </div>
1262      <div id="rfc.iref.c.7"></div>
1263      <div id="rfc.iref.h.5"></div>
1264      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2>
1265      <p id="rfc.section.6.5.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation, and thus what
1266         decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding
1267         is primarily used to allow a representation to be compressed without losing the identity of its underlying media type.
1268      </p>
1269      <div id="rfc.figure.u.21"></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>
1270  <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
1271</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>. An example of its use is
1272      </p>
1273      <div id="rfc.figure.u.22"></div><pre class="text">  Content-Encoding: gzip
1274</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
1275         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
1276         directive is present in the message.
1277      </p>
1278      <p id="rfc.section.6.5.p.6">If the content-coding of a representation is not "identity", then the representation metadata <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;6.5</a>) that lists the non-identity content-coding(s) used.
1279      </p>
1280      <p id="rfc.section.6.5.p.7">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
1281      </p>
1282      <p id="rfc.section.6.5.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
1283      </p>
1284      <div id="rfc.iref.c.8"></div>
1285      <div id="rfc.iref.h.6"></div>
1286      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2>
1287      <p id="rfc.section.6.6.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
1288         that this might not be equivalent to all the languages used within the representation.
1289      </p>
1290      <div id="rfc.figure.u.23"></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>
1291  <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
1292</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
1293         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
1294         field is
1295      </p>
1296      <div id="rfc.figure.u.24"></div><pre class="text">  Content-Language: da
1297</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
1298         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
1299         it is intended.
1300      </p>
1301      <p id="rfc.section.6.6.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi", presented
1302         simultaneously in the original Maori and English versions, would call for
1303      </p>
1304      <div id="rfc.figure.u.25"></div><pre class="text">  Content-Language: mi, en
1305</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
1306         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
1307         intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
1308      </p>
1309      <p id="rfc.section.6.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type — it is not limited to textual documents.
1310      </p>
1311      <div id="rfc.iref.c.9"></div>
1312      <div id="rfc.iref.h.7"></div>
1313      <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2>
1314      <p id="rfc.section.6.7.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
1315         message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a 200 response
1316         would contain the same representation that is enclosed as payload in this message.
1317      </p>
1318      <div id="rfc.figure.u.26"></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>
1319                    <a href="#header.content-location" class="smpl">Content-Location-v</a>
1320  <a href="#header.content-location" class="smpl">Content-Location-v</a> =
1321                    <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
1322</pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
1323         body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
1324      </p>
1325      <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
1326         payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
1327         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
1328         response contains the new representation of that resource, thereby distinguishing it from representations that might only
1329         report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
1330         need for a subsequent GET request.
1331      </p>
1332      <p id="rfc.section.6.7.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
1333         server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
1334         request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
1335         and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location
1336         indicates that this representation contains a report on the action's status and the same report is available (for future access
1337         with GET) at the given URI. For example, a purchase transaction made via a POST request might include a receipt document as
1338         the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
1339         in the future.
1340      </p>
1341      <p id="rfc.section.6.7.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
1342         representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
1343         providing the same representation metadata that it received with the original representation. However, such interpretation <em class="bcp14">MUST NOT</em> be used to alter the semantics of the method requested by the client. For example, if a client makes a PUT request on a negotiated
1344         resource and the origin server accepts that PUT (without redirection), then the new set of values for that resource is expected
1345         to be consistent with the one representation supplied in that PUT; the Content-Location cannot be used as a form of reverse
1346         content selection that identifies only one of the negotiated representations to be updated. If the user agent had wanted the
1347         latter semantics, it would have applied the PUT directly to the Content-Location URI.
1348      </p>
1349      <p id="rfc.section.6.7.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
1350         in other contexts, such as within source links or other metadata.
1351      </p>
1352      <p id="rfc.section.6.7.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
1353         to respond to later requests on that Content-Location URI.
1354      </p>
1355      <p id="rfc.section.6.7.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
1356      <div id="rfc.iref.c.10"></div>
1357      <div id="rfc.iref.h.8"></div>
1358      <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a>&nbsp;<a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2>
1359      <p id="rfc.section.6.8.p.1">The "Content-MD5" 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 payload body that provides an end-to-end message integrity check (MIC) of the payload body (the
1360         message-body after any transfer-coding is decoded). Note that a MIC is good for detecting accidental modification of the payload
1361         body in transit, but is not proof against malicious attacks.
1362      </p>
1363      <div id="rfc.figure.u.27"></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>
1364  <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = &lt;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>&gt;
1365</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
1366         agents <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient <em class="bcp14">MAY</em> check that the digest value in this header field matches a corresponding digest calculated on payload body as received.
1367      </p>
1368      <p id="rfc.section.6.8.p.4">The MD5 digest is computed based on the content of the payload body, including any content-coding, but not including any transfer-coding
1369         applied to the message-body because such transfer-codings might be applied or removed anywhere along the request/response
1370         chain. If the message is received with a transfer-coding, that encoding <em class="bcp14">MUST</em> be decoded prior to checking the Content-MD5 value against the received payload.
1371      </p>
1372      <p id="rfc.section.6.8.p.5">HTTP extends RFC 1864 to permit the digest to be computed for MIME composite media-types (e.g., multipart/* and message/rfc822),
1373         but this does not change how the digest is computed as defined in the preceding paragraph.
1374      </p>
1375      <p id="rfc.section.6.8.p.6">There are several consequences of this. The payload for composite types <em class="bcp14">MAY</em> contain many body-parts, each with its own MIME and HTTP header fields (including Content-MD5, Content-Transfer-Encoding,
1376         and Content-Encoding header fields). If a body-part has a Content-Transfer-Encoding or Content-Encoding header field, it is
1377         assumed that the content of the body-part has had the encoding applied, and the body-part is included in the Content-MD5 digest
1378         as is — i.e., after the application. The Transfer-Encoding header field is not allowed within body-parts.
1379      </p>
1380      <p id="rfc.section.6.8.p.7">Conversion of all line breaks to CRLF <em class="bcp14">MUST NOT</em> be done before computing or checking the digest: the line break convention used in the text actually transmitted <em class="bcp14">MUST</em> be left unaltered when computing the digest.
1381      </p>
1382      <div class="note" id="rfc.section.6.8.p.8"> 
1383         <p> <b>Note:</b> While the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several
1384            ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One
1385            is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another
1386            is that HTTP more frequently uses binary content types than MIME, so it is worth noting that, in such cases, the byte order
1387            used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types
1388            with any of several line break conventions and not just the canonical form using CRLF.
1389         </p> 
1390      </div>
1391      <div id="rfc.iref.c.11"></div>
1392      <div id="rfc.iref.h.9"></div>
1393      <h2 id="rfc.section.6.9"><a href="#rfc.section.6.9">6.9</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2>
1394      <p id="rfc.section.6.9.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
1395         the media type is that which would have been sent had the request been a GET.
1396      </p>
1397      <div id="rfc.figure.u.28"></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>
1398  <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a>
1399</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;2.3</a>. An example of the field is
1400      </p>
1401      <div id="rfc.figure.u.29"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
1402</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&nbsp;4.2</a>.
1403      </p>
1404      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
1405      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
1406      <p id="rfc.section.7.1.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
1407      </p>
1408      <div id="rfc.table.1">
1409         <div id="iana.header.registration.table"></div>
1410         <table class="tt full left" cellpadding="3" cellspacing="0">
1411            <thead>
1412               <tr>
1413                  <th>Header Field Name</th>
1414                  <th>Protocol</th>
1415                  <th>Status</th>
1416                  <th>Reference</th>
1417               </tr>
1418            </thead>
1419            <tbody>
1420               <tr>
1421                  <td class="left">Accept</td>
1422                  <td class="left">http</td>
1423                  <td class="left">standard</td>
1424                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.1</a> 
1425                  </td>
1426               </tr>
1427               <tr>
1428                  <td class="left">Accept-Charset</td>
1429                  <td class="left">http</td>
1430                  <td class="left">standard</td>
1431                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.2</a> 
1432                  </td>
1433               </tr>
1434               <tr>
1435                  <td class="left">Accept-Encoding</td>
1436                  <td class="left">http</td>
1437                  <td class="left">standard</td>
1438                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3</a> 
1439                  </td>
1440               </tr>
1441               <tr>
1442                  <td class="left">Accept-Language</td>
1443                  <td class="left">http</td>
1444                  <td class="left">standard</td>
1445                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.4</a> 
1446                  </td>
1447               </tr>
1448               <tr>
1449                  <td class="left">Content-Encoding</td>
1450                  <td class="left">http</td>
1451                  <td class="left">standard</td>
1452                  <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;6.5</a> 
1453                  </td>
1454               </tr>
1455               <tr>
1456                  <td class="left">Content-Language</td>
1457                  <td class="left">http</td>
1458                  <td class="left">standard</td>
1459                  <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;6.6</a> 
1460                  </td>
1461               </tr>
1462               <tr>
1463                  <td class="left">Content-Location</td>
1464                  <td class="left">http</td>
1465                  <td class="left">standard</td>
1466                  <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;6.7</a> 
1467                  </td>
1468               </tr>
1469               <tr>
1470                  <td class="left">Content-MD5</td>
1471                  <td class="left">http</td>
1472                  <td class="left">standard</td>
1473                  <td class="left"> <a href="#header.content-md5" id="rfc.xref.header.content-md5.2" title="Content-MD5">Section&nbsp;6.8</a> 
1474                  </td>
1475               </tr>
1476               <tr>
1477                  <td class="left">Content-Type</td>
1478                  <td class="left">http</td>
1479                  <td class="left">standard</td>
1480                  <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;6.9</a> 
1481                  </td>
1482               </tr>
1483               <tr>
1484                  <td class="left">MIME-Version</td>
1485                  <td class="left">http</td>
1486                  <td class="left">standard</td>
1487                  <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a> 
1488                  </td>
1489               </tr>
1490            </tbody>
1491         </table>
1492      </div>
1493      <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1494      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
1495      <p id="rfc.section.7.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a> of this document.
1496      </p>
1497      <p id="rfc.section.7.2.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
1498      </p>
1499      <div id="rfc.table.2">
1500         <div id="iana.content.coding.registration.table"></div>
1501         <table class="tt full left" cellpadding="3" cellspacing="0">
1502            <thead>
1503               <tr>
1504                  <th>Name</th>
1505                  <th>Description</th>
1506                  <th>Reference</th>
1507               </tr>
1508            </thead>
1509            <tbody>
1510               <tr>
1511                  <td class="left">compress</td>
1512                  <td class="left">UNIX "compress" program method</td>
1513                  <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 
1514                  </td>
1515               </tr>
1516               <tr>
1517                  <td class="left">deflate</td>
1518                  <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
1519                  </td>
1520                  <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 
1521                  </td>
1522               </tr>
1523               <tr>
1524                  <td class="left">gzip</td>
1525                  <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
1526                  <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> 
1527                  </td>
1528               </tr>
1529               <tr>
1530                  <td class="left">identity</td>
1531                  <td class="left">No transformation</td>
1532                  <td class="left"> <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a> 
1533                  </td>
1534               </tr>
1535            </tbody>
1536         </table>
1537      </div>
1538      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1539      <p id="rfc.section.8.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
1540         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
1541         make some suggestions for reducing security risks.
1542      </p>
1543      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
1544      <p id="rfc.section.8.1.p.1">Accept headers fields can reveal information about the user to all servers which are accessed. The Accept-Language header
1545         field in particular can reveal information the user would consider to be of a private nature, because the understanding of
1546         particular languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer
1547         the option to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged
1548         to let the configuration process include a message which makes the user aware of the loss of privacy involved.
1549      </p>
1550      <p id="rfc.section.8.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
1551         by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
1552         looking for any Vary header fields generated by the server, that such sending could improve the quality of service.
1553      </p>
1554      <p id="rfc.section.8.1.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
1555         used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
1556         to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
1557         of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
1558         also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
1559         be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
1560         filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
1561      </p>
1562      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
1563      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
1564      </h1>
1565      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
1566      </h2>
1567      <table>                               
1568         <tr>
1569            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
1570            <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
1571         </tr>
1572         <tr>
1573            <td class="reference"><b id="Part1">[Part1]</b></td>
1574            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), March&nbsp;2011.
1575            </td>
1576         </tr>
1577         <tr>
1578            <td class="reference"><b id="Part2">[Part2]</b></td>
1579            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), March&nbsp;2011.
1580            </td>
1581         </tr>
1582         <tr>
1583            <td class="reference"><b id="Part4">[Part4]</b></td>
1584            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), March&nbsp;2011.
1585            </td>
1586         </tr>
1587         <tr>
1588            <td class="reference"><b id="Part5">[Part5]</b></td>
1589            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), March&nbsp;2011.
1590            </td>
1591         </tr>
1592         <tr>
1593            <td class="reference"><b id="Part6">[Part6]</b></td>
1594            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), March&nbsp;2011.
1595            </td>
1596         </tr>
1597         <tr>
1598            <td class="reference"><b id="RFC1864">[RFC1864]</b></td>
1599            <td class="top"><a href="mailto:jgm+@cmu.edu" title="Carnegie Mellon University">Myers, J.</a> and <a href="mailto:mrose@dbc.mtview.ca.us" title="Dover Beach Consulting, Inc.">M. Rose</a>, “<a href="http://tools.ietf.org/html/rfc1864">The Content-MD5 Header Field</a>”, RFC&nbsp;1864, October&nbsp;1995.
1600            </td>
1601         </tr>
1602         <tr>
1603            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
1604            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
1605               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
1606            </td>
1607         </tr>
1608         <tr>
1609            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
1610            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
1611               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
1612            </td>
1613         </tr>
1614         <tr>
1615            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
1616            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
1617               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
1618            </td>
1619         </tr>
1620         <tr>
1621            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
1622            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
1623            </td>
1624         </tr>
1625         <tr>
1626            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1627            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
1628            </td>
1629         </tr>
1630         <tr>
1631            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1632            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1633            </td>
1634         </tr>
1635         <tr>
1636            <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
1637            <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
1638            </td>
1639         </tr>
1640         <tr>
1641            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1642            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1643            </td>
1644         </tr>
1645         <tr>
1646            <td class="reference"><b id="RFC5646">[RFC5646]</b></td>
1647            <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
1648            </td>
1649         </tr>
1650      </table>
1651      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
1652      </h2>
1653      <table>                             
1654         <tr>
1655            <td class="reference"><b id="BCP97">[BCP97]</b></td>
1656            <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007.
1657            </td>
1658         </tr>
1659         <tr>
1660            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
1661            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
1662            </td>
1663         </tr>
1664         <tr>
1665            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
1666            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
1667            </td>
1668         </tr>
1669         <tr>
1670            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
1671            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
1672            </td>
1673         </tr>
1674         <tr>
1675            <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
1676            <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC&nbsp;2076, February&nbsp;1997.
1677            </td>
1678         </tr>
1679         <tr>
1680            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
1681            <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.
1682            </td>
1683         </tr>
1684         <tr>
1685            <td class="reference"><b id="RFC2295">[RFC2295]</b></td>
1686            <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="http://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
1687            </td>
1688         </tr>
1689         <tr>
1690            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
1691            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
1692            </td>
1693         </tr>
1694         <tr>
1695            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
1696            <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
1697            </td>
1698         </tr>
1699         <tr>
1700            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1701            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1702            </td>
1703         </tr>
1704         <tr>
1705            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
1706            <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD&nbsp;63, RFC&nbsp;3629, November&nbsp;2003.
1707            </td>
1708         </tr>
1709         <tr>
1710            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1711            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1712            </td>
1713         </tr>
1714         <tr>
1715            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1716            <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
1717            </td>
1718         </tr>
1719         <tr>
1720            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1721            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1722            </td>
1723         </tr>
1724         <tr>
1725            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
1726            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
1727            </td>
1728         </tr>
1729      </table>
1730      <div class="avoidbreak">
1731         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1732         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1733               (editor)
1734               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
1735         <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">Alcatel-Lucent Bell Labs</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:jg@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
1736         <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
1737         <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
1738         <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
1739         <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">Email: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
1740         <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
1741         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1742               (editor)
1743               <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
1744         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1745               (editor)
1746               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
1747      </div>
1748      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
1749      <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message-body to be transmitted in an open variety of representations and with extensible mechanisms. However,
1750         RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
1751         carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
1752         to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
1753      </p>
1754      <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments
1755         to HTTP also need to be aware of the differences because some conversions might be required.
1756      </p>
1757      <div id="rfc.iref.m.1"></div>
1758      <div id="rfc.iref.h.10"></div>
1759      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="mime-version" href="#mime-version">MIME-Version</a></h2>
1760      <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message.
1761         Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as defined in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full compliance (where possible) when exporting HTTP messages to strict MIME
1762         environments.
1763      </p>
1764      <div id="rfc.figure.u.30"></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>
1765  <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>
1766</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
1767         document and not the MIME specification.
1768      </p>
1769      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
1770      <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
1771         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
1772         over HTTP.
1773      </p>
1774      <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
1775         a Content-Encoding and by the fact that HTTP allows the use of some character sets which do not use octets 13 and 10 to represent
1776         CR and LF, as is the case for some multi-byte character sets.
1777      </p>
1778      <p id="rfc.section.A.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in
1779         canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP.
1780      </p>
1781      <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
1782      <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
1783      </p>
1784      <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
1785      <p id="rfc.section.A.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on
1786         the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some
1787         experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;"
1788         to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
1789      </p>
1790      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
1791      <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
1792      </p>
1793      <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
1794         format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
1795         being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over
1796         the destination protocol.
1797      </p>
1798      <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
1799      <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
1800      </p>
1801      <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
1802      <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
1803         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
1804         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
1805      </p>
1806      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
1807      <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1
1808         applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
1809         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
1810         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
1811      </p>
1812      <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
1813      </p>
1814      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1815      <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>)
1816      </p>
1817      <p id="rfc.section.C.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
1818         servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
1819         relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
1820      </p>
1821      <p id="rfc.section.C.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
1822      </p>
1823      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1824      <div id="rfc.figure.u.31"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
1825<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v
1826<a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
1827 qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
1828 qvalue ] ] )
1829<a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding:" OWS Accept-Encoding-v
1830<a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] )
1831 ) *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
1832<a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language:" OWS Accept-Language-v
1833<a href="#header.accept-language" class="smpl">Accept-Language-v</a> = *( "," OWS ) language-range [ OWS ";" OWS "q="
1834 qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
1835 ] )
1836<a href="#header.accept" class="smpl">Accept-v</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
1837 OWS media-range [ accept-params ] ] ) ]
1838
1839<a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding:" OWS Content-Encoding-v
1840<a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = *( "," OWS ) content-coding *( OWS "," [ OWS
1841 content-coding ] )
1842<a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language:" OWS Content-Language-v
1843<a href="#header.content-language" class="smpl">Content-Language-v</a> = *( "," OWS ) language-tag *( OWS "," [ OWS
1844 language-tag ] )
1845<a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location:" OWS Content-Location-v
1846<a href="#header.content-location" class="smpl">Content-Location-v</a> = absolute-URI / partial-URI
1847<a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5:" OWS Content-MD5-v
1848<a href="#header.content-md5" class="smpl">Content-MD5-v</a> = &lt;base64 of 128 bit MD5 digest as per [RFC1864]&gt;
1849<a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type:" OWS Content-Type-v
1850<a href="#header.content-type" class="smpl">Content-Type-v</a> = media-type
1851
1852<a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version:" OWS MIME-Version-v
1853<a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*DIGIT "." 1*DIGIT
1854
1855<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1856
1857<a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;
1858<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
1859<a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext
1860<a href="#rule.parameter" class="smpl">attribute</a> = token
1861
1862<a href="#rule.charset" class="smpl">charset</a> = token
1863<a href="#header.accept-encoding" class="smpl">codings</a> = ( content-coding / "*" )
1864<a href="#content.codings" class="smpl">content-coding</a> = token
1865
1866<a href="#header.accept-language" class="smpl">language-range</a> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
1867<a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
1868
1869<a href="#header.accept" class="smpl">media-range</a> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
1870 ";" OWS parameter )
1871<a href="#media.types" class="smpl">media-type</a> = type "/" subtype *( OWS ";" OWS parameter )
1872
1873<a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
1874<a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.6&gt;
1875
1876<a href="#abnf.dependencies" class="smpl">qvalue</a> = &lt;qvalue, defined in [Part1], Section 6.4&gt;
1877
1878<a href="#media.types" class="smpl">subtype</a> = token
1879
1880<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1881<a href="#media.types" class="smpl">type</a> = token
1882
1883<a href="#rule.parameter" class="smpl">value</a> = word
1884
1885<a href="#core.rules" class="smpl">word</a> = &lt;word, defined in [Part1], Section 1.2.2&gt;
1886</pre> <div id="rfc.figure.u.32"></div>
1887      <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
1888; Accept-Charset defined but not used
1889; Accept-Encoding defined but not used
1890; Accept-Language defined but not used
1891; Content-Encoding defined but not used
1892; Content-Language defined but not used
1893; Content-Location defined but not used
1894; Content-MD5 defined but not used
1895; Content-Type defined but not used
1896; MIME-Version defined but not used
1897</pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1898      <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
1899      </h2>
1900      <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1901      </p>
1902      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
1903      </h2>
1904      <p id="rfc.section.E.2.p.1">Closed issues: </p>
1905      <ul>
1906         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
1907         </li>
1908         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/14">http://tools.ietf.org/wg/httpbis/trac/ticket/14</a>&gt;: "Clarification regarding quoting of charset values" (&lt;<a href="http://purl.org/NET/http-errata#charactersets">http://purl.org/NET/http-errata#charactersets</a>&gt;)
1909         </li>
1910         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/16">http://tools.ietf.org/wg/httpbis/trac/ticket/16</a>&gt;: "Remove 'identity' token references" (&lt;<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>&gt;)
1911         </li>
1912         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/25">http://tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
1913         </li>
1914         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
1915         </li>
1916         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/46">http://tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
1917         </li>
1918         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
1919         </li>
1920         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/65">http://tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
1921         </li>
1922         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/66">http://tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
1923         </li>
1924         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative"
1925         </li>
1926         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
1927         </li>
1928      </ul>
1929      <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
1930      </h2>
1931      <p id="rfc.section.E.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1932      </p>
1933      <ul>
1934         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1935      </ul>
1936      <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
1937      <p id="rfc.section.E.4.p.1">Closed issues: </p>
1938      <ul>
1939         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
1940         </li>
1941         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
1942         </li>
1943         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
1944         </li>
1945      </ul>
1946      <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1947      </p>
1948      <ul>
1949         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
1950      </ul>
1951      <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
1952      <p id="rfc.section.E.5.p.1">Closed issues: </p>
1953      <ul>
1954         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
1955         </li>
1956         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/113">http://tools.ietf.org/wg/httpbis/trac/ticket/113</a>&gt;: "language tag matching (Accept-Language) vs RFC4647"
1957         </li>
1958         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
1959         </li>
1960      </ul>
1961      <p id="rfc.section.E.5.p.2">Other changes: </p>
1962      <ul>
1963         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
1964         </li>
1965      </ul>
1966      <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
1967      <p id="rfc.section.E.6.p.1">Closed issues: </p>
1968      <ul>
1969         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
1970         </li>
1971      </ul>
1972      <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1973      </p>
1974      <ul>
1975         <li>Use "/" instead of "|" for alternatives.</li>
1976         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1977         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1978      </ul>
1979      <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
1980      <p id="rfc.section.E.7.p.1">Closed issues: </p>
1981      <ul>
1982         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
1983         </li>
1984      </ul>
1985      <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1986      </p>
1987      <ul>
1988         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1989      </ul>
1990      <p id="rfc.section.E.7.p.3">Other changes: </p>
1991      <ul>
1992         <li>Move definition of quality values into Part 1.</li>
1993      </ul>
1994      <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
1995      <p id="rfc.section.E.8.p.1">Closed issues: </p>
1996      <ul>
1997         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
1998         </li>
1999         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
2000         </li>
2001      </ul>
2002      <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
2003      <p id="rfc.section.E.9.p.1">Closed issues: </p>
2004      <ul>
2005         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
2006         </li>
2007         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>&gt;: "Clarify rules for determining what entities a response carries"
2008         </li>
2009         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/154">http://tools.ietf.org/wg/httpbis/trac/ticket/154</a>&gt;: "Content-Location base-setting problems"
2010         </li>
2011         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
2012         </li>
2013         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
2014         </li>
2015         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>&gt;: "move definitions of gzip/deflate/compress to part 1"
2016         </li>
2017      </ul>
2018      <p id="rfc.section.E.9.p.2">Partly resolved issues: </p>
2019      <ul>
2020         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
2021         </li>
2022         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/149">http://tools.ietf.org/wg/httpbis/trac/ticket/149</a>&gt;: "update IANA requirements wrt Content-Coding values" (add the IANA Considerations subsection)
2023         </li>
2024      </ul>
2025      <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
2026      <p id="rfc.section.E.10.p.1">Closed issues: </p>
2027      <ul>
2028         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
2029         </li>
2030         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/181">http://tools.ietf.org/wg/httpbis/trac/ticket/181</a>&gt;: "Accept-Language: which RFC4647 filtering?"
2031         </li>
2032      </ul>
2033      <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
2034      <p id="rfc.section.E.11.p.1">Closed issues: </p>
2035      <ul>
2036         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
2037         </li>
2038         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/143">http://tools.ietf.org/wg/httpbis/trac/ticket/143</a>&gt;: "IANA registry for content/transfer encodings"
2039         </li>
2040         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
2041         </li>
2042         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
2043         </li>
2044      </ul>
2045      <p id="rfc.section.E.11.p.2">Partly resolved issues: </p>
2046      <ul>
2047         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
2048         </li>
2049      </ul>
2050      <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
2051      <p id="rfc.section.E.12.p.1">Closed issues: </p>
2052      <ul>
2053         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
2054         </li>
2055         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
2056         </li>
2057         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>&gt;: "Delimiting messages with multipart/byteranges"
2058         </li>
2059         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
2060         </li>
2061         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/136">http://tools.ietf.org/wg/httpbis/trac/ticket/136</a>&gt;: "confusing req. language for Content-Location"
2062         </li>
2063         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/167">http://tools.ietf.org/wg/httpbis/trac/ticket/167</a>&gt;: "Content-Location on 304 responses"
2064         </li>
2065         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/183">http://tools.ietf.org/wg/httpbis/trac/ticket/183</a>&gt;: "'requested resource' in content-encoding definition"
2066         </li>
2067         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
2068         </li>
2069      </ul>
2070      <p id="rfc.section.E.12.p.2">Partly resolved issues: </p>
2071      <ul>
2072         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
2073         </li>
2074      </ul>
2075      <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
2076      <p id="rfc.section.E.13.p.1">Closed issues: </p>
2077      <ul>
2078         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
2079         </li>
2080      </ul>
2081      <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h2>
2082      <p id="rfc.section.E.14.p.1">Closed issues: </p>
2083      <ul>
2084         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
2085         </li>
2086         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
2087         </li>
2088         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/277">http://tools.ietf.org/wg/httpbis/trac/ticket/277</a>&gt;: "potentially misleading MAY in media-type def"
2089         </li>
2090      </ul>
2091      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2092      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> 
2093      </p>
2094      <div class="print2col">
2095         <ul class="ind">
2096            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
2097                  <li>Accept header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.a.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
2098                  <li>Accept-Charset header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.a.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">7.1</a></li>
2099                  <li>Accept-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
2100                  <li>Accept-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.a.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li>
2101               </ul>
2102            </li>
2103            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
2104                  <li><em>BCP97</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP97.1">10.1</a>, <a href="#rfc.xref.BCP97.2">10.1</a>, <a href="#rfc.xref.BCP97.3">10.1</a>, <a href="#BCP97"><b>10.2</b></a>, <a href="#rfc.xref.BCP97.4">E.5</a></li>
2105               </ul>
2106            </li>
2107            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
2108                  <li>Coding Format&nbsp;&nbsp;
2109                     <ul>
2110                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.3">2.2</a></li>
2111                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.4">2.2</a></li>
2112                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.5">2.2</a></li>
2113                        <li>identity&nbsp;&nbsp;<a href="#rfc.iref.c.6">2.2</a></li>
2114                     </ul>
2115                  </li>
2116                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.2">2.2</a></li>
2117                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
2118                  <li>Content-Encoding header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.7"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
2119                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.8"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
2120                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.9"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
2121                  <li>Content-MD5 header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.c.10"><b>6.8</b></a>, <a href="#rfc.xref.header.content-md5.2">7.1</a></li>
2122                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.11"><b>6.9</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
2123               </ul>
2124            </li>
2125            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
2126                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">2.2</a></li>
2127               </ul>
2128            </li>
2129            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
2130                  <li><tt>Grammar</tt>&nbsp;&nbsp;
2131                     <ul>
2132                        <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.1</b></a></li>
2133                        <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.2</b></a></li>
2134                        <li><tt>Accept-Charset-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.2</b></a></li>
2135                        <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.3</b></a></li>
2136                        <li><tt>Accept-Encoding-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.3</b></a></li>
2137                        <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.1</b></a></li>
2138                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.4</b></a></li>
2139                        <li><tt>Accept-Language-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.4</b></a></li>
2140                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.1</b></a></li>
2141                        <li><tt>Accept-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.1</b></a></li>
2142                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>2.3</b></a></li>
2143                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2.1</b></a></li>
2144                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.3</b></a></li>
2145                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.2</b></a></li>
2146                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.5</b></a></li>
2147                        <li><tt>Content-Encoding-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>6.5</b></a></li>
2148                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>6.6</b></a></li>
2149                        <li><tt>Content-Language-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>6.6</b></a></li>
2150                        <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>6.7</b></a></li>
2151                        <li><tt>Content-Location-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>6.7</b></a></li>
2152                        <li><tt>Content-MD5</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>6.8</b></a></li>
2153                        <li><tt>Content-MD5-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>6.8</b></a></li>
2154                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>6.9</b></a></li>
2155                        <li><tt>Content-Type-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>6.9</b></a></li>
2156                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.4</b></a></li>
2157                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>2.4</b></a></li>
2158                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
2159                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.3</b></a></li>
2160                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>A.1</b></a></li>
2161                        <li><tt>MIME-Version-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>A.1</b></a></li>
2162                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>2.3</b></a></li>
2163                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.3</b></a></li>
2164                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.3</b></a></li>
2165                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>2.3</b></a></li>
2166                     </ul>
2167                  </li>
2168                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.3">2.2</a></li>
2169               </ul>
2170            </li>
2171            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
2172                  <li>Header Fields&nbsp;&nbsp;
2173                     <ul>
2174                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.h.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
2175                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.h.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">7.1</a></li>
2176                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.h.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
2177                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.h.4"><b>6.4</b></a>, <a href="#rfc.xref.header.accept-language.2">7.1</a></li>
2178                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.h.5"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
2179                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.h.6"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
2180                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.h.7"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
2181                        <li>Content-MD5&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.h.8"><b>6.8</b></a>, <a href="#rfc.xref.header.content-md5.2">7.1</a></li>
2182                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.h.9"><b>6.9</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
2183                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.h.10"><b>A.1</b></a></li>
2184                     </ul>
2185                  </li>
2186               </ul>
2187            </li>
2188            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
2189                  <li>identity (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.i.1">2.2</a></li>
2190                  <li><em>ISO-8859-1</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a href="#ISO-8859-1"><b>10.1</b></a></li>
2191               </ul>
2192            </li>
2193            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
2194                  <li>MIME-Version header field&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.m.1"><b>A.1</b></a></li>
2195               </ul>
2196            </li>
2197            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
2198                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2.1</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">6.1</a>, <a href="#rfc.xref.Part1.17">6.3</a>, <a href="#rfc.xref.Part1.18">6.7</a>, <a href="#rfc.xref.Part1.19">7.2</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.22">A.3</a>, <a href="#rfc.xref.Part1.23">A.6</a><ul>
2199                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a></li>
2200                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a></li>
2201                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a></li>
2202                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">3.2</a></li>
2203                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">6.7</a></li>
2204                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">A.3</a></li>
2205                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2.1</a></li>
2206                        <li><em>Section 6.2.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">2.2</a>, <a href="#rfc.xref.Part1.19">7.2</a></li>
2207                        <li><em>Section 6.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">2.2.1</a></li>
2208                        <li><em>Section 6.2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.20">7.2</a></li>
2209                        <li><em>Section 6.2.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li>
2210                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.16">6.1</a>, <a href="#rfc.xref.Part1.17">6.3</a></li>
2211                        <li><em>Section 9.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">3.1</a></li>
2212                        <li><em>Section 9.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">A.6</a></li>
2213                     </ul>
2214                  </li>
2215                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a>, <a href="#Part2"><b>10.1</b></a><ul>
2216                        <li><em>Section 9.9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a></li>
2217                     </ul>
2218                  </li>
2219                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
2220                        <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a></li>
2221                     </ul>
2222                  </li>
2223                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1</a>, <a href="#Part5"><b>10.1</b></a><ul>
2224                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.1</a></li>
2225                     </ul>
2226                  </li>
2227                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#rfc.xref.Part6.2">5.1</a>, <a href="#Part6"><b>10.1</b></a><ul>
2228                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
2229                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">5.1</a></li>
2230                     </ul>
2231                  </li>
2232                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.1">3</a></li>
2233               </ul>
2234            </li>
2235            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
2236                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">4</a></li>
2237                  <li><em>RFC1864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1864.1">6.8</a>, <a href="#rfc.xref.RFC1864.2">6.8</a>, <a href="#RFC1864"><b>10.1</b></a></li>
2238                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li>
2239                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">7.2</a>, <a href="#RFC1950"><b>10.1</b></a></li>
2240                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">7.2</a>, <a href="#RFC1951"><b>10.1</b></a></li>
2241                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">7.2</a>, <a href="#RFC1952"><b>10.1</b></a></li>
2242                  <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>10.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
2243                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">2.3</a>, <a href="#rfc.xref.RFC2046.2">2.3.2</a>, <a href="#rfc.xref.RFC2046.3">4.2</a>, <a href="#RFC2046"><b>10.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
2244                        <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">4.2</a></li>
2245                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">2.3.2</a></li>
2246                     </ul>
2247                  </li>
2248                  <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>10.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
2249                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
2250                     </ul>
2251                  </li>
2252                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">10.1</a>, <a href="#rfc.xref.RFC2068.2">10.1</a>, <a href="#rfc.xref.RFC2068.3">10.1</a>, <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a></li>
2253                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
2254                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>10.1</b></a></li>
2255                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">2.1</a>, <a href="#RFC2277"><b>10.2</b></a></li>
2256                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">5</a>, <a href="#RFC2295"><b>10.2</b></a></li>
2257                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">2.3.2</a>, <a href="#RFC2388"><b>10.2</b></a></li>
2258                  <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a>, <a href="#RFC2557"><b>10.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul>
2259                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a></li>
2260                     </ul>
2261                  </li>
2262                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">6.4</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.3">E.1</a><ul>
2263                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">6.4</a></li>
2264                     </ul>
2265                  </li>
2266                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">2.1</a>, <a href="#RFC3629"><b>10.2</b></a></li>
2267                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li>
2268                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">2.3</a>, <a href="#RFC4288"><b>10.2</b></a></li>
2269                  <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a>, <a href="#rfc.xref.RFC4647.2">6.4</a>, <a href="#rfc.xref.RFC4647.3">6.4</a>, <a href="#rfc.xref.RFC4647.4">6.4</a>, <a href="#RFC4647"><b>10.1</b></a><ul>
2270                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a></li>
2271                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.2">6.4</a></li>
2272                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.3">6.4</a></li>
2273                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.4">6.4</a></li>
2274                     </ul>
2275                  </li>
2276                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
2277                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a></li>
2278                     </ul>
2279                  </li>
2280                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#RFC5234"><b>10.1</b></a><ul>
2281                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
2282                     </ul>
2283                  </li>
2284                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#RFC5322"><b>10.2</b></a>, <a href="#rfc.xref.RFC5322.1">A</a></li>
2285                  <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">2.4</a>, <a href="#rfc.xref.RFC5646.2">2.4</a>, <a href="#rfc.xref.RFC5646.3">2.4</a>, <a href="#RFC5646"><b>10.1</b></a><ul>
2286                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">2.4</a></li>
2287                     </ul>
2288                  </li>
2289               </ul>
2290            </li>
2291         </ul>
2292      </div>
2293   </body>
2294</html>
Note: See TracBrowser for help on using the repository browser.