source: draft-ietf-httpbis/03/p3-payload.html @ 1099

Last change on this file since 1099 was 1099, checked in by julian.reschke@…, 9 years ago

bump up document dates, update to latest version of rfc2629.xslt

File size: 170.4 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}
32dd {
33  margin-right: 2em;
34}
35dl {
36  margin-left: 2em;
37}
38
39ul.empty {
40  list-style-type: none;
41}
42ul.empty li {
43  margin-top: .5em;
44}
45dl p {
46  margin-left: 0em;
47}
48dt {
49  margin-top: .5em;
50}
51h1 {
52  font-size: 14pt;
53  line-height: 21pt;
54  page-break-after: avoid;
55}
56h1.np {
57  page-break-before: always;
58}
59h1 a {
60  color: #333333;
61}
62h2 {
63  font-size: 12pt;
64  line-height: 15pt;
65  page-break-after: avoid;
66}
67h3, h4, h5, h6 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
73}
74img {
75  margin-left: 3em;
76}
77li {
78  margin-left: 2em;
79  margin-right: 2em;
80}
81ol {
82  margin-left: 2em;
83  margin-right: 2em;
84}
85ol p {
86  margin-left: 0em;
87}
88p {
89  margin-left: 2em;
90  margin-right: 2em;
91}
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
96}
97pre.text2 {
98  border-style: dotted;
99  border-width: 1px;
100  background-color: #f0f0f0;
101  width: 69em;
102}
103pre.inline {
104  background-color: white;
105  padding: 0em;
106}
107pre.text {
108  border-style: dotted;
109  border-width: 1px;
110  background-color: #f8f8f8;
111  width: 69em;
112}
113pre.drawing {
114  border-style: solid;
115  border-width: 1px;
116  background-color: #f8f8f8;
117  padding: 2em;
118}
119table {
120  margin-left: 2em;
121}
122table.tt {
123  vertical-align: top;
124}
125table.full {
126  border-style: outset;
127  border-width: 1px;
128}
129table.headers {
130  border-style: outset;
131  border-width: 1px;
132}
133table.tt td {
134  vertical-align: top;
135}
136table.full td {
137  border-style: inset;
138  border-width: 1px;
139}
140table.tt th {
141  vertical-align: top;
142}
143table.full th {
144  border-style: inset;
145  border-width: 1px;
146}
147table.headers th {
148  border-style: none none inset none;
149  border-width: 1px;
150}
151table.left {
152  margin-right: auto;
153}
154table.right {
155  margin-left: auto;
156}
157table.center {
158  margin-left: auto;
159  margin-right: auto;
160}
161caption {
162  caption-side: bottom;
163  font-weight: bold;
164  font-size: 9pt;
165  margin-top: .5em;
166}
167
168table.header {
169  border-spacing: 1px;
170  width: 95%;
171  font-size: 10pt;
172  color: white;
173}
174td.top {
175  vertical-align: top;
176}
177td.topnowrap {
178  vertical-align: top;
179  white-space: nowrap; 
180}
181table.header td {
182  background-color: gray;
183  width: 50%;
184}
185table.header a {
186  color: white;
187}
188td.reference {
189  vertical-align: top;
190  white-space: nowrap;
191  padding-right: 1em;
192}
193thead {
194  display:table-header-group;
195}
196ul.toc, ul.toc ul {
197  list-style: none;
198  margin-left: 1.5em;
199  margin-right: 0em;
200  padding-left: 0em;
201}
202ul.toc li {
203  line-height: 150%;
204  font-weight: bold;
205  font-size: 10pt;
206  margin-left: 0em;
207  margin-right: 0em;
208}
209ul.toc li li {
210  line-height: normal;
211  font-weight: normal;
212  font-size: 9pt;
213  margin-left: 0em;
214  margin-right: 0em;
215}
216li.excluded {
217  font-size: 0pt;
218}
219ul p {
220  margin-left: 0em;
221}
222ul.ind, ul.ind ul {
223  list-style: none;
224  margin-left: 1.5em;
225  margin-right: 0em;
226  padding-left: 0em;
227  page-break-before: avoid;
228}
229ul.ind li {
230  font-weight: bold;
231  line-height: 200%;
232  margin-left: 0em;
233  margin-right: 0em;
234}
235ul.ind li li {
236  font-weight: normal;
237  line-height: 150%;
238  margin-left: 0em;
239  margin-right: 0em;
240}
241.avoidbreak {
242  page-break-inside: avoid;
243}
244.bcp14 {
245  font-style: normal;
246  text-transform: lowercase;
247  font-variant: small-caps;
248}
249.comment {
250  background-color: yellow;
251}
252.center {
253  text-align: center;
254}
255.error {
256  color: red;
257  font-style: italic;
258  font-weight: bold;
259}
260.figure {
261  font-weight: bold;
262  text-align: center;
263  font-size: 9pt;
264}
265.filename {
266  color: #333333;
267  font-weight: bold;
268  font-size: 12pt;
269  line-height: 21pt;
270  text-align: center;
271}
272.fn {
273  font-weight: bold;
274}
275.hidden {
276  display: none;
277}
278.left {
279  text-align: left;
280}
281.right {
282  text-align: right;
283}
284.title {
285  color: #990000;
286  font-size: 18pt;
287  line-height: 18pt;
288  font-weight: bold;
289  text-align: center;
290  margin-top: 36pt;
291}
292.vcardline {
293  display: block;
294}
295.warning {
296  font-size: 14pt;
297  background-color: yellow;
298}
299
300
301@media print {
302  .noprint {
303    display: none;
304  }
305 
306  a {
307    color: black;
308    text-decoration: none;
309  }
310
311  table.header {
312    width: 90%;
313  }
314
315  td.header {
316    width: 50%;
317    color: black;
318    background-color: white;
319    vertical-align: top;
320    font-size: 12pt;
321  }
322
323  ul.toc a::after {
324    content: leader('.') target-counter(attr(href), page);
325  }
326 
327  ul.ind li li a {
328    content: target-counter(attr(href), page);
329  }
330 
331  .print2col {
332    column-count: 2;
333    -moz-column-count: 2;
334    column-fill: auto;
335  }
336}
337
338@page {
339  @top-left {
340       content: "Internet-Draft"; 
341  } 
342  @top-right {
343       content: "June 2008"; 
344  } 
345  @top-center {
346       content: "HTTP/1.1, Part 3"; 
347  } 
348  @bottom-left {
349       content: "Fielding, et al."; 
350  } 
351  @bottom-center {
352       content: "Standards Track"; 
353  } 
354  @bottom-right {
355       content: "[Page " counter(page) "]"; 
356  } 
357}
358
359@page:first { 
360    @top-left {
361      content: normal;
362    }
363    @top-right {
364      content: normal;
365    }
366    @top-center {
367      content: normal;
368    }
369}
370</style><link rel="Contents" href="#rfc.toc">
371      <link rel="Author" href="#rfc.authors">
372      <link rel="Copyright" href="#rfc.copyright">
373      <link rel="Index" href="#rfc.index">
374      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
375      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
376      <link rel="Chapter" title="3 Protocol Parameters" href="#rfc.section.3">
377      <link rel="Chapter" title="4 Entity" href="#rfc.section.4">
378      <link rel="Chapter" title="5 Content Negotiation" href="#rfc.section.5">
379      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
380      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
381      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
382      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
383      <link rel="Chapter" href="#rfc.section.10" title="10 References">
384      <link rel="Appendix" title="A Differences Between HTTP Entities and RFC 2045 Entities" href="#rfc.section.A">
385      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
386      <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C">
387      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
388      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
389      <link rel="schema.dct" href="http://purl.org/dc/terms/">
390      <meta name="dct.creator" content="Fielding, R.">
391      <meta name="dct.creator" content="Gettys, J.">
392      <meta name="dct.creator" content="Mogul, J.">
393      <meta name="dct.creator" content="Frystyk, H.">
394      <meta name="dct.creator" content="Masinter, L.">
395      <meta name="dct.creator" content="Leach, P.">
396      <meta name="dct.creator" content="Berners-Lee, T.">
397      <meta name="dct.creator" content="Lafon, Y.">
398      <meta name="dct.creator" content="Reschke, J. F.">
399      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-03">
400      <meta name="dct.issued" scheme="ISO8601" content="2008-06-17">
401      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
402      <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.">
403      <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.">
404   </head>
405   <body>
406      <table class="header">
407         <tbody>
408            <tr>
409               <td class="left">Network Working Group</td>
410               <td class="right">R. Fielding, Editor</td>
411            </tr>
412            <tr>
413               <td class="left">Internet-Draft</td>
414               <td class="right">Day Software</td>
415            </tr>
416            <tr>
417               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
418               </td>
419               <td class="right">J. Gettys</td>
420            </tr>
421            <tr>
422               <td class="left">Intended status: Standards Track</td>
423               <td class="right">One Laptop per Child</td>
424            </tr>
425            <tr>
426               <td class="left">Expires: December 19, 2008</td>
427               <td class="right">J. Mogul</td>
428            </tr>
429            <tr>
430               <td class="left"></td>
431               <td class="right">HP</td>
432            </tr>
433            <tr>
434               <td class="left"></td>
435               <td class="right">H. Frystyk</td>
436            </tr>
437            <tr>
438               <td class="left"></td>
439               <td class="right">Microsoft</td>
440            </tr>
441            <tr>
442               <td class="left"></td>
443               <td class="right">L. Masinter</td>
444            </tr>
445            <tr>
446               <td class="left"></td>
447               <td class="right">Adobe Systems</td>
448            </tr>
449            <tr>
450               <td class="left"></td>
451               <td class="right">P. Leach</td>
452            </tr>
453            <tr>
454               <td class="left"></td>
455               <td class="right">Microsoft</td>
456            </tr>
457            <tr>
458               <td class="left"></td>
459               <td class="right">T. Berners-Lee</td>
460            </tr>
461            <tr>
462               <td class="left"></td>
463               <td class="right">W3C/MIT</td>
464            </tr>
465            <tr>
466               <td class="left"></td>
467               <td class="right">Y. Lafon, Editor</td>
468            </tr>
469            <tr>
470               <td class="left"></td>
471               <td class="right">W3C</td>
472            </tr>
473            <tr>
474               <td class="left"></td>
475               <td class="right">J. Reschke, Editor</td>
476            </tr>
477            <tr>
478               <td class="left"></td>
479               <td class="right">greenbytes</td>
480            </tr>
481            <tr>
482               <td class="left"></td>
483               <td class="right">June 17, 2008</td>
484            </tr>
485         </tbody>
486      </table>
487      <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-03</span></p>
488      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
489      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
490         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
491         6 of BCP 79.
492      </p>
493      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
494         that other groups may also distribute working documents as Internet-Drafts.
495      </p>
496      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
497         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
498         in progress”.
499      </p>
500      <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
501      </p>
502      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
503      </p>
504      <p>This Internet-Draft will expire on December 19, 2008.</p>
505      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
506      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
507         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the
508         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
509         3 defines HTTP message content, metadata, and content negotiation.
510      </p> 
511      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
512      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
513         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
514      </p> 
515      <p>The changes in this draft are summarized in <a href="#changes.since.02" title="Since draft-ietf-httpbis-p3-payload-02">Appendix&nbsp;D.4</a>.
516      </p> 
517      <hr class="noprint">
518      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
519      <ul class="toc">
520         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
521               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
522            </ul>
523         </li>
524         <li>2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
525         <li>3.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
526               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul>
527                     <li>3.1.1&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
528                  </ul>
529               </li>
530               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
531               <li>3.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
532                     <li>3.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
533                     <li>3.3.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
534                  </ul>
535               </li>
536               <li>3.4&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
537               <li>3.5&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
538            </ul>
539         </li>
540         <li>4.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a><ul>
541               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#entity.header.fields">Entity Header Fields</a></li>
542               <li>4.2&nbsp;&nbsp;&nbsp;<a href="#entity.body">Entity Body</a><ul>
543                     <li>4.2.1&nbsp;&nbsp;&nbsp;<a href="#type">Type</a></li>
544                     <li>4.2.2&nbsp;&nbsp;&nbsp;<a href="#entity.length">Entity Length</a></li>
545                  </ul>
546               </li>
547            </ul>
548         </li>
549         <li>5.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
550               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
551               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
552               <li>5.3&nbsp;&nbsp;&nbsp;<a href="#transparent.negotiation">Transparent Negotiation</a></li>
553            </ul>
554         </li>
555         <li>6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
556               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
557               <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
558               <li>6.3&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
559               <li>6.4&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
560               <li>6.5&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
561               <li>6.6&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
562               <li>6.7&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
563               <li>6.8&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
564               <li>6.9&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
565            </ul>
566         </li>
567         <li>7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
568               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
569            </ul>
570         </li>
571         <li>8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
572               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>
573               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#content-disposition.issues">Content-Disposition Issues</a></li>
574            </ul>
575         </li>
576         <li>9.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
577         <li>10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
578               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
579               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
580            </ul>
581         </li>
582         <li><a href="#rfc.authors">Authors' Addresses</a></li>
583         <li>A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul>
584               <li>A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
585               <li>A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
586               <li>A.3&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
587               <li>A.4&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
588               <li>A.5&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
589               <li>A.6&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
590            </ul>
591         </li>
592         <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a><ul>
593               <li>B.1&nbsp;&nbsp;&nbsp;<a href="#content-disposition">Content-Disposition</a></li>
594            </ul>
595         </li>
596         <li>C.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
597               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
598               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
599            </ul>
600         </li>
601         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
602               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
603               <li>D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
604               <li>D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
605               <li>D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
606            </ul>
607         </li>
608         <li><a href="#rfc.index">Index</a></li>
609         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
610      </ul>
611      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
612      <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
613         payload is intended to be interpreted by a recipient, the request header fields that may influence content selection, and
614         the various selection algorithms that are collectively referred to as HTTP content negotiation.
615      </p>
616      <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
617         errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections on
618         entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
619         associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
620         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>.
621      </p>
622      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
623      <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
624         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>.
625      </p>
626      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
627      </p>
628      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
629      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</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> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 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>: <span class="comment" id="abnf.dep">[<a href="#abnf.dep" class="smpl">abnf.dep</a>: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span> 
630      </p>
631      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">ALPHA</a>          = &lt;ALPHA, 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 2.2</a>&gt;
632  <a href="#notation" class="smpl">DIGIT</a>          = &lt;DIGIT, 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 2.2</a>&gt;
633  <a href="#notation" class="smpl">OCTET</a>          = &lt;OCTET, 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 2.2</a>&gt;
634</pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">quoted-string</a>  = &lt;quoted-string, 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#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
635  <a href="#notation" class="smpl">token</a>          = &lt;token, 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#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
636</pre><div id="abnf.dependencies">
637         <p id="rfc.section.2.p.4">                The ABNF rules below are defined in other parts:</p>
638      </div>
639      <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absoluteURI</a>    = &lt;absoluteURI, 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#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
640  <a href="#abnf.dependencies" class="smpl">Content-Length</a> = &lt;Content-Length, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>&gt;
641  <a href="#abnf.dependencies" class="smpl">relativeURI</a>    = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
642  <a href="#abnf.dependencies" class="smpl">message-header</a> = &lt;message-header, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>&gt;
643</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Last-Modified</a>  = &lt;Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 7.6</a>&gt;
644</pre><div id="rfc.figure.u.5"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Content-Range</a>  = &lt;Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 6.2</a>&gt;
645</pre><div id="rfc.figure.u.6"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Expires</a>        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt;
646</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
647      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
648      <p id="rfc.section.3.1.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
649      <p id="rfc.section.3.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
650         of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
651         not all characters may be available in a given character set and a character set may provide more than one sequence of octets
652         to represent a particular character. This definition is intended to allow various kinds of character encoding, from simple
653         single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. However,
654         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
655         to determine the exact mapping is not permitted.
656      </p>
657      <ul class="empty">
658         <li> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME
659            share the same registry, it is important that the terminology also be shared.
660         </li>
661      </ul>
662      <div id="rule.charset">
663         <p id="rfc.section.3.1.p.4">  HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
664            Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
665         </p>
666      </div>
667      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#notation" class="smpl">token</a>
668</pre><p id="rfc.section.3.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
669         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.
670      </p>
671      <p id="rfc.section.3.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header (in which the charset value is an unquoted token)
672         and as the value of a parameter in a Content-Type header (within a request or response), in which case the parameter value
673         of the charset parameter may be quoted.
674      </p>
675      <p id="rfc.section.3.1.p.8">Implementors should 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>.
676      </p>
677      <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
678      <p id="rfc.section.3.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should
679         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.
680      </p>
681      <p id="rfc.section.3.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
682         displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;3.3.1</a>.
683      </p>
684      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
685      <p id="rfc.section.3.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to an entity. Content codings are
686         primarily used to allow a document to be compressed or otherwise usefully transformed without losing the identity of its underlying
687         media type and without loss of information. Frequently, the entity is stored in coded form, transmitted directly, and only
688         decoded by the recipient.
689      </p>
690      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#notation" class="smpl">token</a>
691</pre><p id="rfc.section.3.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
692         mechanism will be required to remove the encoding.
693      </p>
694      <p id="rfc.section.3.2.p.4">The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry
695         contains the following tokens:
696      </p>
697      <p id="rfc.section.3.2.p.5">gzip<span id="rfc.iref.g.3"></span> 
698      </p>
699      <ul class="empty">
700         <li>An encoding format produced by the file compression program "gzip" (GNU zip) as described in <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC.
701         </li>
702      </ul>
703      <p id="rfc.section.3.2.p.6">compress<span id="rfc.iref.c.1"></span> 
704      </p>
705      <ul class="empty">
706         <li>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch
707            coding (LZW).
708         </li>
709         <li>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.
710            Their use here is representative of historical practice, not good design. For compatibility with previous implementations
711            of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.
712         </li>
713      </ul>
714      <p id="rfc.section.3.2.p.7">deflate<span id="rfc.iref.d.1"></span> 
715      </p>
716      <ul class="empty">
717         <li>The "zlib" format defined in <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>.
718         </li>
719      </ul>
720      <p id="rfc.section.3.2.p.8">identity<span id="rfc.iref.i.1"></span> 
721      </p>
722      <ul class="empty">
723         <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
724            header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header.
725         </li>
726      </ul>
727      <p id="rfc.section.3.2.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed
728         to implement a new value <em class="bcp14">SHOULD</em> be publicly available and adequate for independent implementation, and conform to the purpose of content coding defined in
729         this section.
730      </p>
731      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
732      <p id="rfc.section.3.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.
733      </p>
734      <div id="rfc.figure.u.9"></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="#rule.parameter" class="smpl">parameter</a> )
735  <a href="#media.types" class="smpl">type</a>           = <a href="#notation" class="smpl">token</a>
736  <a href="#media.types" class="smpl">subtype</a>        = <a href="#notation" class="smpl">token</a>
737</pre><div id="rule.parameter">
738         <p id="rfc.section.3.3.p.3">      Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs.
739         </p>
740      </div>
741      <div id="rfc.figure.u.10"></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>
742  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#notation" class="smpl">token</a>
743  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#notation" class="smpl">token</a> | <a href="#notation" class="smpl">quoted-string</a>
744</pre><p id="rfc.section.3.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
745         depending on the semantics of the parameter name. Linear white space (LWS) <em class="bcp14">MUST NOT</em> be used between the type and subtype, nor between an attribute and its value. The presence or absence of a parameter might
746         be significant to the processing of a media-type, depending on its definition within the media type registry.
747      </p>
748      <p id="rfc.section.3.3.p.6">All parameters defined as a token are also allowed to occur as quoted-string; both notations are equivalent.</p>
749      <p id="rfc.section.3.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
750         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
751      </p>
752      <p id="rfc.section.3.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
753         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.
754      </p>
755      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
756      <p id="rfc.section.3.3.1.p.1">Internet media types are registered with a canonical form. An entity-body transferred via HTTP messages <em class="bcp14">MUST</em> be represented in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next
757         paragraph.
758      </p>
759      <p id="rfc.section.3.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
760         allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
761         entire entity-body. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP. In addition, if
762         the text is represented in a character set that does not use octets 13 and 10 for CR and LF respectively, as is the case for
763         some multi-byte character sets, HTTP allows the use of whatever octet sequences are defined by that character set to represent
764         the equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the entity-body;
765         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).
766      </p>
767      <p id="rfc.section.3.3.1.p.3">If an entity-body is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
768      </p>
769      <p id="rfc.section.3.3.1.p.4">The "charset" parameter is used with some media types to define the character set (<a href="#character.sets" title="Character Sets">Section&nbsp;3.1</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
770         to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or
771         its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;3.1.1</a> for compatibility problems.
772      </p>
773      <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
774      <p id="rfc.section.3.3.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more entities within a single message-body. All
775         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. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve
776         the self-delimiting nature of a multipart message-body, wherein the "end" of the message-body is indicated by the ending multipart
777         boundary.
778      </p>
779      <p id="rfc.section.3.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception
780         is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response.  In all other cases, 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
781         each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
782      </p>
783      <p id="rfc.section.3.3.2.p.3">In general, 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. If an application receives
784         an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
785      </p>
786      <ul class="empty">
787         <li> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
788            method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
789         </li>
790      </ul>
791      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h2>
792      <p id="rfc.section.3.4.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;5</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
793         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
794         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
795      </p>
796      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#notation" class="smpl">DIGIT</a> ] )
797                 | ( "1" [ "." 0*3("0") ] )
798</pre><p id="rfc.section.3.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p>
799      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
800      <p id="rfc.section.3.5.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information
801         to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and
802         Content-Language fields.
803      </p>
804      <p id="rfc.section.3.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
805      </p>
806      <div id="rfc.figure.u.12"></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>  <a href="#language.tags" class="smpl">language-tag</a>  = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> )
807  <a href="#language.tags" class="smpl">primary-tag</a>   = 1*8<a href="#notation" class="smpl">ALPHA</a>
808  <a href="#language.tags" class="smpl">subtag</a>        = 1*8<a href="#notation" class="smpl">ALPHA</a>
809</pre><p id="rfc.section.3.5.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered
810         by the IANA. Example tags include:
811      </p>
812      <div id="rfc.figure.u.13"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
813</pre><p id="rfc.section.3.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
814         code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
815         in future.)
816      </p>
817      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
818      <p id="rfc.section.4.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
819         fields and an entity-body, although some responses will only include the entity-headers.
820      </p>
821      <p id="rfc.section.4.p.2">In this section, both sender and recipient refer to either the client or the server, depending on who sends and who receives
822         the entity.
823      </p>
824      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="entity.header.fields" href="#entity.header.fields">Entity Header Fields</a></h2>
825      <p id="rfc.section.4.1.p.1">Entity-header fields define metainformation about the entity-body or, if no body is present, about the resource identified
826         by the request.
827      </p>
828      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#entity.header.fields" class="smpl">entity-header</a>  = <a href="#header.content-encoding" class="smpl">Content-Encoding</a>         ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a>
829                 | <a href="#header.content-language" class="smpl">Content-Language</a>         ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a>
830                 | <a href="#abnf.dependencies" class="smpl">Content-Length</a>           ; <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>
831                 | <a href="#header.content-location" class="smpl">Content-Location</a>         ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;6.7</a>
832                 | <a href="#header.content-md5" class="smpl">Content-MD5</a>              ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section&nbsp;6.8</a>
833                 | <a href="#abnf.dependencies" class="smpl">Content-Range</a>            ; <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 6.2</a>
834                 | <a href="#header.content-type" class="smpl">Content-Type</a>             ; <a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;6.9</a>
835                 | <a href="#abnf.dependencies" class="smpl">Expires</a>                  ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>
836                 | <a href="#abnf.dependencies" class="smpl">Last-Modified</a>            ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 7.6</a>
837                 | <a href="#entity.header.fields" class="smpl">extension-header</a>
838 
839  <a href="#entity.header.fields" class="smpl">extension-header</a> = <a href="#abnf.dependencies" class="smpl">message-header</a>
840</pre><p id="rfc.section.4.1.p.3">The extension-header mechanism allows additional entity-header fields to be defined without changing the protocol, but these
841         fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by the recipient and <em class="bcp14">MUST</em> be forwarded by transparent proxies.
842      </p>
843      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="entity.body" href="#entity.body">Entity Body</a></h2>
844      <p id="rfc.section.4.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p>
845      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  <a href="#entity.body" class="smpl">entity-body</a>    = *<a href="#notation" class="smpl">OCTET</a>
846</pre><p id="rfc.section.4.2.p.3">An entity-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 4.3</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>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
847         safe and proper transfer of the message.
848      </p>
849      <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a id="type" href="#type">Type</a></h3>
850      <p id="rfc.section.4.2.1.p.1">When an entity-body is included with a message, the data type of that body is determined via the header fields Content-Type
851         and Content-Encoding. These define a two-layer, ordered encoding model:
852      </p>
853      <div id="rfc.figure.u.16"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
854</pre><p id="rfc.section.4.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
855         codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
856         is no default encoding.
857      </p>
858      <p id="rfc.section.4.2.1.p.4">Any HTTP/1.1 message containing an entity-body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a
859         Content-Type field, the recipient <em class="bcp14">MAY</em> attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the
860         resource. If the media type remains unknown, the recipient <em class="bcp14">SHOULD</em> treat it as type "application/octet-stream".
861      </p>
862      <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a id="entity.length" href="#entity.length">Entity Length</a></h3>
863      <p id="rfc.section.4.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</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> defines how the transfer-length of a message-body is determined.
864      </p>
865      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
866      <p id="rfc.section.5.p.1">Most HTTP responses include an entity which contains information for interpretation by a human user. Naturally, it is desirable
867         to supply the user with the "best available" entity corresponding to the request. Unfortunately for servers and caches, not
868         all users have the same preferences for what is "best," and not all user agents are equally capable of rendering all entity
869         types. For that reason, HTTP has provisions for several mechanisms for "content negotiation" -- the process of selecting the
870         best representation for a given response when there are multiple representations available.
871      </p>
872      <ul class="empty">
873         <li> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different
874            capabilities of that type, be in different languages, etc.
875         </li>
876      </ul>
877      <p id="rfc.section.5.p.2">Any response containing an entity-body <em class="bcp14">MAY</em> be subject to negotiation, including error responses.
878      </p>
879      <p id="rfc.section.5.p.3">There are two kinds of content negotiation which are possible in HTTP: server-driven and agent-driven negotiation. These two
880         kinds of negotiation are orthogonal and thus may be used separately or in combination. One method of combination, referred
881         to as transparent negotiation, occurs when a cache uses the agent-driven negotiation information provided by the origin server
882         in order to provide server-driven negotiation for subsequent requests.
883      </p>
884      <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>
885      <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
886         negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.
887         language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
888         pertaining to the request (such as the network address of the client).
889      </p>
890      <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
891         to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
892         (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
893         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.
894      </p>
895      <p id="rfc.section.5.1.p.3">Server-driven negotiation has disadvantages: </p>
896      <ol>
897         <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
898            complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
899            to view it on screen or print it on paper?).
900         </li>
901         <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
902            of responses have multiple representations) and a potential violation of the user's privacy.
903         </li>
904         <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
905         <li>It may limit a public cache's ability to use the same response for multiple user's requests.</li>
906      </ol>
907      <p id="rfc.section.5.1.p.4">HTTP/1.1 includes the following request-header fields for enabling server-driven negotiation through description of user agent
908         capabilities 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 10.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 information outside the request-header fields or within extension
909         header fields not defined by this specification.
910      </p>
911      <p id="rfc.section.5.1.p.5">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><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.
912      </p>
913      <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>
914      <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
915         an initial response from the origin server. Selection is based on a list of the available representations of the response
916         included within the header fields or entity-body of the initial response, with each representation identified by its own URI.
917         Selection from among the representations may be performed automatically (if the user agent is capable of doing so) or manually
918         by the user selecting from a generated (possibly hypertext) menu.
919      </p>
920      <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,
921         or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
922         when public caches are used to distribute server load and reduce network usage.
923      </p>
924      <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.
925         This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
926         for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
927         and used within HTTP/1.1.
928      </p>
929      <p id="rfc.section.5.2.p.4">HTTP/1.1 defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation when
930         the server is unwilling or unable to provide a varying response using server-driven negotiation.
931      </p>
932      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="transparent.negotiation" href="#transparent.negotiation">Transparent Negotiation</a></h2>
933      <p id="rfc.section.5.3.p.1">Transparent negotiation is a combination of both server-driven and agent-driven negotiation. When a cache is supplied with
934         a form of the list of available representations of the response (as in agent-driven negotiation) and the dimensions of variance
935         are completely understood by the cache, then the cache becomes capable of performing server-driven negotiation on behalf of
936         the origin server for subsequent requests on that resource.
937      </p>
938      <p id="rfc.section.5.3.p.2">Transparent negotiation has the advantage of distributing the negotiation work that would otherwise be required of the origin
939         server and also removing the second request delay of agent-driven negotiation when the cache is able to correctly guess the
940         right response.
941      </p>
942      <p id="rfc.section.5.3.p.3">This specification does not define any mechanism for transparent negotiation, though it also does not prevent any such mechanism
943         from being developed as an extension that could be used within HTTP/1.1.
944      </p>
945      <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>
946      <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>
947      <p id="rfc.section.6.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
948         receives the entity.
949      </p>
950      <div id="rfc.iref.a.1"></div>
951      <div id="rfc.iref.h.1"></div>
952      <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>
953      <p id="rfc.section.6.1.p.1">The Accept request-header field can be used to specify certain media types which are acceptable for the response. Accept headers
954         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
955         for an in-line image.
956      </p>
957      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.17"></span><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" class="smpl">Accept</a>         = "Accept" ":"
958                   #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
959 
960  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
961                   | ( <a href="#media.types" class="smpl">type</a> "/" "*" )
962                   | ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> )
963                   ) *( ";" <a href="#rule.parameter" class="smpl">parameter</a> )
964  <a href="#header.accept" class="smpl">accept-params</a>  = ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-extension</a> )
965  <a href="#header.accept" class="smpl">accept-extension</a> = ";" <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> | <a href="#notation" class="smpl">quoted-string</a> ) ]
966</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
967         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
968      </p>
969      <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
970         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
971         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="#quality.values" title="Quality Values">Section&nbsp;3.4</a>). The default value is q=1.
972      </p>
973      <ul class="empty">
974         <li> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
975            Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
976            be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
977            in Accept. Future media types are discouraged from registering any parameter named "q".
978         </li>
979      </ul>
980      <p id="rfc.section.6.1.p.5">The example</p>
981      <div id="rfc.figure.u.18"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
982</pre><p id="rfc.section.6.1.p.7"> <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
983         quality."
984      </p>
985      <p id="rfc.section.6.1.p.8">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field
986         is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then
987         the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response.
988      </p>
989      <p id="rfc.section.6.1.p.9">A more elaborate example is</p>
990      <div id="rfc.figure.u.19"></div><pre class="text">    Accept: text/plain; q=0.5, text/html,
991            text/x-dvi; q=0.8, text/x-c
992</pre><p id="rfc.section.6.1.p.11">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
993         send the text/x-dvi entity, and if that does not exist, send the text/plain entity."
994      </p>
995      <p id="rfc.section.6.1.p.12">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
996         to a given type, the most specific reference has precedence. For example,
997      </p>
998      <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
999</pre><p id="rfc.section.6.1.p.14">have the following precedence:</p>
1000      <div id="rfc.figure.u.21"></div><pre class="text">    1) text/html;level=1
1001    2) text/html
1002    3) text/*
1003    4) */*
1004</pre><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
1005         which matches that type. For example,
1006      </p>
1007      <div id="rfc.figure.u.22"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
1008            text/html;level=2;q=0.4, */*;q=0.5
1009</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
1010      <div id="rfc.figure.u.23"></div><pre class="text">    text/html;level=1         = 1
1011    text/html                 = 0.7
1012    text/plain                = 0.3
1013    image/jpeg                = 0.5
1014    text/html;level=2         = 0.4
1015    text/html;level=3         = 0.7
1016</pre><p id="rfc.section.6.1.p.20"> <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
1017         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
1018      </p>
1019      <div id="rfc.iref.a.2"></div>
1020      <div id="rfc.iref.h.2"></div>
1021      <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>
1022      <p id="rfc.section.6.2.p.1">The Accept-Charset request-header field can be used to indicate what character sets are acceptable for the response. This
1023         field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability
1024         to a server which is capable of representing documents in those character sets.
1025      </p>
1026      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":"
1027          1#( ( <a href="#rule.charset" class="smpl">charset</a> | "*" ) [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] )
1028</pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section&nbsp;3.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
1029         example is
1030      </p>
1031      <div id="rfc.figure.u.25"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1032</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
1033         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
1034         not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly
1035         mentioned.
1036      </p>
1037      <p id="rfc.section.6.2.p.6">If no Accept-Charset header is present, the default is that any character set is acceptable. If an Accept-Charset header is
1038         present, and if the server cannot send a response which is acceptable according to the Accept-Charset header, 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.
1039      </p>
1040      <div id="rfc.iref.a.3"></div>
1041      <div id="rfc.iref.h.3"></div>
1042      <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>
1043      <p id="rfc.section.6.3.p.1">The Accept-Encoding request-header field is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>) that are acceptable in the response.
1044      </p>
1045      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = "Accept-Encoding" ":"
1046                     #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] )
1047  <a href="#header.accept-encoding" class="smpl">codings</a>          = ( <a href="#content.codings" class="smpl">content-coding</a> | "*" )
1048</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.
1049      </p>
1050      <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
1051      <div id="rfc.figure.u.27"></div><pre class="text">    Accept-Encoding: compress, gzip
1052    Accept-Encoding:
1053    Accept-Encoding: *
1054    Accept-Encoding: compress;q=0.5, gzip;q=1.0
1055    Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
1056</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>
1057      <ol>
1058         <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it
1059            is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section&nbsp;3.4</a>, a qvalue of 0 means "not acceptable.")
1060         </li>
1061         <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
1062            field.
1063         </li>
1064         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
1065         <li>The "identity" content-coding is always acceptable, unless specifically refused because the Accept-Encoding field includes
1066            "identity;q=0", or because the field includes "*;q=0" and does not explicitly include the "identity" content-coding. If the
1067            Accept-Encoding field-value is empty, then only the "identity" encoding is acceptable.
1068         </li>
1069      </ol>
1070      <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
1071         to the Accept-Encoding header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
1072      </p>
1073      <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,
1074         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
1075         client.
1076      </p>
1077      <ul class="empty">
1078         <li> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings
1079            commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display
1080            messages sent with other content-codings. The server might also make this decision based on information about the particular
1081            user-agent or client.
1082         </li>
1083         <li> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
1084            not work and are not permitted with x-gzip or x-compress.
1085         </li>
1086      </ul>
1087      <div id="rfc.iref.a.4"></div>
1088      <div id="rfc.iref.h.4"></div>
1089      <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>
1090      <p id="rfc.section.6.4.p.1">The Accept-Language request-header field is similar to Accept, but restricts the set of natural languages that are preferred
1091         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>.
1092      </p>
1093      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":"
1094                    1#( <a href="#header.accept-language" class="smpl">language-range</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] )
1095  <a href="#header.accept-language" class="smpl">language-range</a>  = ( ( 1*8<a href="#notation" class="smpl">ALPHA</a> *( "-" 1*8<a href="#notation" class="smpl">ALPHA</a> ) ) | "*" )
1096</pre><p id="rfc.section.6.4.p.3">Each language-range <em class="bcp14">MAY</em> be given an associated quality value which represents an estimate of the user's preference for the languages specified by
1097         that range. The quality value defaults to "q=1". For example,
1098      </p>
1099      <div id="rfc.figure.u.29"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
1100</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag
1101         if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the
1102         prefix is "-". The special range "*", if present in the Accept-Language field, matches every tag not matched by any other
1103         range present in the Accept-Language field.
1104      </p>
1105      <ul class="empty">
1106         <li> <b>Note:</b> This use of a prefix matching rule does not imply that language tags are assigned to languages in such a way that it is always
1107            true that if a user understands a language with a certain tag, then this user will also understand all languages with tags
1108            for which this tag is a prefix. The prefix rule simply allows the use of prefix tags if this is the case.
1109         </li>
1110      </ul>
1111      <p id="rfc.section.6.4.p.6">The language quality factor assigned to a language-tag by the Accept-Language field is the quality value of the longest language-range
1112         in the field that matches the language-tag. If no language-range in the field matches the tag, the language quality factor
1113         assigned is 0. If no Accept-Language header is present in the request, the server <em class="bcp14">SHOULD</em> assume that all languages are equally acceptable. If an Accept-Language header is present, then all languages which are assigned
1114         a quality factor greater than 0 are acceptable.
1115      </p>
1116      <p id="rfc.section.6.4.p.7">It might be contrary to the privacy expectations of the user to send an Accept-Language header with the complete linguistic
1117         preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.headers" title="Privacy Issues Connected to Accept Headers">Section&nbsp;8.1</a>.
1118      </p>
1119      <p id="rfc.section.6.4.p.8">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
1120         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.
1121      </p>
1122      <ul class="empty">
1123         <li> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
1124            familiar with the details of language matching as described above, and should provide appropriate guidance. As an example,
1125            users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
1126            A user agent might suggest in such a case to add "en" to get the best matching behavior.
1127         </li>
1128      </ul>
1129      <div id="rfc.iref.c.2"></div>
1130      <div id="rfc.iref.h.5"></div>
1131      <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>
1132      <p id="rfc.section.6.5.p.1">The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional
1133         content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain
1134         the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed
1135         without losing the identity of its underlying media type.
1136      </p>
1137      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>  = "Content-Encoding" ":" 1#<a href="#content.codings" class="smpl">content-coding</a>
1138</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>. An example of its use is
1139      </p>
1140      <div id="rfc.figure.u.31"></div><pre class="text">    Content-Encoding: gzip
1141</pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the entity identified by the Request-URI. Typically, the entity-body is stored with
1142         this encoding and is only decoded before rendering or analogous usage. However, a non-transparent 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
1143         directive is present in the message.
1144      </p>
1145      <p id="rfc.section.6.5.p.6">If the content-coding of an entity is not "identity", then the response <em class="bcp14">MUST</em> include a Content-Encoding entity-header (<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.
1146      </p>
1147      <p id="rfc.section.6.5.p.7">If the content-coding of an entity 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).
1148      </p>
1149      <p id="rfc.section.6.5.p.8">If multiple encodings have been applied to an entity, 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 entity-header fields not defined by this specification.
1150      </p>
1151      <div id="rfc.iref.c.3"></div>
1152      <div id="rfc.iref.h.6"></div>
1153      <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>
1154      <p id="rfc.section.6.6.p.1">The Content-Language entity-header field describes the natural language(s) of the intended audience for the enclosed entity.
1155         Note that this might not be equivalent to all the languages used within the entity-body.
1156      </p>
1157      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>  = "Content-Language" ":" 1#<a href="#language.tags" class="smpl">language-tag</a>
1158</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's
1159         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is
1160      </p>
1161      <div id="rfc.figure.u.33"></div><pre class="text">    Content-Language: da
1162</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
1163         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
1164         it is intended.
1165      </p>
1166      <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
1167         simultaneously in the original Maori and English versions, would call for
1168      </p>
1169      <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: mi, en
1170</pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic
1171         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended
1172         to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
1173      </p>
1174      <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.
1175      </p>
1176      <div id="rfc.iref.c.4"></div>
1177      <div id="rfc.iref.h.7"></div>
1178      <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>
1179      <p id="rfc.section.6.7.p.1">The Content-Location entity-header field <em class="bcp14">MAY</em> be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location
1180         separate from the requested resource's URI. A server <em class="bcp14">SHOULD</em> provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has
1181         multiple entities associated with it, and those entities actually have separate locations by which they might be individually
1182         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
1183      </p>
1184      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":"
1185                    ( <a href="#abnf.dependencies" class="smpl">absoluteURI</a> | <a href="#abnf.dependencies" class="smpl">relativeURI</a> )
1186</pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p>
1187      <p id="rfc.section.6.7.p.4">The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of
1188         the resource corresponding to this particular entity at the time of the request. Future requests <em class="bcp14">MAY</em> specify the Content-Location URI as the request-URI if the desire is to identify the source of that particular entity.
1189      </p>
1190      <p id="rfc.section.6.7.p.5">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond
1191         to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple
1192         entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
1193      </p>
1194      <p id="rfc.section.6.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the Request-URI.</p>
1195      <p id="rfc.section.6.7.p.7">The meaning of the Content-Location header in PUT or POST requests is undefined; servers are free to ignore it in those cases.</p>
1196      <div id="rfc.iref.c.5"></div>
1197      <div id="rfc.iref.h.8"></div>
1198      <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>
1199      <p id="rfc.section.6.8.p.1">The Content-MD5 entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body.
1200         (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious
1201         attacks.)
1202      </p>
1203      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#header.content-md5" class="smpl">md5-digest</a>
1204  <a href="#header.content-md5" class="smpl">md5-digest</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;
1205</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 entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including
1206         gateways and proxies, <em class="bcp14">MAY</em> check that the digest value in this header field matches that of the entity-body as received.
1207      </p>
1208      <p id="rfc.section.6.8.p.4">The MD5 digest is computed based on the content of the entity-body, including any content-coding that has been applied, but
1209         not including any transfer-encoding applied to the message-body. If the message is received with a transfer-encoding, that
1210         encoding <em class="bcp14">MUST</em> be removed prior to checking the Content-MD5 value against the received entity.
1211      </p>
1212      <p id="rfc.section.6.8.p.5">This has the result that the digest is computed on the octets of the entity-body exactly as, and in the order that, they would
1213         be sent if no transfer-encoding were being applied.
1214      </p>
1215      <p id="rfc.section.6.8.p.6">HTTP extends RFC 1864 to permit the digest to be computed for MIME composite media-types (e.g., multipart/* and message/rfc822),
1216         but this does not change how the digest is computed as defined in the preceding paragraph.
1217      </p>
1218      <p id="rfc.section.6.8.p.7">There are several consequences of this. The entity-body for composite types <em class="bcp14">MAY</em> contain many body-parts, each with its own MIME and HTTP headers (including Content-MD5, Content-Transfer-Encoding, and Content-Encoding
1219         headers). If a body-part has a Content-Transfer-Encoding or Content-Encoding header, it is assumed that the content of the
1220         body-part has had the encoding applied, and the body-part is included in the Content-MD5 digest as is -- i.e., after the application.
1221         The Transfer-Encoding header field is not allowed within body-parts.
1222      </p>
1223      <p id="rfc.section.6.8.p.8">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.
1224      </p>
1225      <ul class="empty">
1226         <li> <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
1227            ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One
1228            is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another
1229            is that HTTP more frequently uses binary content types than MIME, so it is worth noting that, in such cases, the byte order
1230            used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types
1231            with any of several line break conventions and not just the canonical form using CRLF.
1232         </li>
1233      </ul>
1234      <div id="rfc.iref.c.6"></div>
1235      <div id="rfc.iref.h.9"></div>
1236      <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>
1237      <p id="rfc.section.6.9.p.1">The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of
1238         the HEAD method, the media type that would have been sent had the request been a GET.
1239      </p>
1240      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#media.types" class="smpl">media-type</a>
1241</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;3.3</a>. An example of the field is
1242      </p>
1243      <div id="rfc.figure.u.38"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
1244</pre><p id="rfc.section.6.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section&nbsp;4.2.1</a>.
1245      </p>
1246      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
1247      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
1248      <p id="rfc.section.7.1.p.1">The Message Header 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; should 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>):
1249      </p>
1250      <div id="rfc.table.u.1">
1251         <table class="tt full center" cellpadding="3" cellspacing="0">
1252            <thead>
1253               <tr>
1254                  <th>Header Field Name</th>
1255                  <th>Protocol</th>
1256                  <th>Status</th>
1257                  <th>Reference</th>
1258               </tr>
1259            </thead>
1260            <tbody>
1261               <tr>
1262                  <td class="left">Accept</td>
1263                  <td class="left">http</td>
1264                  <td class="left">standard</td>
1265                  <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.1</a> 
1266                  </td>
1267               </tr>
1268               <tr>
1269                  <td class="left">Accept-Charset</td>
1270                  <td class="left">http</td>
1271                  <td class="left">standard</td>
1272                  <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.2</a> 
1273                  </td>
1274               </tr>
1275               <tr>
1276                  <td class="left">Accept-Encoding</td>
1277                  <td class="left">http</td>
1278                  <td class="left">standard</td>
1279                  <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3</a> 
1280                  </td>
1281               </tr>
1282               <tr>
1283                  <td class="left">Accept-Language</td>
1284                  <td class="left">http</td>
1285                  <td class="left">standard</td>
1286                  <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.4</a> 
1287                  </td>
1288               </tr>
1289               <tr>
1290                  <td class="left">Content-Disposition</td>
1291                  <td class="left">http</td>
1292                  <td class="left">&nbsp;</td>
1293                  <td class="left"> <a href="#content-disposition" id="rfc.xref.content-disposition.1" title="Content-Disposition">Appendix&nbsp;B.1</a> 
1294                  </td>
1295               </tr>
1296               <tr>
1297                  <td class="left">Content-Encoding</td>
1298                  <td class="left">http</td>
1299                  <td class="left">standard</td>
1300                  <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;6.5</a> 
1301                  </td>
1302               </tr>
1303               <tr>
1304                  <td class="left">Content-Language</td>
1305                  <td class="left">http</td>
1306                  <td class="left">standard</td>
1307                  <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;6.6</a> 
1308                  </td>
1309               </tr>
1310               <tr>
1311                  <td class="left">Content-Location</td>
1312                  <td class="left">http</td>
1313                  <td class="left">standard</td>
1314                  <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;6.7</a> 
1315                  </td>
1316               </tr>
1317               <tr>
1318                  <td class="left">Content-MD5</td>
1319                  <td class="left">http</td>
1320                  <td class="left">standard</td>
1321                  <td class="left"> <a href="#header.content-md5" id="rfc.xref.header.content-md5.2" title="Content-MD5">Section&nbsp;6.8</a> 
1322                  </td>
1323               </tr>
1324               <tr>
1325                  <td class="left">Content-Type</td>
1326                  <td class="left">http</td>
1327                  <td class="left">standard</td>
1328                  <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;6.9</a> 
1329                  </td>
1330               </tr>
1331            </tbody>
1332         </table>
1333      </div>
1334      <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1335      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1336      <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
1337         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
1338         make some suggestions for reducing security risks.
1339      </p>
1340      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="privacy.issues.connected.to.accept.headers" href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></h2>
1341      <p id="rfc.section.8.1.p.1">Accept request-headers can reveal information about the user to all servers which are accessed. The Accept-Language header
1342         in particular can reveal information the user would consider to be of a private nature, because the understanding of particular
1343         languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option
1344         to configure the contents of an Accept-Language header to be sent in every request are strongly encouraged to let the configuration
1345         process include a message which makes the user aware of the loss of privacy involved.
1346      </p>
1347      <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 headers by default,
1348         and to ask the user whether or not to start sending Accept-Language headers to a server if it detects, by looking for any
1349         Vary response-header fields generated by the server, that such sending could improve the quality of service.
1350      </p>
1351      <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
1352         used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
1353         to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
1354         of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
1355         also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
1356         be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
1357         filter the accept headers 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.
1358      </p>
1359      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="content-disposition.issues" href="#content-disposition.issues">Content-Disposition Issues</a></h2>
1360      <p id="rfc.section.8.2.p.1"> <a href="#RFC1806" id="rfc.xref.RFC1806.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>, from which the often implemented Content-Disposition (see <a href="#content-disposition" id="rfc.xref.content-disposition.2" title="Content-Disposition">Appendix&nbsp;B.1</a>) header in HTTP is derived, has a number of very serious security considerations. Content-Disposition is not part of the
1361         HTTP standard, but since it is widely implemented, we are documenting its use and risks for implementors. See <a href="#RFC2183" id="rfc.xref.RFC2183.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> (which updates <a href="#RFC1806" id="rfc.xref.RFC1806.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>) for details.
1362      </p>
1363      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
1364      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
1365      </h1>
1366      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
1367      </h2>
1368      <table>                           
1369         <tr>
1370            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
1371            <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>
1372         </tr>
1373         <tr>
1374            <td class="reference"><b id="Part1">[Part1]</b></td>
1375            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-03">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-03 (work in progress), June&nbsp;2008.
1376            </td>
1377         </tr>
1378         <tr>
1379            <td class="reference"><b id="Part2">[Part2]</b></td>
1380            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-03">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-03 (work in progress), June&nbsp;2008.
1381            </td>
1382         </tr>
1383         <tr>
1384            <td class="reference"><b id="Part4">[Part4]</b></td>
1385            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-03">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-03 (work in progress), June&nbsp;2008.
1386            </td>
1387         </tr>
1388         <tr>
1389            <td class="reference"><b id="Part5">[Part5]</b></td>
1390            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-03">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-03 (work in progress), June&nbsp;2008.
1391            </td>
1392         </tr>
1393         <tr>
1394            <td class="reference"><b id="Part6">[Part6]</b></td>
1395            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-p6-cache-03">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-03 (work in progress), June&nbsp;2008.
1396            </td>
1397         </tr>
1398         <tr>
1399            <td class="reference"><b id="RFC1766">[RFC1766]</b></td>
1400            <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc1766">Tags for the Identification of Languages</a>”, RFC&nbsp;1766, March&nbsp;1995.
1401            </td>
1402         </tr>
1403         <tr>
1404            <td class="reference"><b id="RFC1864">[RFC1864]</b></td>
1405            <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.
1406            </td>
1407         </tr>
1408         <tr>
1409            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
1410            <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>RFC1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
1411               was present since <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
1412            </td>
1413         </tr>
1414         <tr>
1415            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
1416            <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>RFC1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
1417               was present since <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
1418            </td>
1419         </tr>
1420         <tr>
1421            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
1422            <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>RFC1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference
1423               was present since <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice.
1424            </td>
1425         </tr>
1426         <tr>
1427            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
1428            <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.
1429            </td>
1430         </tr>
1431         <tr>
1432            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1433            <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.
1434            </td>
1435         </tr>
1436         <tr>
1437            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1438            <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.
1439            </td>
1440         </tr>
1441      </table>
1442      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
1443      </h2>
1444      <table>                           
1445         <tr>
1446            <td class="reference"><b id="RFC1806">[RFC1806]</b></td>
1447            <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a> and <a href="mailto:sdorner@qualcomm.com" title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC&nbsp;1806, June&nbsp;1995.
1448            </td>
1449         </tr>
1450         <tr>
1451            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
1452            <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.
1453            </td>
1454         </tr>
1455         <tr>
1456            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
1457            <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.
1458            </td>
1459         </tr>
1460         <tr>
1461            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
1462            <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.
1463            </td>
1464         </tr>
1465         <tr>
1466            <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
1467            <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.
1468            </td>
1469         </tr>
1470         <tr>
1471            <td class="reference"><b id="RFC2183">[RFC2183]</b></td>
1472            <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a>, <a href="mailto:sdorner@qualcomm.com" title="QUALCOMM Incorporated">Dorner, S.</a>, and <a href="mailto:moore@cs.utk.edu" title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC&nbsp;2183, August&nbsp;1997.
1473            </td>
1474         </tr>
1475         <tr>
1476            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
1477            <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.
1478            </td>
1479         </tr>
1480         <tr>
1481            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
1482            <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.
1483            </td>
1484         </tr>
1485         <tr>
1486            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
1487            <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.
1488            </td>
1489         </tr>
1490         <tr>
1491            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1492            <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.
1493            </td>
1494         </tr>
1495         <tr>
1496            <td class="reference"><b id="RFC2822">[RFC2822]</b></td>
1497            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc2822">Internet Message Format</a>”, RFC&nbsp;2822, April&nbsp;2001.
1498            </td>
1499         </tr>
1500         <tr>
1501            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
1502            <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>”, RFC&nbsp;3629, STD&nbsp;63, November&nbsp;2003.
1503            </td>
1504         </tr>
1505         <tr>
1506            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1507            <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.
1508            </td>
1509         </tr>
1510         <tr>
1511            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1512            <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.
1513            </td>
1514         </tr>
1515      </table>
1516      <div class="avoidbreak">
1517         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1518         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1519               (editor)
1520               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></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>
1521         <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">One Laptop per Child</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@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
1522         <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>
1523         <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>
1524         <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>
1525         <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>
1526         <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>
1527         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1528               (editor)
1529               <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>
1530         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1531               (editor)
1532               <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>
1533      </div>
1534      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="differences.between.http.entities.and.rfc.2045.entities" href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a></h1>
1535      <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</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 entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 2045
1536         discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully
1537         chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, to make date
1538         comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
1539      </p>
1540      <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from RFC 2045. 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
1541         to HTTP also need to be aware of the differences because some conversions might be required.
1542      </p>
1543      <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>
1544      <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 general-header field to indicate what version of the MIME protocol was used to construct the
1545         message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as
1546         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
1547         environments.
1548      </p>
1549      <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
1550</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
1551         document and not the MIME specification.
1552      </p>
1553      <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>
1554      <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity 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;3.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.3"><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
1555         break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
1556         over HTTP.
1557      </p>
1558      <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;3.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
1559         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
1560         CR and LF, as is the case for some multi-byte character sets.
1561      </p>
1562      <p id="rfc.section.A.2.p.3">Implementors should note that conversion will break any cryptographic checksums applied to the original content unless the
1563         original content is already in canonical form. Therefore, the canonical form is recommended for any content that uses such
1564         checksums in HTTP.
1565      </p>
1566      <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
1567      <p id="rfc.section.A.3.p.1">RFC 2045 does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier
1568         on 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 entity-body before forwarding the message. (Some experimental
1569         applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;" to perform
1570         a function equivalent to Content-Encoding. However, this parameter is not part of RFC 2045).
1571      </p>
1572      <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
1573      <p id="rfc.section.A.4.p.1">HTTP does not use the Content-Transfer-Encoding field of RFC 2045. 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.
1574      </p>
1575      <p id="rfc.section.A.4.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
1576         format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
1577         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
1578         the destination protocol.
1579      </p>
1580      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
1581      <p id="rfc.section.A.5.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</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>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
1582      </p>
1583      <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
1584      <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.1"><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
1585         fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
1586         and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;3.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
1587      </p>
1588      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
1589      <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
1590         applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
1591         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
1592         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
1593      </p>
1594      <p id="rfc.section.B.p.2">A number of other headers, 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>).
1595      </p>
1596      <div id="rfc.iref.h.10"></div>
1597      <div id="rfc.iref.c.7"></div>
1598      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2>
1599      <p id="rfc.section.B.1.p.1">The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename
1600         if the user requests that the content is saved to a file. This usage is derived from the definition of Content-Disposition
1601         in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>.
1602      </p>
1603      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":"
1604                        <a href="#content-disposition" class="smpl">disposition-type</a> *( ";" <a href="#content-disposition" class="smpl">disposition-parm</a> )
1605  <a href="#content-disposition" class="smpl">disposition-type</a> = "attachment" | <a href="#content-disposition" class="smpl">disp-extension-token</a>
1606  <a href="#content-disposition" class="smpl">disposition-parm</a> = <a href="#content-disposition" class="smpl">filename-parm</a> | <a href="#content-disposition" class="smpl">disp-extension-parm</a>
1607  <a href="#content-disposition" class="smpl">filename-parm</a> = "filename" "=" <a href="#notation" class="smpl">quoted-string</a>
1608  <a href="#content-disposition" class="smpl">disp-extension-token</a> = <a href="#notation" class="smpl">token</a>
1609  <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#notation" class="smpl">token</a> "=" ( <a href="#notation" class="smpl">token</a> | <a href="#notation" class="smpl">quoted-string</a> )
1610</pre><p id="rfc.section.B.1.p.3">An example is</p>
1611      <div id="rfc.figure.u.41"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
1612</pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply
1613         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
1614      </p>
1615      <p id="rfc.section.B.1.p.6">If this header is used in a response with the application/octet-stream content-type, the implied suggestion is that the user
1616         agent should not display the response, but directly enter a `save response as...' dialog.
1617      </p>
1618      <p id="rfc.section.B.1.p.7">See <a href="#content-disposition.issues" title="Content-Disposition Issues">Section&nbsp;8.2</a> for Content-Disposition security issues.
1619      </p>
1620      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
1621      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
1622      <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
1623         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
1624         computed. (<a href="#entity.length" title="Entity Length">Section&nbsp;4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
1625      </p>
1626      <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.3" title="Accept-Charset">Section&nbsp;6.2</a>)
1627      </p>
1628      <p id="rfc.section.C.1.p.3">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce
1629         it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>.
1630      </p>
1631      <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>)
1632      </p>
1633      <p id="rfc.section.C.1.p.5">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section&nbsp;3.4</a>)
1634      </p>
1635      <p id="rfc.section.C.1.p.6">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
1636      </p>
1637      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
1638      <p id="rfc.section.C.2.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section&nbsp;3.1</a>)
1639      </p>
1640      <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.4</a>)
1641      </p>
1642      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1643      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
1644      </h2>
1645      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1646      </p>
1647      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
1648      </h2>
1649      <p id="rfc.section.D.2.p.1">Closed issues: </p>
1650      <ul>
1651         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/8">http://www3.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;)
1652         </li>
1653         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/14">http://www3.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;)
1654         </li>
1655         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16">http://www3.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;)
1656         </li>
1657         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
1658         </li>
1659         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
1660         </li>
1661         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
1662         </li>
1663         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/55">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
1664         </li>
1665         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
1666         </li>
1667         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
1668         </li>
1669         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative"
1670         </li>
1671         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
1672         </li>
1673      </ul>
1674      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
1675      </h2>
1676      <p id="rfc.section.D.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1677      </p>
1678      <ul>
1679         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1680      </ul>
1681      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
1682      <p id="rfc.section.D.4.p.1">Closed issues: </p>
1683      <ul>
1684         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/67">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
1685         </li>
1686         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
1687         </li>
1688         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
1689         </li>
1690      </ul>
1691      <p id="rfc.section.D.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1692      </p>
1693      <ul>
1694         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
1695      </ul>
1696      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1697      <p class="noprint"><a href="#rfc.index.A">A</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.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a> 
1698      </p>
1699      <div class="print2col">
1700         <ul class="ind">
1701            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1702                  <li>Accept header&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.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>
1703                  <li>Accept-Charset header&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>, <a href="#rfc.xref.header.accept-charset.3">C.1</a></li>
1704                  <li>Accept-Encoding header&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.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>
1705                  <li>Accept-Language header&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>
1706                  <li>Alternates header&nbsp;&nbsp;<a href="#rfc.iref.a.5"><b>C.1</b></a></li>
1707               </ul>
1708            </li>
1709            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1710                  <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.1">3.2</a></li>
1711                  <li>Content-Base header&nbsp;&nbsp;<a href="#rfc.iref.c.9"><b>C.1</b></a></li>
1712                  <li>Content-Disposition header&nbsp;&nbsp;<a href="#rfc.xref.content-disposition.1">7.1</a>, <a href="#rfc.xref.content-disposition.2">8.2</a>, <a href="#rfc.iref.c.7"><b>B.1</b></a>, <a href="#rfc.extref.c.22">B.1</a></li>
1713                  <li>Content-Encoding header&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.2"><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>
1714                  <li>Content-Language header&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.3"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
1715                  <li>Content-Location header&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.4"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a></li>
1716                  <li>Content-MD5 header&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">4.1</a>, <a href="#rfc.iref.c.5"><b>6.8</b></a>, <a href="#rfc.xref.header.content-md5.2">7.1</a></li>
1717                  <li>Content-Type header&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.6"><b>6.9</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
1718                  <li>Content-Version header&nbsp;&nbsp;<a href="#rfc.iref.c.8"><b>C.1</b></a></li>
1719               </ul>
1720            </li>
1721            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
1722                  <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.d.1">3.2</a></li>
1723                  <li>Derived-From header&nbsp;&nbsp;<a href="#rfc.iref.d.2"><b>C.1</b></a></li>
1724               </ul>
1725            </li>
1726            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1727                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1728                     <ul>
1729                        <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.1</b></a></li>
1730                        <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.2</b></a></li>
1731                        <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.3</b></a></li>
1732                        <li><tt>accept-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.1</b></a></li>
1733                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.4</b></a></li>
1734                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.1</b></a></li>
1735                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.3</b></a></li>
1736                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.1</b></a></li>
1737                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.3</b></a></li>
1738                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.2</b></a></li>
1739                        <li><tt>content-disposition</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>B.1</b></a></li>
1740                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>6.5</b></a></li>
1741                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>6.6</b></a></li>
1742                        <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>6.7</b></a></li>
1743                        <li><tt>Content-MD5</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>6.8</b></a></li>
1744                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>6.9</b></a></li>
1745                        <li><tt>disp-extension-parm</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>B.1</b></a></li>
1746                        <li><tt>disp-extension-token</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>B.1</b></a></li>
1747                        <li><tt>disposition-parm</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>B.1</b></a></li>
1748                        <li><tt>disposition-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>B.1</b></a></li>
1749                        <li><tt>entity-body</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>4.2</b></a></li>
1750                        <li><tt>entity-header</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>4.1</b></a></li>
1751                        <li><tt>extension-header</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>4.1</b></a></li>
1752                        <li><tt>filename-parm</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>B.1</b></a></li>
1753                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>6.4</b></a></li>
1754                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>3.5</b></a></li>
1755                        <li><tt>md5-digest</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>6.8</b></a></li>
1756                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.1</b></a></li>
1757                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.3</b></a></li>
1758                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>A.1</b></a></li>
1759                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.3</b></a></li>
1760                        <li><tt>primary-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.5</b></a></li>
1761                        <li><tt>qvalue</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
1762                        <li><tt>subtag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>3.5</b></a></li>
1763                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.3</b></a></li>
1764                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.3</b></a></li>
1765                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.3</b></a></li>
1766                     </ul>
1767                  </li>
1768                  <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.g.3">3.2</a></li>
1769               </ul>
1770            </li>
1771            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1772                  <li>Headers&nbsp;&nbsp;
1773                     <ul>
1774                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">3.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>
1775                        <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>, <a href="#rfc.xref.header.accept-charset.3">C.1</a></li>
1776                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.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>
1777                        <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>
1778                        <li>Alternate&nbsp;&nbsp;<a href="#rfc.iref.h.11"><b>C.1</b></a></li>
1779                        <li>Content-Base&nbsp;&nbsp;<a href="#rfc.iref.h.17"><b>C.1</b></a></li>
1780                        <li>Content-Disposition&nbsp;&nbsp;<a href="#rfc.xref.content-disposition.1">7.1</a>, <a href="#rfc.xref.content-disposition.2">8.2</a>, <a href="#rfc.iref.h.10"><b>B.1</b></a>, <a href="#rfc.extref.c.22">B.1</a></li>
1781                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.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>
1782                        <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>
1783                        <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></li>
1784                        <li>Content-MD5&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">4.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>
1785                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.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>
1786                        <li>Content-Version&nbsp;&nbsp;<a href="#rfc.iref.h.12"><b>C.1</b></a></li>
1787                        <li>Derived-From&nbsp;&nbsp;<a href="#rfc.iref.h.13"><b>C.1</b></a></li>
1788                        <li>Link&nbsp;&nbsp;<a href="#rfc.iref.h.14"><b>C.1</b></a></li>
1789                        <li>Public&nbsp;&nbsp;<a href="#rfc.iref.h.16"><b>C.1</b></a></li>
1790                        <li>URI&nbsp;&nbsp;<a href="#rfc.iref.h.15"><b>C.1</b></a></li>
1791                     </ul>
1792                  </li>
1793               </ul>
1794            </li>
1795            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1796                  <li>identity&nbsp;&nbsp;<a href="#rfc.iref.i.1">3.2</a></li>
1797                  <li><em>ISO-8859-1</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO-8859-1.1">3.1.1</a>, <a href="#ISO-8859-1"><b>10.1</b></a></li>
1798               </ul>
1799            </li>
1800            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
1801                  <li>Link header&nbsp;&nbsp;<a href="#rfc.iref.l.1"><b>C.1</b></a></li>
1802               </ul>
1803            </li>
1804            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1805                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2</a>, <a href="#rfc.xref.Part1.2">2</a>, <a href="#rfc.xref.Part1.3">2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">2</a>, <a href="#rfc.xref.Part1.8">2</a>, <a href="#rfc.xref.Part1.9">2</a>, <a href="#rfc.xref.Part1.10">2</a>, <a href="#rfc.xref.Part1.11">2</a>, <a href="#rfc.xref.Part1.12">4.1</a>, <a href="#rfc.xref.Part1.13">4.2</a>, <a href="#rfc.xref.Part1.14">4.2.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.15">A.5</a>, <a href="#rfc.xref.Part1.16">C.1</a><ul>
1806                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2</a></li>
1807                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">2</a>, <a href="#rfc.xref.Part1.3">2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">2</a></li>
1808                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">2</a>, <a href="#rfc.xref.Part1.10">2</a></li>
1809                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2</a></li>
1810                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">4.2</a></li>
1811                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">4.2.2</a></li>
1812                        <li><em>Section 8.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">2</a>, <a href="#rfc.xref.Part1.12">4.1</a></li>
1813                        <li><em>Section 8.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">A.5</a></li>
1814                     </ul>
1815                  </li>
1816                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a>, <a href="#Part2"><b>10.1</b></a><ul>
1817                        <li><em>Section 10.9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a></li>
1818                     </ul>
1819                  </li>
1820                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
1821                        <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2</a>, <a href="#rfc.xref.Part4.2">4.1</a></li>
1822                     </ul>
1823                  </li>
1824                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2</a>, <a href="#rfc.xref.Part5.2">3.3.2</a>, <a href="#rfc.xref.Part5.3">4.1</a>, <a href="#Part5"><b>10.1</b></a>, <a href="#rfc.xref.Part5.4">C.1</a><ul>
1825                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2</a>, <a href="#rfc.xref.Part5.3">4.1</a></li>
1826                        <li><em>Appendix A</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.3.2</a></li>
1827                     </ul>
1828                  </li>
1829                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2</a>, <a href="#rfc.xref.Part6.2">4.1</a>, <a href="#rfc.xref.Part6.3">5.1</a>, <a href="#rfc.xref.Part6.4">6.7</a>, <a href="#Part6"><b>10.1</b></a>, <a href="#rfc.xref.Part6.5">C.1</a><ul>
1830                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">6.7</a></li>
1831                        <li><em>Section 16.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2</a>, <a href="#rfc.xref.Part6.2">4.1</a></li>
1832                        <li><em>Section 16.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">5.1</a></li>
1833                     </ul>
1834                  </li>
1835                  <li>Public header&nbsp;&nbsp;<a href="#rfc.iref.p.1"><b>C.1</b></a></li>
1836               </ul>
1837            </li>
1838            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1839                  <li><em>RFC1766</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1766.1">3.5</a>, <a href="#RFC1766"><b>10.1</b></a></li>
1840                  <li><em>RFC1806</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1806.1">8.2</a>, <a href="#rfc.xref.RFC1806.2">8.2</a>, <a href="#RFC1806"><b>10.2</b></a>, <a href="#rfc.xref.RFC1806.3">B.1</a></li>
1841                  <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>
1842                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li>
1843                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">3.2</a>, <a href="#RFC1950"><b>10.1</b></a></li>
1844                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">3.2</a>, <a href="#RFC1951"><b>10.1</b></a></li>
1845                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">3.2</a>, <a href="#RFC1952"><b>10.1</b></a></li>
1846                  <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>, <a href="#rfc.xref.RFC2045.3">A.2</a></li>
1847                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#rfc.xref.RFC2046.2">3.3.2</a>, <a href="#RFC2046"><b>10.1</b></a>, <a href="#rfc.xref.RFC2046.3">A.2</a><ul>
1848                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">3.3.2</a></li>
1849                     </ul>
1850                  </li>
1851                  <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>10.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
1852                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
1853                     </ul>
1854                  </li>
1855                  <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>, <a href="#rfc.xref.RFC2068.5">C.1</a></li>
1856                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
1857                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
1858                  <li><em>RFC2183</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2183.1">8.2</a>, <a href="#RFC2183"><b>10.2</b></a></li>
1859                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">3.1</a>, <a href="#RFC2277"><b>10.2</b></a></li>
1860                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">3.3.2</a>, <a href="#RFC2388"><b>10.2</b></a></li>
1861                  <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#RFC2557"><b>10.2</b></a>, <a href="#rfc.xref.RFC2557.1">A.6</a>, <a href="#rfc.xref.RFC2557.2">C.1</a></li>
1862                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.2">D.1</a></li>
1863                  <li><em>RFC2822</em>&nbsp;&nbsp;<a href="#RFC2822"><b>10.2</b></a>, <a href="#rfc.xref.RFC2822.1">A</a></li>
1864                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">3.1</a>, <a href="#RFC3629"><b>10.2</b></a></li>
1865                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li>
1866                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">3.3</a>, <a href="#RFC4288"><b>10.2</b></a></li>
1867               </ul>
1868            </li>
1869            <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
1870                  <li>URI header&nbsp;&nbsp;<a href="#rfc.iref.u.1"><b>C.1</b></a></li>
1871               </ul>
1872            </li>
1873         </ul>
1874      </div>
1875      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
1876      <p>Copyright © The IETF Trust (2008).</p>
1877      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
1878         authors retain all their rights.
1879      </p>
1880      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
1881         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
1882         DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
1883         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1884      </p>
1885      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
1886      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
1887         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
1888         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
1889         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
1890         BCP 79.
1891      </p>
1892      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
1893         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
1894         of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1895      </p>
1896      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
1897         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
1898         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
1899      </p>
1900   </body>
1901</html>
Note: See TracBrowser for help on using the repository browser.