Ignore:
Timestamp:
14/06/14 11:20:37 (8 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/12/p3-payload.html

    r1051 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>HTTP/1.1, part 3: Message Payload and Content Negotiation</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
     
    3334  margin-left: 2em;
    3435}
    35 dd {
    36   margin-right: 2em;
    37 }
    3836dl {
    3937  margin-left: 2em;
    4038}
    41 
    4239ul.empty {
    4340  list-style-type: none;
     
    5350}
    5451h1 {
    55   font-size: 14pt;
     52  font-size: 130%;
    5653  line-height: 21pt;
    5754  page-break-after: avoid;
     
    6057  page-break-before: always;
    6158}
    62 h1 a {
    63   color: #333333;
    64 }
    6559h2 {
    66   font-size: 12pt;
     60  font-size: 120%;
    6761  line-height: 15pt;
    6862  page-break-after: avoid;
    6963}
    70 h3, h4, h5, h6 {
    71   font-size: 10pt;
     64h3 {
     65  font-size: 110%;
    7266  page-break-after: avoid;
    7367}
    74 h2 a, h3 a, h4 a, h5 a, h6 a {
     68h4, h5, h6 {
     69  page-break-after: avoid;
     70}
     71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7572  color: black;
    7673}
     
    8077li {
    8178  margin-left: 2em;
    82   margin-right: 2em;
    8379}
    8480ol {
    8581  margin-left: 2em;
    86   margin-right: 2em;
     82}
     83ol.la {
     84  list-style-type: lower-alpha;
     85}
     86ol.ua {
     87  list-style-type: upper-alpha;
    8788}
    8889ol p {
     
    9192p {
    9293  margin-left: 2em;
    93   margin-right: 2em;
    9494}
    9595pre {
     
    9797  background-color: lightyellow;
    9898  padding: .25em;
     99  page-break-inside: avoid;
    99100}
    100101pre.text2 {
     
    125126table.tt {
    126127  vertical-align: top;
     128  border-color: gray;
     129}
     130table.tt th {
     131  border-color: gray;
     132}
     133table.tt td {
     134  border-color: gray;
     135}
     136table.all {
     137  border-style: solid;
     138  border-width: 2px;
    127139}
    128140table.full {
    129   border-style: outset;
    130   border-width: 1px;
    131 }
    132 table.headers {
    133   border-style: outset;
    134   border-width: 1px;
     141  border-style: solid;
     142  border-width: 2px;
    135143}
    136144table.tt td {
    137145  vertical-align: top;
    138146}
     147table.all td {
     148  border-style: solid;
     149  border-width: 1px;
     150}
    139151table.full td {
    140   border-style: inset;
     152  border-style: none solid;
    141153  border-width: 1px;
    142154}
     
    144156  vertical-align: top;
    145157}
     158table.all th {
     159  border-style: solid;
     160  border-width: 1px;
     161}
    146162table.full th {
    147   border-style: inset;
    148   border-width: 1px;
     163  border-style: solid;
     164  border-width: 1px 1px 2px 1px;
    149165}
    150166table.headers th {
    151   border-style: none none inset none;
    152   border-width: 1px;
     167  border-style: none none solid none;
     168  border-width: 2px;
    153169}
    154170table.left {
     
    165181  caption-side: bottom;
    166182  font-weight: bold;
    167   font-size: 9pt;
     183  font-size: 10pt;
    168184  margin-top: .5em;
    169185}
     
    172188  border-spacing: 1px;
    173189  width: 95%;
    174   font-size: 10pt;
     190  font-size: 11pt;
    175191  color: white;
    176192}
     
    180196td.topnowrap {
    181197  vertical-align: top;
    182   white-space: nowrap; 
     198  white-space: nowrap;
    183199}
    184200table.header td {
     
    197213  display:table-header-group;
    198214}
    199 ul.toc {
     215ul.toc, ul.toc ul {
    200216  list-style: none;
    201217  margin-left: 1.5em;
    202   margin-right: 0em;
    203218  padding-left: 0em;
    204219}
    205 li.tocline0 {
     220ul.toc li {
    206221  line-height: 150%;
    207222  font-weight: bold;
     223  margin-left: 0em;
     224}
     225ul.toc li li {
     226  line-height: normal;
     227  font-weight: normal;
    208228  font-size: 10pt;
    209229  margin-left: 0em;
    210   margin-right: 0em;
    211 }
    212 li.tocline1 {
    213   line-height: normal;
    214   font-weight: normal;
    215   font-size: 9pt;
    216   margin-left: 0em;
    217   margin-right: 0em;
    218 }
    219 li.tocline2 {
     230}
     231li.excluded {
    220232  font-size: 0pt;
    221233}
     
    223235  margin-left: 0em;
    224236}
    225 ul.ind {
     237.title, .filename, h1, h2, h3, h4 {
     238  font-family: candara, helvetica, arial, sans-serif;
     239}
     240samp, tt, code, pre {
     241  font: consolas, monospace;
     242}
     243ul.ind, ul.ind ul {
    226244  list-style: none;
    227245  margin-left: 1.5em;
    228   margin-right: 0em;
    229246  padding-left: 0em;
    230247  page-break-before: avoid;
    231248}
    232 li.indline0 {
     249ul.ind li {
    233250  font-weight: bold;
    234251  line-height: 200%;
    235252  margin-left: 0em;
    236   margin-right: 0em;
    237 }
    238 li.indline1 {
     253}
     254ul.ind li li {
    239255  font-weight: normal;
    240256  line-height: 150%;
    241257  margin-left: 0em;
    242   margin-right: 0em;
    243258}
    244259.avoidbreak {
     
    264279  font-weight: bold;
    265280  text-align: center;
    266   font-size: 9pt;
     281  font-size: 10pt;
    267282}
    268283.filename {
    269284  color: #333333;
     285  font-size: 75%;
    270286  font-weight: bold;
    271   font-size: 12pt;
    272287  line-height: 21pt;
    273288  text-align: center;
     
    276291  font-weight: bold;
    277292}
    278 .hidden {
    279   display: none;
    280 }
    281293.left {
    282294  text-align: left;
     
    286298}
    287299.title {
    288   color: #990000;
    289   font-size: 18pt;
     300  color: green;
     301  font-size: 150%;
    290302  line-height: 18pt;
    291303  font-weight: bold;
     
    293305  margin-top: 36pt;
    294306}
    295 .vcardline {
    296   display: block;
    297 }
    298307.warning {
    299   font-size: 14pt;
     308  font-size: 130%;
    300309  background-color: yellow;
    301310}
     
    306315    display: none;
    307316  }
    308  
     317
    309318  a {
    310319    color: black;
     
    321330    background-color: white;
    322331    vertical-align: top;
    323     font-size: 12pt;
     332    font-size: 110%;
    324333  }
    325334
    326   ul.toc a::after {
     335  ul.toc a:nth-child(2)::after {
    327336    content: leader('.') target-counter(attr(href), page);
    328337  }
    329  
    330   a.iref {
     338
     339  ul.ind li li a {
    331340    content: target-counter(attr(href), page);
    332341  }
    333  
     342
    334343  .print2col {
    335344    column-count: 2;
     
    341350@page {
    342351  @top-left {
    343        content: "Internet-Draft"; 
    344   } 
     352       content: "Internet-Draft";
     353  }
    345354  @top-right {
    346        content: "October 2010"; 
    347   } 
     355       content: "October 2010";
     356  }
    348357  @top-center {
    349        content: "HTTP/1.1, Part 3"; 
    350   } 
     358       content: "HTTP/1.1, Part 3";
     359  }
    351360  @bottom-left {
    352        content: "Fielding, et al."; 
    353   } 
     361       content: "Fielding, et al.";
     362  }
    354363  @bottom-center {
    355        content: "Standards Track";
    356   } 
     364       content: "Expires April 28, 2011";
     365  }
    357366  @bottom-right {
    358        content: "[Page " counter(page) "]"; 
    359   } 
    360 }
    361 
    362 @page:first { 
     367       content: "[Page " counter(page) "]";
     368  }
     369}
     370
     371@page:first {
    363372    @top-left {
    364373      content: normal;
     
    390399      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    391400      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    392       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.524, 2010-09-14 12:37:11, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     401      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    393402      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    394403      <meta name="dct.creator" content="Fielding, R.">
     
    419428            </tr>
    420429            <tr>
    421                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     430               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    422431               </td>
    423432               <td class="right">J. Gettys</td>
     
    490499      </table>
    491500      <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-12</span></p>
    492       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     501      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    493502      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    494503         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the
    495504         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    496505         3 defines HTTP message content, metadata, and content negotiation.
    497       </p> 
    498       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     506      </p>
     507      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    499508      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    500509         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    501       </p> 
     510      </p>
    502511      <p>The changes in this draft are summarized in <a href="#changes.since.11" title="Since draft-ietf-httpbis-p3-payload-11">Appendix&nbsp;E.13</a>.
    503       </p>
    504       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    505       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    506       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    507          working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
    508512      </p>
    509       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    510          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    511          in progress”.
    512       </p>
    513       <p>This Internet-Draft will expire on April 28, 2011.</p>
    514       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    515       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    516       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
    517          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    518          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    519          BSD License.
    520       </p>
    521       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    522          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    523          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    524          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    525          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    526          it into languages other than English.
    527       </p>
     513      <div id="rfc.status">
     514         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     515         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     516         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     517            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     518         </p>
     519         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     520            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     521            in progress”.
     522         </p>
     523         <p>This Internet-Draft will expire on April 28, 2011.</p>
     524      </div>
     525      <div id="rfc.copyrightnotice">
     526         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     527         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     528         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     529            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     530            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     531            BSD License.
     532         </p>
     533         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     534            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     535            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     536            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     537            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     538            it into languages other than English.
     539         </p>
     540      </div>
    528541      <hr class="noprint">
    529542      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    530543      <ul class="toc">
    531          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    532                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
    533                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    534                <li class="tocline1">1.3&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    535                      <li class="tocline1">1.3.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    536                      <li class="tocline1">1.3.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     544         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     545               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#terminology">Terminology</a></li>
     546               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     547               <li><a href="#rfc.section.1.3">1.3</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     548                     <li><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     549                     <li><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    537550                  </ul>
    538551               </li>
    539552            </ul>
    540553         </li>
    541          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">
    542                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul class="toc">
    543                      <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
     554         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
     555               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul>
     556                     <li><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
    544557                  </ul>
    545558               </li>
    546                <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul class="toc">
    547                      <li class="tocline1">2.2.1&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
     559               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a><ul>
     560                     <li><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></li>
    548561                  </ul>
    549562               </li>
    550                <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul class="toc">
    551                      <li class="tocline1">2.3.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    552                      <li class="tocline1">2.3.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     563               <li><a href="#rfc.section.2.3">2.3</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     564                     <li><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     565                     <li><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    553566                  </ul>
    554567               </li>
    555                <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
     568               <li><a href="#rfc.section.2.4">2.4</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    556569            </ul>
    557570         </li>
    558          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul class="toc">
    559                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
    560                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
     571         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#payload">Payload</a><ul>
     572               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></li>
     573               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#payload.body">Payload Body</a></li>
    561574            </ul>
    562575         </li>
    563          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul class="toc">
    564                <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
    565                <li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
     576         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
     577               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></li>
     578               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#representation.data">Representation Data</a></li>
    566579            </ul>
    567580         </li>
    568          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul class="toc">
    569                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
    570                <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
     581         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     582               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
     583               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    571584            </ul>
    572585         </li>
    573          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    574                <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    575                <li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    576                <li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    577                <li class="tocline1">6.4&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    578                <li class="tocline1">6.5&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    579                <li class="tocline1">6.6&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    580                <li class="tocline1">6.7&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    581                <li class="tocline1">6.8&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
    582                <li class="tocline1">6.9&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
     586         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     587               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     588               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     589               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     590               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     591               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
     592               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
     593               <li><a href="#rfc.section.6.7">6.7</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
     594               <li><a href="#rfc.section.6.8">6.8</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
     595               <li><a href="#rfc.section.6.9">6.9</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    583596            </ul>
    584597         </li>
    585          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    586                <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    587                <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
     598         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     599               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     600               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></li>
    588601            </ul>
    589602         </li>
    590          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
    591                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
     603         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     604               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></li>
    592605            </ul>
    593606         </li>
    594          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    595          <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    596                <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    597                <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     607         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     608         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     609               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     610               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    598611            </ul>
    599612         </li>
    600          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    601          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul class="toc">
    602                <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
    603                <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
    604                <li class="tocline1">A.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
    605                <li class="tocline1">A.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
    606                <li class="tocline1">A.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
    607                <li class="tocline1">A.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
    608                <li class="tocline1">A.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
     613         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
     614               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     615               <li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
     616               <li><a href="#rfc.section.A.3">A.3</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     617               <li><a href="#rfc.section.A.4">A.4</a>&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
     618               <li><a href="#rfc.section.A.5">A.5</a>&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
     619               <li><a href="#rfc.section.A.6">A.6</a>&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
     620               <li><a href="#rfc.section.A.7">A.7</a>&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
    609621            </ul>
    610622         </li>
    611          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
    612          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    613          <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    614          <li class="tocline0">E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    615                <li class="tocline1">E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
    616                <li class="tocline1">E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
    617                <li class="tocline1">E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
    618                <li class="tocline1">E.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
    619                <li class="tocline1">E.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
    620                <li class="tocline1">E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
    621                <li class="tocline1">E.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
    622                <li class="tocline1">E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
    623                <li class="tocline1">E.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
    624                <li class="tocline1">E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
    625                <li class="tocline1">E.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
    626                <li class="tocline1">E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
    627                <li class="tocline1">E.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
     623         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
     624         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     625         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     626         <li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     627               <li><a href="#rfc.section.E.1">E.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
     628               <li><a href="#rfc.section.E.2">E.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p3-payload-00</a></li>
     629               <li><a href="#rfc.section.E.3">E.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-01</a></li>
     630               <li><a href="#rfc.section.E.4">E.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
     631               <li><a href="#rfc.section.E.5">E.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
     632               <li><a href="#rfc.section.E.6">E.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
     633               <li><a href="#rfc.section.E.7">E.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
     634               <li><a href="#rfc.section.E.8">E.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
     635               <li><a href="#rfc.section.E.9">E.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
     636               <li><a href="#rfc.section.E.10">E.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
     637               <li><a href="#rfc.section.E.11">E.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
     638               <li><a href="#rfc.section.E.12">E.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
     639               <li><a href="#rfc.section.E.13">E.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
    628640            </ul>
    629641         </li>
    630          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     642         <li><a href="#rfc.index">Index</a></li>
     643         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    631644      </ul>
    632       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    633       <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
    634          payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and
    635          the various selection algorithms that are collectively referred to as HTTP content negotiation.
    636       </p>
    637       <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
    638          errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections on
    639          entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
    640          associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
    641          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>.
    642       </p>
    643       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h2>
    644       <p id="rfc.section.1.1.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    645       <p id="rfc.section.1.1.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>content negotiation</dfn> 
    646       </p>
    647       <ul class="empty">
    648          <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
    649             be negotiated (including error responses).
    650          </li>
    651       </ul>
    652       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    653       <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    654          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>.
    655       </p>
    656       <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
    657          protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    658          for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    659          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    660       </p>
    661       <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    662       <p id="rfc.section.1.3.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rule expanded.
    663       </p>
    664       <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    665          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    666          and WSP (whitespace).
    667       </p>
    668       <h3 id="rfc.section.1.3.1"><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    669       <p id="rfc.section.1.3.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    670       </p>
    671       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     645      <div id="introduction">
     646         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     647         <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
     648            payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, and
     649            the various selection algorithms that are collectively referred to as HTTP content negotiation.
     650         </p>
     651         <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
     652            errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections on
     653            entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
     654            associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
     655            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>.
     656         </p>
     657         <div id="terminology">
     658            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#terminology">Terminology</a></h2>
     659            <p id="rfc.section.1.1.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
     660            <p id="rfc.section.1.1.p.2"><span id="rfc.iref.c.1"></span> <dfn>content negotiation</dfn>
     661            </p>
     662            <ul class="empty">
     663               <li>The mechanism for selecting the appropriate representation when servicing a request. The representation in any response can
     664                  be negotiated (including error responses).
     665               </li>
     666            </ul>
     667         </div>
     668         <div id="intro.requirements">
     669            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     670            <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     671               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>.
     672            </p>
     673            <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     674               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     675               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     676               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
     677            </p>
     678         </div>
     679         <div id="notation">
     680            <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     681            <p id="rfc.section.1.3.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rule expanded.
     682            </p>
     683            <p id="rfc.section.1.3.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     684               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     685               and WSP (whitespace).
     686            </p>
     687            <div id="core.rules">
     688               <h3 id="rfc.section.1.3.1"><a href="#rfc.section.1.3.1">1.3.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
     689               <p id="rfc.section.1.3.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     690               </p>
     691               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    672692  <a href="#core.rules" class="smpl">word</a>           = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    673693  <a href="#core.rules" class="smpl">OWS</a>            = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    674 </pre><h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    675       <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
    676       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>   = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
     694</pre></div>
     695            <div id="abnf.dependencies">
     696               <h3 id="rfc.section.1.3.2"><a href="#rfc.section.1.3.2">1.3.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
     697               <p id="rfc.section.1.3.2.p.1">The ABNF rules below are defined in other parts:</p>
     698               <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>   = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
    677699  <a href="#abnf.dependencies" class="smpl">Content-Length</a> = &lt;Content-Length, 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#header.content-length" title="Content-Length">Section 9.2</a>&gt;
    678700  <a href="#abnf.dependencies" class="smpl">partial-URI</a>    = &lt;partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
     
    681703</pre><div id="rfc.figure.u.4"></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 5.2</a>&gt;
    682704</pre><div id="rfc.figure.u.5"></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 3.3</a>&gt;
    683 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    684       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
    685       <p id="rfc.section.2.1.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
    686       <p id="rfc.section.2.1.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence
    687          of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
    688          not all characters might be available in a given character set and a character set might provide more than one sequence of
    689          octets to represent a particular character. This definition is intended to allow various kinds of character encoding, from
    690          simple single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques.
    691          However, the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information
    692          to determine the exact mapping is not permitted.
    693       </p>
    694       <div class="note" id="rfc.section.2.1.p.3">
    695          <p> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding". However, since HTTP and MIME
    696             share the same registry, it is important that the terminology also be shared.
    697          </p>
     705</pre></div>
     706         </div>
    698707      </div>
    699       <div id="rule.charset">
    700          <p id="rfc.section.2.1.p.4">  HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
    701             Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    702          </p>
    703       </div>
    704       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
     708      <div id="protocol.parameters">
     709         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#protocol.parameters">Protocol Parameters</a></h1>
     710         <div id="character.sets">
     711            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#character.sets">Character Sets</a></h2>
     712            <p id="rfc.section.2.1.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
     713            <p id="rfc.section.2.1.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence
     714               of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
     715               not all characters might be available in a given character set and a character set might provide more than one sequence of
     716               octets to represent a particular character. This definition is intended to allow various kinds of character encoding, from
     717               simple single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques.
     718               However, the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information
     719               to determine the exact mapping is not permitted.
     720            </p>
     721            <div class="note" id="rfc.section.2.1.p.3">
     722               <p><b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding". However, since HTTP and MIME
     723                  share the same registry, it is important that the terminology also be shared.
     724               </p>
     725            </div>
     726            <div id="rule.charset">
     727               <p id="rfc.section.2.1.p.4"> HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
     728                  Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
     729               </p>
     730            </div>
     731            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
    705732</pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    706          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.
    707       </p>
    708       <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
    709          token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
    710          value of the charset parameter can be quoted.
    711       </p>
    712       <p id="rfc.section.2.1.p.8">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    713       </p>
    714       <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
    715       <p id="rfc.section.2.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header field without charset parameter incorrectly to mean "recipient
    716          should guess". Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.
    717       </p>
    718       <p id="rfc.section.2.1.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially
    719          displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>.
    720       </p>
    721       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    722       <p id="rfc.section.2.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
    723          are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
    724          of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
    725          directly, and only decoded by the recipient.
    726       </p>
    727       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
     733               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.
     734            </p>
     735            <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header field (in which the charset value is an unquoted
     736               token) and as the value of a parameter in a Content-Type header field (within a request or response), in which case the parameter
     737               value of the charset parameter can be quoted.
     738            </p>
     739            <p id="rfc.section.2.1.p.8">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     740            </p>
     741            <div id="missing.charset">
     742               <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a href="#missing.charset">Missing Charset</a></h3>
     743               <p id="rfc.section.2.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header field without charset parameter incorrectly to mean "recipient
     744                  should guess". Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.
     745               </p>
     746               <p id="rfc.section.2.1.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially
     747                  displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a>.
     748               </p>
     749            </div>
     750         </div>
     751         <div id="content.codings">
     752            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#content.codings">Content Codings</a></h2>
     753            <p id="rfc.section.2.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to a representation. Content codings
     754               are primarily used to allow a representation to be compressed or otherwise usefully transformed without losing the identity
     755               of its underlying media type and without loss of information. Frequently, the representation is stored in coded form, transmitted
     756               directly, and only decoded by the recipient.
     757            </p>
     758            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
    728759</pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    729          mechanism will be required to remove the encoding.
    730       </p>
    731       <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span> 
    732       </p>
    733       <ul class="empty">
    734          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    735          </li>
    736       </ul>
    737       <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span> 
    738       </p>
    739       <ul class="empty">
    740          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    741          </li>
    742       </ul>
    743       <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span> 
    744       </p>
    745       <ul class="empty">
    746          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    747          </li>
    748       </ul>
    749       <p id="rfc.section.2.2.p.7">identity<span id="rfc.iref.i.1"></span><span id="rfc.iref.c.6"></span> 
    750       </p>
    751       <ul class="empty">
    752          <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
    753             header field, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header field.
    754          </li>
    755       </ul>
    756       <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h3>
    757       <p id="rfc.section.2.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
    758       <p id="rfc.section.2.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    759       </p>
    760       <ul>
    761          <li>Name</li>
    762          <li>Description</li>
    763          <li>Pointer to specification text</li>
    764       </ul>
    765       <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 6.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    766       </p>
    767       <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    768       </p>
    769       <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    770       </p>
    771       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    772       <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    773       </p>
    774       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     760               mechanism will be required to remove the encoding.
     761            </p>
     762            <p id="rfc.section.2.2.p.4">compress<span id="rfc.iref.c.2"></span><span id="rfc.iref.c.3"></span>
     763            </p>
     764            <ul class="empty">
     765               <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     766               </li>
     767            </ul>
     768            <p id="rfc.section.2.2.p.5">deflate<span id="rfc.iref.d.1"></span><span id="rfc.iref.c.4"></span>
     769            </p>
     770            <ul class="empty">
     771               <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     772               </li>
     773            </ul>
     774            <p id="rfc.section.2.2.p.6">gzip<span id="rfc.iref.g.3"></span><span id="rfc.iref.c.5"></span>
     775            </p>
     776            <ul class="empty">
     777               <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     778               </li>
     779            </ul>
     780            <p id="rfc.section.2.2.p.7">identity<span id="rfc.iref.i.1"></span><span id="rfc.iref.c.6"></span>
     781            </p>
     782            <ul class="empty">
     783               <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
     784                  header field, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header field.
     785               </li>
     786            </ul>
     787            <div id="content.coding.registry">
     788               <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></h3>
     789               <p id="rfc.section.2.2.1.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p>
     790               <p id="rfc.section.2.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     791               </p>
     792               <ul>
     793                  <li>Name</li>
     794                  <li>Description</li>
     795                  <li>Pointer to specification text</li>
     796               </ul>
     797               <p id="rfc.section.2.2.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), unless the encoding transformation is identical (as it is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 6.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     798               </p>
     799               <p id="rfc.section.2.2.1.p.4">Values to be added to this name space require a specification (see "Specification Required" in <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     800               </p>
     801               <p id="rfc.section.2.2.1.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     802               </p>
     803            </div>
     804         </div>
     805         <div id="media.types">
     806            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#media.types">Media Types</a></h2>
     807            <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
     808            </p>
     809            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    775810  <a href="#media.types" class="smpl">type</a>       = <a href="#core.rules" class="smpl">token</a>
    776811  <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
    777812</pre><div id="rule.parameter">
    778          <p id="rfc.section.2.3.p.3">      Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs.
    779          </p>
    780       </div>
    781       <div id="rfc.figure.u.9"></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>
     813               <p id="rfc.section.2.3.p.3">   Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs.
     814               </p>
     815            </div>
     816            <div id="rfc.figure.u.9"></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>
    782817  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
    783818  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#core.rules" class="smpl">word</a>
    784819</pre><p id="rfc.section.2.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    785          depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    786          of a media-type, depending on its definition within the media type registry.
    787       </p>
    788       <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    789       </p>
    790       <p id="rfc.section.2.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    791          implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    792       </p>
    793       <p id="rfc.section.2.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
    794          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.
    795       </p>
    796       <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    797       <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
    798       </p>
    799       <p id="rfc.section.2.3.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
    800          allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    801          entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
    802          in a character encoding that does not use octets 13 and 10 for CR and LF respectively, as is the case for some multi-byte
    803          character encodings, HTTP allows the use of whatever octet sequences are defined by that character encoding to represent the
    804          equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the payload
    805          body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
    806       </p>
    807       <p id="rfc.section.2.3.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
    808       </p>
    809       <p id="rfc.section.2.3.1.p.4">The "charset" parameter is used with some media types to define the character encoding (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
    810          to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character encodings other than "ISO-8859-1"
    811          or its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;2.1.1</a> for compatibility problems.
    812       </p>
    813       <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    814       <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more representations within a single message-body.
    815          All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts.
    816       </p>
    817       <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. HTTP does
    818          not use the multipart boundary as an indicator of message-body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
    819          each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
    820       </p>
    821       <p id="rfc.section.2.3.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
    822       </p>
    823       <div class="note" id="rfc.section.2.3.2.p.4">
    824          <p> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    825             method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
    826          </p>
     820               depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
     821               of a media-type, depending on its definition within the media type registry.
     822            </p>
     823            <p id="rfc.section.2.3.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
     824            </p>
     825            <p id="rfc.section.2.3.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
     826               implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
     827            </p>
     828            <p id="rfc.section.2.3.p.8">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     829               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.
     830            </p>
     831            <div id="canonicalization.and.text.defaults">
     832               <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     833               <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. A representation transferred via HTTP messages <em class="bcp14">MUST</em> be in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next paragraph.
     834               </p>
     835               <p id="rfc.section.2.3.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
     836                  allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
     837                  entire representation. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as indicating a line break in text media received via HTTP. In addition, if the text is
     838                  in a character encoding that does not use octets 13 and 10 for CR and LF respectively, as is the case for some multi-byte
     839                  character encodings, HTTP allows the use of whatever octet sequences are defined by that character encoding to represent the
     840                  equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the payload
     841                  body; a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
     842               </p>
     843               <p id="rfc.section.2.3.1.p.3">If a representation is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
     844               </p>
     845               <p id="rfc.section.2.3.1.p.4">The "charset" parameter is used with some media types to define the character encoding (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
     846                  to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character encodings other than "ISO-8859-1"
     847                  or its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;2.1.1</a> for compatibility problems.
     848               </p>
     849            </div>
     850            <div id="multipart.types">
     851               <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h3>
     852               <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more representations within a single message-body.
     853                  All multipart types share a common syntax, as defined in <a href="https://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.
     854               </p>
     855               <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. HTTP does
     856                  not use the multipart boundary as an indicator of message-body length.  In all other respects, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
     857                  each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
     858               </p>
     859               <p id="rfc.section.2.3.2.p.3">If an application receives an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
     860               </p>
     861               <div class="note" id="rfc.section.2.3.2.p.4">
     862                  <p><b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
     863                     method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>.
     864                  </p>
     865               </div>
     866            </div>
     867         </div>
     868         <div id="language.tags">
     869            <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#language.tags">Language Tags</a></h2>
     870            <p id="rfc.section.2.4.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
     871               other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
     872               fields.
     873            </p>
     874            <p id="rfc.section.2.4.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
     875               of subtags:
     876            </p>
     877            <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="https://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     878</pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
     879               by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
     880            </p>
     881            <div id="rfc.figure.u.11"></div>
     882            <p>Example tags include:</p><pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
     883</pre><p id="rfc.section.2.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     884            </p>
     885         </div>
    827886      </div>
    828       <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    829       <p id="rfc.section.2.4.p.1">A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to
    830          other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language
    831          fields.
    832       </p>
    833       <p id="rfc.section.2.4.p.2">In summary, a language tag is composed of one or more parts: A primary language subtag followed by a possibly empty series
    834          of subtags:
    835       </p>
    836       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    837 </pre><p id="rfc.section.2.4.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    838          by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    839       </p>
    840       <div id="rfc.figure.u.11"></div>
    841       <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    842 </pre> <p id="rfc.section.2.4.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    843       </p>
    844       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="payload" href="#payload">Payload</a></h1>
    845       <p id="rfc.section.3.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
    846          in the form of header fields, and data, in the form of the sequence of octets in the message-body after any transfer-coding
    847          has been decoded.
    848       </p>
    849       <div id="rfc.iref.p.1"></div>
    850       <p id="rfc.section.3.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
    851          because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
    852          of the representation (e.g., the 206 status code).
    853       </p>
    854       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
    855       <p id="rfc.section.3.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
    856          header fields". The following payload header fields are defined by HTTP/1.1:
    857       </p>
    858       <div id="rfc.figure.u.12"></div><pre>   <a href="#abnf.dependencies" class="smpl">Content-Length</a>           ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a>
     887      <div id="payload">
     888         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#payload">Payload</a></h1>
     889         <p id="rfc.section.3.p.1">HTTP messages <em class="bcp14">MAY</em> transfer a payload if not otherwise restricted by the request method or response status code. The payload consists of metadata,
     890            in the form of header fields, and data, in the form of the sequence of octets in the message-body after any transfer-coding
     891            has been decoded.
     892         </p>
     893         <div id="rfc.iref.p.1"></div>
     894         <p id="rfc.section.3.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
     895            because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
     896            of the representation (e.g., the 206 status code).
     897         </p>
     898         <div id="payload.header.fields">
     899            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#payload.header.fields">Payload Header Fields</a></h2>
     900            <p id="rfc.section.3.1.p.1">HTTP header fields that specifically define the payload, rather than the associated representation, are referred to as "payload
     901               header fields". The following payload header fields are defined by HTTP/1.1:
     902            </p>
     903            <div id="rfc.figure.u.12"></div><pre>   <a href="#abnf.dependencies" class="smpl">Content-Length</a>           ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a>
    859904   <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>
    860905   <a href="#abnf.dependencies" class="smpl">Content-Range</a>            ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a>
    861 </pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    862       <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    863          safe and proper transfer of the message.
    864       </p>
    865       <div id="rfc.iref.r.1"></div>
    866       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
    867       <p id="rfc.section.4.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information
    868          that reflects the state of that resource, as observed at some point in the past (e.g., in a response to GET) or to be desired
    869          at some point in the future (e.g., in a PUT request).
    870       </p>
    871       <p id="rfc.section.4.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
    872          identified by the effective request URI). The precise semantics of a representation are determined by the type of message
    873          (request or response), the request method, the response status code, and the representation metadata. For example, the above
    874          semantic is true for the representation in any 200 (OK) response to GET and for the representation in any PUT request. A 200
    875          response to PUT, in contrast, contains either a representation that describes the successful action or a representation of
    876          the target resource, with the latter indicated by a Content-Location header field with the same value as the effective request
    877          URI. Likewise, response messages with an error status code usually contain a representation that describes the error and what
    878          next steps are suggested for resolving it.
    879       </p>
    880       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
    881       <p id="rfc.section.4.1.p.1">Representation header fields define metadata about the representation data enclosed in the message-body or, if no message-body
    882          is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request with
    883          the same effective request URI.
    884       </p>
    885       <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p>
    886       <div id="rfc.figure.u.13"></div><pre>   <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>
     906</pre></div>
     907         <div id="payload.body">
     908            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#payload.body">Payload Body</a></h2>
     909            <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
     910               safe and proper transfer of the message.
     911            </p>
     912         </div>
     913      </div>
     914      <div id="representation">
     915         <div id="rfc.iref.r.1"></div>
     916         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#representation">Representation</a></h1>
     917         <p id="rfc.section.4.p.1">A "<dfn>representation</dfn>" is information in a format that can be readily communicated from one party to another. A resource representation is information
     918            that reflects the state of that resource, as observed at some point in the past (e.g., in a response to GET) or to be desired
     919            at some point in the future (e.g., in a PUT request).
     920         </p>
     921         <p id="rfc.section.4.p.2">Most, but not all, representations transferred via HTTP are intended to be a representation of the target resource (the resource
     922            identified by the effective request URI). The precise semantics of a representation are determined by the type of message
     923            (request or response), the request method, the response status code, and the representation metadata. For example, the above
     924            semantic is true for the representation in any 200 (OK) response to GET and for the representation in any PUT request. A 200
     925            response to PUT, in contrast, contains either a representation that describes the successful action or a representation of
     926            the target resource, with the latter indicated by a Content-Location header field with the same value as the effective request
     927            URI. Likewise, response messages with an error status code usually contain a representation that describes the error and what
     928            next steps are suggested for resolving it.
     929         </p>
     930         <div id="representation.header.fields">
     931            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#representation.header.fields">Representation Header Fields</a></h2>
     932            <p id="rfc.section.4.1.p.1">Representation header fields define metadata about the representation data enclosed in the message-body or, if no message-body
     933               is present, about the representation that would have been transferred in a 200 response to a simultaneous GET request with
     934               the same effective request URI.
     935            </p>
     936            <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p>
     937            <div id="rfc.figure.u.13"></div><pre>   <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>
    887938   <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>
    888939   <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>
     
    890941   <a href="#abnf.dependencies" class="smpl">Expires</a>                  ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a>
    891942   <a href="#abnf.dependencies" class="smpl">Last-Modified</a>            ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a>
    892 </pre><h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
    893       <p id="rfc.section.4.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
    894          to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    895          the representation metadata header fields.
    896       </p>
    897       <p id="rfc.section.4.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
    898          a two-layer, ordered encoding model:
    899       </p>
    900       <div id="rfc.figure.u.14"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
     943</pre></div>
     944         <div id="representation.data">
     945            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#representation.data">Representation Data</a></h2>
     946            <p id="rfc.section.4.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
     947               to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
     948               the representation metadata header fields.
     949            </p>
     950            <p id="rfc.section.4.2.p.2">The data type of the representation data is determined via the header fields Content-Type and Content-Encoding. These define
     951               a two-layer, ordered encoding model:
     952            </p>
     953            <div id="rfc.figure.u.14"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    901954</pre><p id="rfc.section.4.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload
    902          body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown
    903          to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
    904          of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type.
    905       </p>
    906       <p id="rfc.section.4.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
    907          a given representation, with the result that some clients will examine a response body's content and override the specified
    908          type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
    909          escalation"). Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats
    910          match multiple media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling
    911          such "content sniffing" when it is used.
    912       </p>
    913       <p id="rfc.section.4.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
    914          that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
    915          that defined by the Content-Type.
    916       </p>
    917       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
    918       <p id="rfc.section.5.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
    919          processing. Often, the server has different ways of representing the same information; for example, in different formats,
    920          languages, or using different character encodings.
    921       </p>
    922       <p id="rfc.section.5.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
    923          which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
    924          provides mechanisms for "content negotiation" -- a process of allowing selection of a representation of a given resource,
    925          when more than one is available.
    926       </p>
    927       <p id="rfc.section.5.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
    928          based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
    929          for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
    930          "active content" pattern, where the server returns active content which runs on the client and, based on client available
    931          parameters, selects additional resources to invoke. "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>) has also been proposed.
    932       </p>
    933       <p id="rfc.section.5.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    934          of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    935          a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    936          to choose from is very large, agent-driven negotiation might not be appropriate.
    937       </p>
    938       <p id="rfc.section.5.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
    939          be considered to be the "same information".
    940       </p>
    941       <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>
    942       <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
    943          negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
    944          language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    945          pertaining to the request (such as the network address of the client).
    946       </p>
    947       <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
    948          to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
    949          (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
    950          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.
    951       </p>
    952       <p id="rfc.section.5.1.p.3">Server-driven negotiation has disadvantages: </p>
    953       <ol>
    954          <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
    955             complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
    956             to view it on screen or print it on paper?).
    957          </li>
    958          <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
    959             of responses have multiple representations) and a potential violation of the user's privacy.
    960          </li>
    961          <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
    962          <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
    963       </ol>
    964       <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
    965          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 9.9</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension
    966          header fields not defined by this specification.
    967       </p>
    968       <div class="note" id="rfc.section.5.1.p.5">
    969          <p> <b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
    970          </p>
     955               body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown
     956               to the sender. If the Content-Type header field is not present, it indicates that the sender does not know the media type
     957               of the representation; recipients <em class="bcp14">MAY</em> either assume that the media type is "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="https://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the content to determine its type.
     958            </p>
     959            <p id="rfc.section.4.2.p.5">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     960               a given representation, with the result that some clients will examine a response body's content and override the specified
     961               type. Clients that do so risk drawing incorrect conclusions, which might expose additional security risks (e.g., "privilege
     962               escalation"). Furthermore, it is impossible to determine the sender's intent by examining the data format: many data formats
     963               match multiple media types that differ only in processing semantics. Implementers are encouraged to provide a means of disabling
     964               such "content sniffing" when it is used.
     965            </p>
     966            <p id="rfc.section.4.2.p.6">Content-Encoding is used to indicate any additional content codings applied to the data, usually for the purpose of data compression,
     967               that are a property of the representation. If Content-Encoding is not present, then there is no additional encoding beyond
     968               that defined by the Content-Type.
     969            </p>
     970         </div>
    971971      </div>
    972       <p id="rfc.section.5.1.p.6">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.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.
    973       </p>
    974       <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>
    975       <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
    976          an initial response from the origin server. Selection is based on a list of the available representations of the response
    977          included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
    978          from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the
    979          user selecting from a generated (possibly hypertext) menu.
    980       </p>
    981       <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,
    982          or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
    983          when public caches are used to distribute server load and reduce network usage.
    984       </p>
    985       <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.
    986          This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
    987          for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
    988          and used within HTTP/1.1.
    989       </p>
    990       <p id="rfc.section.5.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
    991          when the server is unwilling or unable to provide a varying response using server-driven negotiation.
    992       </p>
    993       <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>
    994       <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>
    995       <div id="rfc.iref.a.1"></div>
    996       <div id="rfc.iref.h.1"></div>
    997       <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>
    998       <p id="rfc.section.6.1.p.1">The "Accept" request-header field can be used by user agents to specify response media types that are acceptable. Accept header
    999          fields can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of
    1000          a request for an in-line image.
    1001       </p>
    1002       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept" class="smpl">Accept</a>   = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>
     972      <div id="content.negotiation">
     973         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#content.negotiation">Content Negotiation</a></h1>
     974         <p id="rfc.section.5.p.1">HTTP responses include a representation which contains information for interpretation, whether by a human user or for further
     975            processing. Often, the server has different ways of representing the same information; for example, in different formats,
     976            languages, or using different character encodings.
     977         </p>
     978         <p id="rfc.section.5.p.2">HTTP clients and their users might have different or variable capabilities, characteristics or preferences which would influence
     979            which representation, among those available from the server, would be best for the server to deliver. For this reason, HTTP
     980            provides mechanisms for "content negotiation" -- a process of allowing selection of a representation of a given resource,
     981            when more than one is available.
     982         </p>
     983         <p id="rfc.section.5.p.3">This specification defines two patterns of content negotiation; "server-driven", where the server selects the representation
     984            based upon the client's stated preferences, and "agent-driven" negotiation, where the server provides a list of representations
     985            for the client to choose from, based upon their metadata. In addition, there are other patterns: some applications use an
     986            "active content" pattern, where the server returns active content which runs on the client and, based on client available
     987            parameters, selects additional resources to invoke. "Transparent Content Negotiation" (<a href="#RFC2295" id="rfc.xref.RFC2295.1"><cite title="Transparent Content Negotiation in HTTP">[RFC2295]</cite></a>) has also been proposed.
     988         </p>
     989         <p id="rfc.section.5.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
     990            of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
     991            a user-agent), server-driven negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
     992            to choose from is very large, agent-driven negotiation might not be appropriate.
     993         </p>
     994         <p id="rfc.section.5.p.5">Note that in all cases, the supplier of representations has the responsibility for determining which representations might
     995            be considered to be the "same information".
     996         </p>
     997         <div id="server-driven.negotiation">
     998            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
     999            <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
     1000               negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.,
     1001               language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
     1002               pertaining to the request (such as the network address of the client).
     1003            </p>
     1004            <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
     1005               to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response
     1006               (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to
     1007               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.
     1008            </p>
     1009            <p id="rfc.section.5.1.p.3">Server-driven negotiation has disadvantages: </p>
     1010            <ol>
     1011               <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require
     1012                  complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want
     1013                  to view it on screen or print it on paper?).
     1014               </li>
     1015               <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage
     1016                  of responses have multiple representations) and a potential violation of the user's privacy.
     1017               </li>
     1018               <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li>
     1019               <li>It might limit a public cache's ability to use the same response for multiple user's requests.</li>
     1020            </ol>
     1021            <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
     1022               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 9.9</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension
     1023               header fields not defined by this specification.
     1024            </p>
     1025            <div class="note" id="rfc.section.5.1.p.5">
     1026               <p><b>Note:</b> In practice, User-Agent based negotiation is fragile, because new clients might not be recognized.
     1027               </p>
     1028            </div>
     1029            <p id="rfc.section.5.1.p.6">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.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.
     1030            </p>
     1031         </div>
     1032         <div id="agent-driven.negotiation">
     1033            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2>
     1034            <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
     1035               an initial response from the origin server. Selection is based on a list of the available representations of the response
     1036               included within the header fields or body of the initial response, with each representation identified by its own URI. Selection
     1037               from among the representations can be performed automatically (if the user agent is capable of doing so) or manually by the
     1038               user selecting from a generated (possibly hypertext) menu.
     1039            </p>
     1040            <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,
     1041               or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally
     1042               when public caches are used to distribute server load and reduce network usage.
     1043            </p>
     1044            <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.
     1045               This second request is only efficient when caching is used. In addition, this specification does not define any mechanism
     1046               for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension
     1047               and used within HTTP/1.1.
     1048            </p>
     1049            <p id="rfc.section.5.2.p.4">This specification defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation
     1050               when the server is unwilling or unable to provide a varying response using server-driven negotiation.
     1051            </p>
     1052         </div>
     1053      </div>
     1054      <div id="header.fields">
     1055         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     1056         <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>
     1057         <div id="header.accept">
     1058            <div id="rfc.iref.a.1"></div>
     1059            <div id="rfc.iref.h.1"></div>
     1060            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#header.accept">Accept</a></h2>
     1061            <p id="rfc.section.6.1.p.1">The "Accept" request-header field can be used by user agents to specify response media types that are acceptable. Accept header
     1062               fields can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of
     1063               a request for an in-line image.
     1064            </p>
     1065            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept" class="smpl">Accept</a>   = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>
    10031066  <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
    10041067 
     
    10101073  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> [ "=" <a href="#core.rules" class="smpl">word</a> ]
    10111074</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
    1012          all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    1013       </p>
    1014       <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
    1015          "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    1016          agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
    1017       </p>
    1018       <div class="note" id="rfc.section.6.1.p.5">
    1019          <p> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
    1020             Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
    1021             be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
    1022             in Accept. Future media types are discouraged from registering any parameter named "q".
    1023          </p>
    1024       </div>
    1025       <p id="rfc.section.6.1.p.6">The example</p>
    1026       <div id="rfc.figure.u.16"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    1027 </pre><p id="rfc.section.6.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    1028          quality".
    1029       </p>
    1030       <p id="rfc.section.6.1.p.9">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field
    1031          is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then
    1032          the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response.
    1033       </p>
    1034       <p id="rfc.section.6.1.p.10">A more elaborate example is</p>
    1035       <div id="rfc.figure.u.17"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
     1075               all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
     1076            </p>
     1077            <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
     1078               "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
     1079               agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
     1080            </p>
     1081            <div class="note" id="rfc.section.6.1.p.5">
     1082               <p><b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.
     1083                  Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to
     1084                  be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters
     1085                  in Accept. Future media types are discouraged from registering any parameter named "q".
     1086               </p>
     1087            </div>
     1088            <p id="rfc.section.6.1.p.6">The example</p>
     1089            <div id="rfc.figure.u.16"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
     1090</pre><p id="rfc.section.6.1.p.8"><em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
     1091               quality".
     1092            </p>
     1093            <p id="rfc.section.6.1.p.9">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field
     1094               is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then
     1095               the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response.
     1096            </p>
     1097            <p id="rfc.section.6.1.p.10">A more elaborate example is</p>
     1098            <div id="rfc.figure.u.17"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    10361099          text/x-dvi; q=0.8, text/x-c
    10371100</pre><p id="rfc.section.6.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    1038          send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
    1039       </p>
    1040       <p id="rfc.section.6.1.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
    1041          to a given type, the most specific reference has precedence. For example,
    1042       </p>
    1043       <div id="rfc.figure.u.18"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
     1101               send the text/x-dvi representation, and if that does not exist, send the text/plain representation".
     1102            </p>
     1103            <p id="rfc.section.6.1.p.13">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies
     1104               to a given type, the most specific reference has precedence. For example,
     1105            </p>
     1106            <div id="rfc.figure.u.18"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
    10441107</pre><p id="rfc.section.6.1.p.15">have the following precedence: </p>
    1045       <ol>
    1046          <li>text/html;level=1</li>
    1047          <li>text/html</li>
    1048          <li>text/*</li>
    1049          <li>*/*</li>
    1050       </ol>
    1051       <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
    1052          which matches that type. For example,
    1053       </p>
    1054       <div id="rfc.figure.u.19"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     1108            <ol>
     1109               <li>text/html;level=1</li>
     1110               <li>text/html</li>
     1111               <li>text/*</li>
     1112               <li>*/*</li>
     1113            </ol>
     1114            <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
     1115               which matches that type. For example,
     1116            </p>
     1117            <div id="rfc.figure.u.19"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    10551118          text/html;level=2;q=0.4, */*;q=0.5
    10561119</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    1057       <div id="rfc.table.u.1">
    1058          <table class="tt full left" cellpadding="3" cellspacing="0">
    1059             <thead>
    1060                <tr>
    1061                   <th>Media Type</th>
    1062                   <th>Quality Value</th>
    1063                </tr>
    1064             </thead>
    1065             <tbody>
    1066                <tr>
    1067                   <td class="left">text/html;level=1</td>
    1068                   <td class="left">1</td>
    1069                </tr>
    1070                <tr>
    1071                   <td class="left">text/html</td>
    1072                   <td class="left">0.7</td>
    1073                </tr>
    1074                <tr>
    1075                   <td class="left">text/plain</td>
    1076                   <td class="left">0.3</td>
    1077                </tr>
    1078                <tr>
    1079                   <td class="left">image/jpeg</td>
    1080                   <td class="left">0.5</td>
    1081                </tr>
    1082                <tr>
    1083                   <td class="left">text/html;level=2</td>
    1084                   <td class="left">0.4</td>
    1085                </tr>
    1086                <tr>
    1087                   <td class="left">text/html;level=3</td>
    1088                   <td class="left">0.7</td>
    1089                </tr>
    1090             </tbody>
    1091          </table>
    1092       </div>
    1093       <p id="rfc.section.6.1.p.19"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    1094          is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    1095       </p>
    1096       <div id="rfc.iref.a.2"></div>
    1097       <div id="rfc.iref.h.2"></div>
    1098       <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>
    1099       <p id="rfc.section.6.2.p.1">The "Accept-Charset" request-header field can be used by user agents to indicate what response character sets are acceptable.
    1100          This field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability
    1101          to a server which is capable of representing documents in those character sets.
    1102       </p>
    1103       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
     1120            <div id="rfc.table.u.1">
     1121               <table class="tt full left" cellpadding="3" cellspacing="0">
     1122                  <thead>
     1123                     <tr>
     1124                        <th>Media Type</th>
     1125                        <th>Quality Value</th>
     1126                     </tr>
     1127                  </thead>
     1128                  <tbody>
     1129                     <tr>
     1130                        <td class="left">text/html;level=1</td>
     1131                        <td class="left">1</td>
     1132                     </tr>
     1133                     <tr>
     1134                        <td class="left">text/html</td>
     1135                        <td class="left">0.7</td>
     1136                     </tr>
     1137                     <tr>
     1138                        <td class="left">text/plain</td>
     1139                        <td class="left">0.3</td>
     1140                     </tr>
     1141                     <tr>
     1142                        <td class="left">image/jpeg</td>
     1143                        <td class="left">0.5</td>
     1144                     </tr>
     1145                     <tr>
     1146                        <td class="left">text/html;level=2</td>
     1147                        <td class="left">0.4</td>
     1148                     </tr>
     1149                     <tr>
     1150                        <td class="left">text/html;level=3</td>
     1151                        <td class="left">0.7</td>
     1152                     </tr>
     1153                  </tbody>
     1154               </table>
     1155            </div>
     1156            <p id="rfc.section.6.1.p.19"><b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
     1157               is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
     1158            </p>
     1159         </div>
     1160         <div id="header.accept-charset">
     1161            <div id="rfc.iref.a.2"></div>
     1162            <div id="rfc.iref.h.2"></div>
     1163            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#header.accept-charset">Accept-Charset</a></h2>
     1164            <p id="rfc.section.6.2.p.1">The "Accept-Charset" request-header field can be used by user agents to indicate what response character sets are acceptable.
     1165               This field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability
     1166               to a server which is capable of representing documents in those character sets.
     1167            </p>
     1168            <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
    11041169          <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a>
    11051170  <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    11061171                         [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    11071172</pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
    1108          example is
    1109       </p>
    1110       <div id="rfc.figure.u.21"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1173               example is
     1174            </p>
     1175            <div id="rfc.figure.u.21"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    11111176</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
    1112          not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
    1113          not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly
    1114          mentioned.
    1115       </p>
    1116       <p id="rfc.section.6.2.p.6">If no Accept-Charset header field is present, the default is that any character set is acceptable. If an Accept-Charset header
    1117          field is present, and if the server cannot send a response which is acceptable according to the Accept-Charset header field,
    1118          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.
    1119       </p>
    1120       <div id="rfc.iref.a.3"></div>
    1121       <div id="rfc.iref.h.3"></div>
    1122       <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>
    1123       <p id="rfc.section.6.3.p.1">The "Accept-Encoding" request-header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) are acceptable in the response.
    1124       </p>
    1125       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
     1177               not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
     1178               not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly
     1179               mentioned.
     1180            </p>
     1181            <p id="rfc.section.6.2.p.6">If no Accept-Charset header field is present, the default is that any character set is acceptable. If an Accept-Charset header
     1182               field is present, and if the server cannot send a response which is acceptable according to the Accept-Charset header field,
     1183               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.
     1184            </p>
     1185         </div>
     1186         <div id="header.accept-encoding">
     1187            <div id="rfc.iref.a.3"></div>
     1188            <div id="rfc.iref.h.3"></div>
     1189            <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></h2>
     1190            <p id="rfc.section.6.3.p.1">The "Accept-Encoding" request-header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) are acceptable in the response.
     1191            </p>
     1192            <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
    11261193                     <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>
    11271194  <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>  =
     
    11291196  <a href="#header.accept-encoding" class="smpl">codings</a>            = ( <a href="#content.codings" class="smpl">content-coding</a> / "*" )
    11301197</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.
    1131       </p>
    1132       <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
    1133       <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Encoding: compress, gzip
     1198            </p>
     1199            <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
     1200            <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Encoding: compress, gzip
    11341201  Accept-Encoding:
    11351202  Accept-Encoding: *
     
    11371204  Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    11381205</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>
    1139       <ol>
    1140          <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it
    1141             is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
    1142          </li>
    1143          <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
    1144             field.
    1145          </li>
    1146          <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    1147          <li>The "identity" content-coding is always acceptable, unless specifically refused because the Accept-Encoding field includes
    1148             "identity;q=0", or because the field includes "*;q=0" and does not explicitly include the "identity" content-coding. If the
    1149             Accept-Encoding field-value is empty, then only the "identity" encoding is acceptable.
    1150          </li>
    1151       </ol>
    1152       <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
    1153          to the Accept-Encoding header field, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
    1154       </p>
    1155       <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,
    1156          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
    1157          client.
    1158       </p>
    1159       <div class="note" id="rfc.section.6.3.p.9">
    1160          <p> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings
    1161             commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display
    1162             messages sent with other content-codings. The server might also make this decision based on information about the particular
    1163             user-agent or client.
    1164          </p>
    1165       </div>
    1166       <div class="note" id="rfc.section.6.3.p.10">
    1167          <p> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
    1168             not work and are not permitted with x-gzip or x-compress.
    1169          </p>
    1170       </div>
    1171       <div id="rfc.iref.a.4"></div>
    1172       <div id="rfc.iref.h.4"></div>
    1173       <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>
    1174       <p id="rfc.section.6.4.p.1">The "Accept-Language" request-header field can be used by user agents to indicate the set of natural languages that are preferred
    1175          in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
    1176       </p>
    1177       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
     1206            <ol>
     1207               <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it
     1208                  is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 6.4</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
     1209               </li>
     1210               <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header
     1211                  field.
     1212               </li>
     1213               <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
     1214               <li>The "identity" content-coding is always acceptable, unless specifically refused because the Accept-Encoding field includes
     1215                  "identity;q=0", or because the field includes "*;q=0" and does not explicitly include the "identity" content-coding. If the
     1216                  Accept-Encoding field-value is empty, then only the "identity" encoding is acceptable.
     1217               </li>
     1218            </ol>
     1219            <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
     1220               to the Accept-Encoding header field, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
     1221            </p>
     1222            <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,
     1223               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
     1224               client.
     1225            </p>
     1226            <div class="note" id="rfc.section.6.3.p.9">
     1227               <p><b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings
     1228                  commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display
     1229                  messages sent with other content-codings. The server might also make this decision based on information about the particular
     1230                  user-agent or client.
     1231               </p>
     1232            </div>
     1233            <div class="note" id="rfc.section.6.3.p.10">
     1234               <p><b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will
     1235                  not work and are not permitted with x-gzip or x-compress.
     1236               </p>
     1237            </div>
     1238         </div>
     1239         <div id="header.accept-language">
     1240            <div id="rfc.iref.a.4"></div>
     1241            <div id="rfc.iref.h.4"></div>
     1242            <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#header.accept-language">Accept-Language</a></h2>
     1243            <p id="rfc.section.6.4.p.1">The "Accept-Language" request-header field can be used by user agents to indicate the set of natural languages that are preferred
     1244               in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
     1245            </p>
     1246            <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
    11781247                    <a href="#header.accept-language" class="smpl">Accept-Language-v</a>
    11791248  <a href="#header.accept-language" class="smpl">Accept-Language-v</a> =
    11801249                    1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
    11811250  <a href="#header.accept-language" class="smpl">language-range</a>    =
    1182             &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
     1251            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="https://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    11831252</pre><p id="rfc.section.6.4.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the
    1184          languages specified by that range. The quality value defaults to "q=1". For example,
    1185       </p>
    1186       <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    1187 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
    1188       </p>
    1189       <p id="rfc.section.6.4.p.6">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
    1190       </p>
    1191       <div class="note" id="rfc.section.6.4.p.7">
    1192          <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1193          </p>
    1194       </div>
    1195       <p id="rfc.section.6.4.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
    1196          preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;8.1</a>.
    1197       </p>
    1198       <p id="rfc.section.6.4.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
    1199          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.
    1200       </p>
    1201       <div class="note" id="rfc.section.6.4.p.10">
    1202          <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
    1203             familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
    1204             users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
    1205             A user agent might suggest in such a case to add "en" to get the best matching behavior.
    1206          </p>
    1207       </div>
    1208       <div id="rfc.iref.c.7"></div>
    1209       <div id="rfc.iref.h.5"></div>
    1210       <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>
    1211       <p id="rfc.section.6.5.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation, and thus what
    1212          decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding
    1213          is primarily used to allow a representation to be compressed without losing the identity of its underlying media type.
    1214       </p>
    1215       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
     1253               languages specified by that range. The quality value defaults to "q=1". For example,
     1254            </p>
     1255            <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1256</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="https://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
     1257            </p>
     1258            <p id="rfc.section.6.4.p.6">For matching, <a href="https://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements.
     1259            </p>
     1260            <div class="note" id="rfc.section.6.4.p.7">
     1261               <p><b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="https://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="https://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1262               </p>
     1263            </div>
     1264            <p id="rfc.section.6.4.p.8">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     1265               preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.header.fields" title="Privacy Issues Connected to Accept Header Fields">Section&nbsp;8.1</a>.
     1266            </p>
     1267            <p id="rfc.section.6.4.p.9">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice
     1268               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.
     1269            </p>
     1270            <div class="note" id="rfc.section.6.4.p.10">
     1271               <p><b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
     1272                  familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
     1273                  users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
     1274                  A user agent might suggest in such a case to add "en" to get the best matching behavior.
     1275               </p>
     1276            </div>
     1277         </div>
     1278         <div id="header.content-encoding">
     1279            <div id="rfc.iref.c.7"></div>
     1280            <div id="rfc.iref.h.5"></div>
     1281            <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#header.content-encoding">Content-Encoding</a></h2>
     1282            <p id="rfc.section.6.5.p.1">The "Content-Encoding" header field indicates what content-codings have been applied to the representation, and thus what
     1283               decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding
     1284               is primarily used to allow a representation to be compressed without losing the identity of its underlying media type.
     1285            </p>
     1286            <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
    12161287  <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    12171288</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>. An example of its use is
    1218       </p>
    1219       <div id="rfc.figure.u.27"></div><pre class="text">  Content-Encoding: gzip
     1289            </p>
     1290            <div id="rfc.figure.u.27"></div><pre class="text">  Content-Encoding: gzip
    12201291</pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    1221          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
    1222          directive is present in the message.
    1223       </p>
    1224       <p id="rfc.section.6.5.p.6">If the content-coding of a representation is not "identity", then the representation metadata <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;6.5</a>) that lists the non-identity content-coding(s) used.
    1225       </p>
    1226       <p id="rfc.section.6.5.p.7">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
    1227       </p>
    1228       <p id="rfc.section.6.5.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
    1229       </p>
    1230       <div id="rfc.iref.c.8"></div>
    1231       <div id="rfc.iref.h.6"></div>
    1232       <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>
    1233       <p id="rfc.section.6.6.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
    1234          that this might not be equivalent to all the languages used within the representation.
    1235       </p>
    1236       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
     1292               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
     1293               directive is present in the message.
     1294            </p>
     1295            <p id="rfc.section.6.5.p.6">If the content-coding of a representation is not "identity", then the representation metadata <em class="bcp14">MUST</em> include a Content-Encoding header field (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section&nbsp;6.5</a>) that lists the non-identity content-coding(s) used.
     1296            </p>
     1297            <p id="rfc.section.6.5.p.7">If the content-coding of a representation in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type).
     1298            </p>
     1299            <p id="rfc.section.6.5.p.8">If multiple encodings have been applied to a representation, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     1300            </p>
     1301         </div>
     1302         <div id="header.content-language">
     1303            <div id="rfc.iref.c.8"></div>
     1304            <div id="rfc.iref.h.6"></div>
     1305            <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#header.content-language">Content-Language</a></h2>
     1306            <p id="rfc.section.6.6.p.1">The "Content-Language" header field describes the natural language(s) of the intended audience for the representation. Note
     1307               that this might not be equivalent to all the languages used within the representation.
     1308            </p>
     1309            <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
    12371310  <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    12381311</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    1239          user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    1240          field is
    1241       </p>
    1242       <div id="rfc.figure.u.29"></div><pre class="text">  Content-Language: da
     1312               user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
     1313               field is
     1314            </p>
     1315            <div id="rfc.figure.u.29"></div><pre class="text">  Content-Language: da
    12431316</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
    1244          that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    1245          it is intended.
    1246       </p>
    1247       <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
    1248          simultaneously in the original Maori and English versions, would call for
    1249       </p>
    1250       <div id="rfc.figure.u.30"></div><pre class="text">  Content-Language: mi, en
     1317               that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
     1318               it is intended.
     1319            </p>
     1320            <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
     1321               simultaneously in the original Maori and English versions, would call for
     1322            </p>
     1323            <div id="rfc.figure.u.30"></div><pre class="text">  Content-Language: mi, en
    12511324</pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    1252          linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    1253          intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
    1254       </p>
    1255       <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.
    1256       </p>
    1257       <div id="rfc.iref.c.9"></div>
    1258       <div id="rfc.iref.h.7"></div>
    1259       <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>
    1260       <p id="rfc.section.6.7.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
    1261          message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a 200 response
    1262          would contain the same representation that is enclosed as payload in this message.
    1263       </p>
    1264       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
     1325               linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
     1326               intended to be used by an English-literate audience. In this case, the Content-Language would properly only include "en".
     1327            </p>
     1328            <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.
     1329            </p>
     1330         </div>
     1331         <div id="header.content-location">
     1332            <div id="rfc.iref.c.9"></div>
     1333            <div id="rfc.iref.h.7"></div>
     1334            <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a href="#header.content-location">Content-Location</a></h2>
     1335            <p id="rfc.section.6.7.p.1">The "Content-Location" header field supplies a URI that can be used as a specific identifier for the representation in this
     1336               message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a 200 response
     1337               would contain the same representation that is enclosed as payload in this message.
     1338            </p>
     1339            <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
    12651340                    <a href="#header.content-location" class="smpl">Content-Location-v</a>
    12661341  <a href="#header.content-location" class="smpl">Content-Location-v</a> =
    12671342                    <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    12681343</pre><p id="rfc.section.6.7.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    1269          body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    1270       </p>
    1271       <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    1272          payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    1273          when no Content-Location is provided by the server. For a state-changing method like PUT or POST, it implies that the server's
    1274          response contains the new representation of that resource, thereby distinguishing it from representations that might only
    1275          report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
    1276          need for a subsequent GET request.
    1277       </p>
    1278       <p id="rfc.section.6.7.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
    1279          server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
    1280          request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
    1281          and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location
    1282          indicates that this representation contains a report on the action's status and the same report is available (for future access
    1283          with GET) at the given URI. For example, a purchase transaction made via the POST method might include a receipt document
    1284          as the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
    1285          in the future.
    1286       </p>
    1287       <p id="rfc.section.6.7.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
    1288          representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
    1289          providing the same representation metadata that it received with the original representation. However, such interpretation <em class="bcp14">MUST NOT</em> be used to alter the semantics of the method requested by the client. For example, if a client makes a PUT request on a negotiated
    1290          resource and the origin server accepts that PUT (without redirection), then the new set of values for that resource is expected
    1291          to be consistent with the one representation supplied in that PUT; the Content-Location cannot be used as a form of reverse
    1292          content selection that identifies only one of the negotiated representations to be updated. If the user agent had wanted the
    1293          latter semantics, it would have applied the PUT directly to the Content-Location URI.
    1294       </p>
    1295       <p id="rfc.section.6.7.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
    1296          in other contexts, such as within source links or other metadata.
    1297       </p>
    1298       <p id="rfc.section.6.7.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
    1299          to respond to later requests on that Content-Location URI.
    1300       </p>
    1301       <p id="rfc.section.6.7.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
    1302       <div id="rfc.iref.c.10"></div>
    1303       <div id="rfc.iref.h.8"></div>
    1304       <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>
    1305       <p id="rfc.section.6.8.p.1">The "Content-MD5" header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the payload body that provides an end-to-end message integrity check (MIC) of the payload body (the
    1306          message-body after any transfer-coding is decoded). Note that a MIC is good for detecting accidental modification of the payload
    1307          body in transit, but is not proof against malicious attacks.
    1308       </p>
    1309       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
     1344               body parts in <a href="https://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
     1345            </p>
     1346            <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
     1347               payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
     1348               when no Content-Location is provided by the server. For a state-changing method like PUT or POST, it implies that the server's
     1349               response contains the new representation of that resource, thereby distinguishing it from representations that might only
     1350               report about the action (e.g., "It worked!"). This allows authoring applications to update their local copies without the
     1351               need for a subsequent GET request.
     1352            </p>
     1353            <p id="rfc.section.6.7.p.5">If Content-Location is included in a response message and its value differs from the effective request URI, then the origin
     1354               server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
     1355               request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
     1356               and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location
     1357               indicates that this representation contains a report on the action's status and the same report is available (for future access
     1358               with GET) at the given URI. For example, a purchase transaction made via the POST method might include a receipt document
     1359               as the payload of the 200 response; the Content-Location value provides an identifier for retrieving a copy of that same receipt
     1360               in the future.
     1361            </p>
     1362            <p id="rfc.section.6.7.p.6">If Content-Location is included in a request message, then it <em class="bcp14">MAY</em> be interpreted by the origin server as an indication of where the user agent originally obtained the content of the enclosed
     1363               representation (prior to any subsequent modification of the content by that user agent). In other words, the user agent is
     1364               providing the same representation metadata that it received with the original representation. However, such interpretation <em class="bcp14">MUST NOT</em> be used to alter the semantics of the method requested by the client. For example, if a client makes a PUT request on a negotiated
     1365               resource and the origin server accepts that PUT (without redirection), then the new set of values for that resource is expected
     1366               to be consistent with the one representation supplied in that PUT; the Content-Location cannot be used as a form of reverse
     1367               content selection that identifies only one of the negotiated representations to be updated. If the user agent had wanted the
     1368               latter semantics, it would have applied the PUT directly to the Content-Location URI.
     1369            </p>
     1370            <p id="rfc.section.6.7.p.7">A Content-Location field received in a request message is transitory information that <em class="bcp14">SHOULD NOT</em> be saved with other representation metadata for use in later responses. The Content-Location's value might be saved for use
     1371               in other contexts, such as within source links or other metadata.
     1372            </p>
     1373            <p id="rfc.section.6.7.p.8">A cache cannot assume that a representation with a Content-Location different from the URI used to retrieve it can be used
     1374               to respond to later requests on that Content-Location URI.
     1375            </p>
     1376            <p id="rfc.section.6.7.p.9">If the Content-Location value is a partial URI, the partial URI is interpreted relative to the effective request URI.</p>
     1377         </div>
     1378         <div id="header.content-md5">
     1379            <div id="rfc.iref.c.10"></div>
     1380            <div id="rfc.iref.h.8"></div>
     1381            <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a>&nbsp;<a href="#header.content-md5">Content-MD5</a></h2>
     1382            <p id="rfc.section.6.8.p.1">The "Content-MD5" header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the payload body that provides an end-to-end message integrity check (MIC) of the payload body (the
     1383               message-body after any transfer-coding is decoded). Note that a MIC is good for detecting accidental modification of the payload
     1384               body in transit, but is not proof against malicious attacks.
     1385            </p>
     1386            <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
    13101387  <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = &lt;base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>&gt;
    13111388</pre><p id="rfc.section.6.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the payload body. Only origin servers or user
    1312          agents <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 <em class="bcp14">MAY</em> check that the digest value in this header field matches a corresponding digest calculated on payload body as received.
    1313       </p>
    1314       <p id="rfc.section.6.8.p.4">The MD5 digest is computed based on the content of the payload body, including any content-coding, but not including any transfer-coding
    1315          applied to the message-body because such transfer-codings might be applied or removed anywhere along the request/response
    1316          chain. If the message is received with a transfer-coding, that encoding <em class="bcp14">MUST</em> be decoded prior to checking the Content-MD5 value against the received payload.
    1317       </p>
    1318       <p id="rfc.section.6.8.p.5">HTTP extends RFC 1864 to permit the digest to be computed for MIME composite media-types (e.g., multipart/* and message/rfc822),
    1319          but this does not change how the digest is computed as defined in the preceding paragraph.
    1320       </p>
    1321       <p id="rfc.section.6.8.p.6">There are several consequences of this. The payload for composite types <em class="bcp14">MAY</em> contain many body-parts, each with its own MIME and HTTP header fields (including Content-MD5, Content-Transfer-Encoding,
    1322          and Content-Encoding header fields). If a body-part has a Content-Transfer-Encoding or Content-Encoding header field, it is
    1323          assumed that the content of the body-part has had the encoding applied, and the body-part is included in the Content-MD5 digest
    1324          as is -- i.e., after the application. The Transfer-Encoding header field is not allowed within body-parts.
    1325       </p>
    1326       <p id="rfc.section.6.8.p.7">Conversion of all line breaks to CRLF <em class="bcp14">MUST NOT</em> be done before computing or checking the digest: the line break convention used in the text actually transmitted <em class="bcp14">MUST</em> be left unaltered when computing the digest.
    1327       </p>
    1328       <div class="note" id="rfc.section.6.8.p.8">
    1329          <p> <b>Note:</b> While the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several
    1330             ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One
    1331             is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another
    1332             is that HTTP more frequently uses binary content types than MIME, so it is worth noting that, in such cases, the byte order
    1333             used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types
    1334             with any of several line break conventions and not just the canonical form using CRLF.
    1335          </p>
    1336       </div>
    1337       <div id="rfc.iref.c.11"></div>
    1338       <div id="rfc.iref.h.9"></div>
    1339       <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>
    1340       <p id="rfc.section.6.9.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
    1341          the media type is that which would have been sent had the request been a GET.
    1342       </p>
    1343       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
     1389               agents <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 <em class="bcp14">MAY</em> check that the digest value in this header field matches a corresponding digest calculated on payload body as received.
     1390            </p>
     1391            <p id="rfc.section.6.8.p.4">The MD5 digest is computed based on the content of the payload body, including any content-coding, but not including any transfer-coding
     1392               applied to the message-body because such transfer-codings might be applied or removed anywhere along the request/response
     1393               chain. If the message is received with a transfer-coding, that encoding <em class="bcp14">MUST</em> be decoded prior to checking the Content-MD5 value against the received payload.
     1394            </p>
     1395            <p id="rfc.section.6.8.p.5">HTTP extends RFC 1864 to permit the digest to be computed for MIME composite media-types (e.g., multipart/* and message/rfc822),
     1396               but this does not change how the digest is computed as defined in the preceding paragraph.
     1397            </p>
     1398            <p id="rfc.section.6.8.p.6">There are several consequences of this. The payload for composite types <em class="bcp14">MAY</em> contain many body-parts, each with its own MIME and HTTP header fields (including Content-MD5, Content-Transfer-Encoding,
     1399               and Content-Encoding header fields). If a body-part has a Content-Transfer-Encoding or Content-Encoding header field, it is
     1400               assumed that the content of the body-part has had the encoding applied, and the body-part is included in the Content-MD5 digest
     1401               as is -- i.e., after the application. The Transfer-Encoding header field is not allowed within body-parts.
     1402            </p>
     1403            <p id="rfc.section.6.8.p.7">Conversion of all line breaks to CRLF <em class="bcp14">MUST NOT</em> be done before computing or checking the digest: the line break convention used in the text actually transmitted <em class="bcp14">MUST</em> be left unaltered when computing the digest.
     1404            </p>
     1405            <div class="note" id="rfc.section.6.8.p.8">
     1406               <p><b>Note:</b> While the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several
     1407                  ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One
     1408                  is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another
     1409                  is that HTTP more frequently uses binary content types than MIME, so it is worth noting that, in such cases, the byte order
     1410                  used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types
     1411                  with any of several line break conventions and not just the canonical form using CRLF.
     1412               </p>
     1413            </div>
     1414         </div>
     1415         <div id="header.content-type">
     1416            <div id="rfc.iref.c.11"></div>
     1417            <div id="rfc.iref.h.9"></div>
     1418            <h2 id="rfc.section.6.9"><a href="#rfc.section.6.9">6.9</a>&nbsp;<a href="#header.content-type">Content-Type</a></h2>
     1419            <p id="rfc.section.6.9.p.1">The "Content-Type" header field indicates the media type of the representation. In the case of responses to the HEAD method,
     1420               the media type is that which would have been sent had the request been a GET.
     1421            </p>
     1422            <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
    13441423  <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a>
    13451424</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;2.3</a>. An example of the field is
    1346       </p>
    1347       <div id="rfc.figure.u.34"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     1425            </p>
     1426            <div id="rfc.figure.u.34"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    13481427</pre><p id="rfc.section.6.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;4.2</a>.
    1349       </p>
    1350       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1351       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1352       <p id="rfc.section.7.1.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    1353       </p>
    1354       <div id="rfc.table.1">
    1355          <div id="iana.header.registration.table"></div>
    1356          <table class="tt full left" cellpadding="3" cellspacing="0">
    1357             <thead>
    1358                <tr>
    1359                   <th>Header Field Name</th>
    1360                   <th>Protocol</th>
    1361                   <th>Status</th>
    1362                   <th>Reference</th>
    1363                </tr>
    1364             </thead>
    1365             <tbody>
    1366                <tr>
    1367                   <td class="left">Accept</td>
    1368                   <td class="left">http</td>
    1369                   <td class="left">standard</td>
    1370                   <td class="left"> <a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.1</a>
    1371                   </td>
    1372                </tr>
    1373                <tr>
    1374                   <td class="left">Accept-Charset</td>
    1375                   <td class="left">http</td>
    1376                   <td class="left">standard</td>
    1377                   <td class="left"> <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.2</a>
    1378                   </td>
    1379                </tr>
    1380                <tr>
    1381                   <td class="left">Accept-Encoding</td>
    1382                   <td class="left">http</td>
    1383                   <td class="left">standard</td>
    1384                   <td class="left"> <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3</a>
    1385                   </td>
    1386                </tr>
    1387                <tr>
    1388                   <td class="left">Accept-Language</td>
    1389                   <td class="left">http</td>
    1390                   <td class="left">standard</td>
    1391                   <td class="left"> <a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.4</a>
    1392                   </td>
    1393                </tr>
    1394                <tr>
    1395                   <td class="left">Content-Encoding</td>
    1396                   <td class="left">http</td>
    1397                   <td class="left">standard</td>
    1398                   <td class="left"> <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;6.5</a>
    1399                   </td>
    1400                </tr>
    1401                <tr>
    1402                   <td class="left">Content-Language</td>
    1403                   <td class="left">http</td>
    1404                   <td class="left">standard</td>
    1405                   <td class="left"> <a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;6.6</a>
    1406                   </td>
    1407                </tr>
    1408                <tr>
    1409                   <td class="left">Content-Location</td>
    1410                   <td class="left">http</td>
    1411                   <td class="left">standard</td>
    1412                   <td class="left"> <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;6.7</a>
    1413                   </td>
    1414                </tr>
    1415                <tr>
    1416                   <td class="left">Content-MD5</td>
    1417                   <td class="left">http</td>
    1418                   <td class="left">standard</td>
    1419                   <td class="left"> <a href="#header.content-md5" id="rfc.xref.header.content-md5.2" title="Content-MD5">Section&nbsp;6.8</a>
    1420                   </td>
    1421                </tr>
    1422                <tr>
    1423                   <td class="left">Content-Type</td>
    1424                   <td class="left">http</td>
    1425                   <td class="left">standard</td>
    1426                   <td class="left"> <a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;6.9</a>
    1427                   </td>
    1428                </tr>
    1429                <tr>
    1430                   <td class="left">MIME-Version</td>
    1431                   <td class="left">http</td>
    1432                   <td class="left">standard</td>
    1433                   <td class="left"> <a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
    1434                   </td>
    1435                </tr>
    1436             </tbody>
    1437          </table>
     1428            </p>
     1429         </div>
    14381430      </div>
    1439       <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1440       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="content.coding.registration" href="#content.coding.registration">Content Coding Registry</a></h2>
    1441       <p id="rfc.section.7.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a> of this document.
    1442       </p>
    1443       <p id="rfc.section.7.2.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
    1444       </p>
    1445       <div id="rfc.table.2">
    1446          <div id="iana.content.coding.registration.table"></div>
    1447          <table class="tt full left" cellpadding="3" cellspacing="0">
    1448             <thead>
    1449                <tr>
    1450                   <th>Name</th>
    1451                   <th>Description</th>
    1452                   <th>Reference</th>
    1453                </tr>
    1454             </thead>
    1455             <tbody>
    1456                <tr>
    1457                   <td class="left">compress</td>
    1458                   <td class="left">UNIX "compress" program method</td>
    1459                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1460                   </td>
    1461                </tr>
    1462                <tr>
    1463                   <td class="left">deflate</td>
    1464                   <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    1465                   </td>
    1466                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1467                   </td>
    1468                </tr>
    1469                <tr>
    1470                   <td class="left">gzip</td>
    1471                   <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    1472                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    1473                   </td>
    1474                </tr>
    1475                <tr>
    1476                   <td class="left">identity</td>
    1477                   <td class="left">No transformation</td>
    1478                   <td class="left"> <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>
    1479                   </td>
    1480                </tr>
    1481             </tbody>
    1482          </table>
     1431      <div id="IANA.considerations">
     1432         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1433         <div id="header.field.registration">
     1434            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     1435            <p id="rfc.section.7.1.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     1436            </p>
     1437            <div id="rfc.table.1">
     1438               <div id="iana.header.registration.table"></div>
     1439               <table class="tt full left" cellpadding="3" cellspacing="0">
     1440                  <thead>
     1441                     <tr>
     1442                        <th>Header Field Name</th>
     1443                        <th>Protocol</th>
     1444                        <th>Status</th>
     1445                        <th>Reference</th>
     1446                     </tr>
     1447                  </thead>
     1448                  <tbody>
     1449                     <tr>
     1450                        <td class="left">Accept</td>
     1451                        <td class="left">http</td>
     1452                        <td class="left">standard</td>
     1453                        <td class="left"><a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.1</a>
     1454                        </td>
     1455                     </tr>
     1456                     <tr>
     1457                        <td class="left">Accept-Charset</td>
     1458                        <td class="left">http</td>
     1459                        <td class="left">standard</td>
     1460                        <td class="left"><a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;6.2</a>
     1461                        </td>
     1462                     </tr>
     1463                     <tr>
     1464                        <td class="left">Accept-Encoding</td>
     1465                        <td class="left">http</td>
     1466                        <td class="left">standard</td>
     1467                        <td class="left"><a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3</a>
     1468                        </td>
     1469                     </tr>
     1470                     <tr>
     1471                        <td class="left">Accept-Language</td>
     1472                        <td class="left">http</td>
     1473                        <td class="left">standard</td>
     1474                        <td class="left"><a href="#header.accept-language" id="rfc.xref.header.accept-language.2" title="Accept-Language">Section&nbsp;6.4</a>
     1475                        </td>
     1476                     </tr>
     1477                     <tr>
     1478                        <td class="left">Content-Encoding</td>
     1479                        <td class="left">http</td>
     1480                        <td class="left">standard</td>
     1481                        <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.4" title="Content-Encoding">Section&nbsp;6.5</a>
     1482                        </td>
     1483                     </tr>
     1484                     <tr>
     1485                        <td class="left">Content-Language</td>
     1486                        <td class="left">http</td>
     1487                        <td class="left">standard</td>
     1488                        <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.2" title="Content-Language">Section&nbsp;6.6</a>
     1489                        </td>
     1490                     </tr>
     1491                     <tr>
     1492                        <td class="left">Content-Location</td>
     1493                        <td class="left">http</td>
     1494                        <td class="left">standard</td>
     1495                        <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;6.7</a>
     1496                        </td>
     1497                     </tr>
     1498                     <tr>
     1499                        <td class="left">Content-MD5</td>
     1500                        <td class="left">http</td>
     1501                        <td class="left">standard</td>
     1502                        <td class="left"><a href="#header.content-md5" id="rfc.xref.header.content-md5.2" title="Content-MD5">Section&nbsp;6.8</a>
     1503                        </td>
     1504                     </tr>
     1505                     <tr>
     1506                        <td class="left">Content-Type</td>
     1507                        <td class="left">http</td>
     1508                        <td class="left">standard</td>
     1509                        <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;6.9</a>
     1510                        </td>
     1511                     </tr>
     1512                     <tr>
     1513                        <td class="left">MIME-Version</td>
     1514                        <td class="left">http</td>
     1515                        <td class="left">standard</td>
     1516                        <td class="left"><a href="#mime-version" id="rfc.xref.mime-version.1" title="MIME-Version">Appendix&nbsp;A.1</a>
     1517                        </td>
     1518                     </tr>
     1519                  </tbody>
     1520               </table>
     1521            </div>
     1522            <p id="rfc.section.7.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1523         </div>
     1524         <div id="content.coding.registration">
     1525            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#content.coding.registration">Content Coding Registry</a></h2>
     1526            <p id="rfc.section.7.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;2.2.1</a> of this document.
     1527            </p>
     1528            <p id="rfc.section.7.2.p.2">The HTTP Content Codings Registry located at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt; shall be updated with the registration below:
     1529            </p>
     1530            <div id="rfc.table.2">
     1531               <div id="iana.content.coding.registration.table"></div>
     1532               <table class="tt full left" cellpadding="3" cellspacing="0">
     1533                  <thead>
     1534                     <tr>
     1535                        <th>Name</th>
     1536                        <th>Description</th>
     1537                        <th>Reference</th>
     1538                     </tr>
     1539                  </thead>
     1540                  <tbody>
     1541                     <tr>
     1542                        <td class="left">compress</td>
     1543                        <td class="left">UNIX "compress" program method</td>
     1544                        <td class="left"><a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 6.2.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1545                        </td>
     1546                     </tr>
     1547                     <tr>
     1548                        <td class="left">deflate</td>
     1549                        <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
     1550                        </td>
     1551                        <td class="left"><a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1552                        </td>
     1553                     </tr>
     1554                     <tr>
     1555                        <td class="left">gzip</td>
     1556                        <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
     1557                        <td class="left"><a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 6.2.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     1558                        </td>
     1559                     </tr>
     1560                     <tr>
     1561                        <td class="left">identity</td>
     1562                        <td class="left">No transformation</td>
     1563                        <td class="left"><a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>
     1564                        </td>
     1565                     </tr>
     1566                  </tbody>
     1567               </table>
     1568            </div>
     1569         </div>
    14831570      </div>
    1484       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1485       <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
    1486          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    1487          make some suggestions for reducing security risks.
    1488       </p>
    1489       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="privacy.issues.connected.to.accept.header.fields" href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
    1490       <p id="rfc.section.8.1.p.1">Accept request-headers fields can reveal information about the user to all servers which are accessed. The Accept-Language
    1491          header field in particular can reveal information the user would consider to be of a private nature, because the understanding
    1492          of particular languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer
    1493          the option to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged
    1494          to let the configuration process include a message which makes the user aware of the loss of privacy involved.
    1495       </p>
    1496       <p id="rfc.section.8.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
    1497          by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
    1498          looking for any Vary response-header fields generated by the server, that such sending could improve the quality of service.
    1499       </p>
    1500       <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
    1501          used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
    1502          to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
    1503          of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
    1504          also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
    1505          be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
    1506          filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
    1507       </p>
    1508       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     1571      <div id="security.considerations">
     1572         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1573         <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
     1574            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
     1575            make some suggestions for reducing security risks.
     1576         </p>
     1577         <div id="privacy.issues.connected.to.accept.header.fields">
     1578            <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#privacy.issues.connected.to.accept.header.fields">Privacy Issues Connected to Accept Header Fields</a></h2>
     1579            <p id="rfc.section.8.1.p.1">Accept request-headers fields can reveal information about the user to all servers which are accessed. The Accept-Language
     1580               header field in particular can reveal information the user would consider to be of a private nature, because the understanding
     1581               of particular languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer
     1582               the option to configure the contents of an Accept-Language header field to be sent in every request are strongly encouraged
     1583               to let the configuration process include a message which makes the user aware of the loss of privacy involved.
     1584            </p>
     1585            <p id="rfc.section.8.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
     1586               by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
     1587               looking for any Vary response-header fields generated by the server, that such sending could improve the quality of service.
     1588            </p>
     1589            <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
     1590               used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers
     1591               to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions
     1592               of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
     1593               also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
     1594               be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
     1595               filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
     1596            </p>
     1597         </div>
     1598      </div>
     1599      <div id="ack">
     1600         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     1601      </div>
    15091602      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
    15101603      </h1>
    15111604      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
    15121605      </h2>
    1513       <table>                               
     1606      <table>
    15141607         <tr>
    15151608            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    15181611         <tr>
    15191612            <td class="reference"><b id="Part1">[Part1]</b></td>
    1520             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-12">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-12 (work in progress), October&nbsp;2010.
     1613            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-12">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-12 (work in progress), October&nbsp;2010.
    15211614            </td>
    15221615         </tr>
    15231616         <tr>
    15241617            <td class="reference"><b id="Part2">[Part2]</b></td>
    1525             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-12 (work in progress), October&nbsp;2010.
     1618            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-12">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-12 (work in progress), October&nbsp;2010.
    15261619            </td>
    15271620         </tr>
    15281621         <tr>
    15291622            <td class="reference"><b id="Part4">[Part4]</b></td>
    1530             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-12">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-12 (work in progress), October&nbsp;2010.
     1623            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-12">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-12 (work in progress), October&nbsp;2010.
    15311624            </td>
    15321625         </tr>
    15331626         <tr>
    15341627            <td class="reference"><b id="Part5">[Part5]</b></td>
    1535             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-12">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-12 (work in progress), October&nbsp;2010.
     1628            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-12">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-12 (work in progress), October&nbsp;2010.
    15361629            </td>
    15371630         </tr>
    15381631         <tr>
    15391632            <td class="reference"><b id="Part6">[Part6]</b></td>
    1540             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-12">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-12 (work in progress), October&nbsp;2010.
     1633            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-12">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-12 (work in progress), October&nbsp;2010.
    15411634            </td>
    15421635         </tr>
    15431636         <tr>
    15441637            <td class="reference"><b id="RFC1864">[RFC1864]</b></td>
    1545             <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.
     1638            <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="https://tools.ietf.org/html/rfc1864">The Content-MD5 Header Field</a>”, RFC&nbsp;1864, October&nbsp;1995.
    15461639            </td>
    15471640         </tr>
    15481641         <tr>
    15491642            <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
    1550             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
     1643            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</a> and J-L. Gailly, “<a href="https://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.<br>RFC 1950 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
    15511644               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.1"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    15521645            </td>
     
    15541647         <tr>
    15551648            <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
    1556             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
     1649            <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="https://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.<br>RFC 1951 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
    15571650               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.2"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    15581651            </td>
     
    15601653         <tr>
    15611654            <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
    1562             <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
     1655            <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="https://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.<br>RFC 1952 is an Informational RFC, thus it might be less stable than this specification. On the other hand, this downward reference
    15631656               was present since the publication of RFC 2068 in 1997 (<a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>), therefore it is unlikely to cause problems in practice. See also <a href="#BCP97" id="rfc.xref.BCP97.3"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    15641657            </td>
     
    15661659         <tr>
    15671660            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    1568             <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.
     1661            <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="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
    15691662            </td>
    15701663         </tr>
    15711664         <tr>
    15721665            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    1573             <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.
     1666            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    15741667            </td>
    15751668         </tr>
    15761669         <tr>
    15771670            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1578             <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.
     1671            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://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.
    15791672            </td>
    15801673         </tr>
    15811674         <tr>
    15821675            <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
    1583             <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
     1676            <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="https://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
    15841677            </td>
    15851678         </tr>
    15861679         <tr>
    15871680            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1588             <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1681            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    15891682            </td>
    15901683         </tr>
    15911684         <tr>
    15921685            <td class="reference"><b id="RFC5646">[RFC5646]</b></td>
    1593             <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
     1686            <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="https://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
    15941687            </td>
    15951688         </tr>
     
    15971690      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
    15981691      </h2>
    1599       <table>                             
     1692      <table>
    16001693         <tr>
    16011694            <td class="reference"><b id="BCP97">[BCP97]</b></td>
    1602             <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="http://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007.
     1695            <td class="top"><a href="mailto:klensin+ietf@jck.com">Klensin, J.</a> and <a href="mailto:hartmans-ietf@mit.edu" title="MIT">S. Hartman</a>, “<a href="https://tools.ietf.org/html/rfc4897">Handling Normative References to Standards-Track Documents</a>”, BCP&nbsp;97, RFC&nbsp;4897, June&nbsp;2007.
    16031696            </td>
    16041697         </tr>
    16051698         <tr>
    16061699            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    1607             <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.
     1700            <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="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    16081701            </td>
    16091702         </tr>
    16101703         <tr>
    16111704            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
    1612             <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.
     1705            <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="https://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
    16131706            </td>
    16141707         </tr>
    16151708         <tr>
    16161709            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    1617             <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.
     1710            <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="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    16181711            </td>
    16191712         </tr>
    16201713         <tr>
    16211714            <td class="reference"><b id="RFC2076">[RFC2076]</b></td>
    1622             <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.
     1715            <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University/KTH">Palme, J.</a>, “<a href="https://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC&nbsp;2076, February&nbsp;1997.
    16231716            </td>
    16241717         </tr>
    16251718         <tr>
    16261719            <td class="reference"><b id="RFC2277">[RFC2277]</b></td>
    1627             <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.
     1720            <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="https://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP&nbsp;18, RFC&nbsp;2277, January&nbsp;1998.
    16281721            </td>
    16291722         </tr>
    16301723         <tr>
    16311724            <td class="reference"><b id="RFC2295">[RFC2295]</b></td>
    1632             <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="http://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
     1725            <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="https://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
    16331726            </td>
    16341727         </tr>
    16351728         <tr>
    16361729            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
    1637             <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.
     1730            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
    16381731            </td>
    16391732         </tr>
    16401733         <tr>
    16411734            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
    1642             <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.
     1735            <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="https://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
    16431736            </td>
    16441737         </tr>
    16451738         <tr>
    16461739            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1647             <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.
     1740            <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="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    16481741            </td>
    16491742         </tr>
    16501743         <tr>
    16511744            <td class="reference"><b id="RFC3629">[RFC3629]</b></td>
    1652             <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD&nbsp;63, RFC&nbsp;3629, November&nbsp;2003.
     1745            <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="https://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, STD&nbsp;63, RFC&nbsp;3629, November&nbsp;2003.
    16531746            </td>
    16541747         </tr>
    16551748         <tr>
    16561749            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    1657             <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.
     1750            <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="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    16581751            </td>
    16591752         </tr>
    16601753         <tr>
    16611754            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    1662             <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.
     1755            <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="https://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    16631756            </td>
    16641757         </tr>
    16651758         <tr>
    16661759            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    1667             <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     1760            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    16681761            </td>
    16691762         </tr>
    16701763         <tr>
    16711764            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    1672             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     1765            <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    16731766            </td>
    16741767         </tr>
    16751768      </table>
    1676       <div class="avoidbreak">
    1677          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1678          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1679                (editor)
    1680                <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>
    1681          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">Alcatel-Lucent Bell Labs</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:jg@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
    1682          <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>
    1683          <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>
    1684          <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>
    1685          <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>
    1686          <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>
    1687          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1688                (editor)
    1689                <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>
    1690          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1691                (editor)
    1692                <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>
    1693       </div>
    1694       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
    1695       <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message-body to be transmitted in an open variety of representations and with extensible mechanisms. However,
    1696          RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
    1697          carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
    1698          to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
    1699       </p>
    1700       <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments
    1701          to HTTP also need to be aware of the differences because some conversions might be required.
    1702       </p>
    1703       <div id="rfc.iref.m.1"></div>
    1704       <div id="rfc.iref.h.10"></div>
    1705       <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>
    1706       <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
    1707          message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as
    1708          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
    1709          environments.
    1710       </p>
    1711       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
     1769      <div id="differences.between.http.and.mime">
     1770         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
     1771         <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message-body to be transmitted in an open variety of representations and with extensible mechanisms. However,
     1772            RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
     1773            carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
     1774            to make date comparisons easier, and to acknowledge the practice of some early HTTP servers and clients.
     1775         </p>
     1776         <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from MIME. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments
     1777            to HTTP also need to be aware of the differences because some conversions might be required.
     1778         </p>
     1779         <div id="mime-version">
     1780            <div id="rfc.iref.m.1"></div>
     1781            <div id="rfc.iref.h.10"></div>
     1782            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#mime-version">MIME-Version</a></h2>
     1783            <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
     1784               message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as
     1785               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
     1786               environments.
     1787            </p>
     1788            <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
    17121789  <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
    17131790</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
    1714          document and not the MIME specification.
    1715       </p>
    1716       <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>
    1717       <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    1718          break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
    1719          over HTTP.
    1720       </p>
    1721       <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
    1722          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
    1723          CR and LF, as is the case for some multi-byte character sets.
    1724       </p>
    1725       <p id="rfc.section.A.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in
    1726          canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP.
    1727       </p>
    1728       <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
    1729       <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
    1730       </p>
    1731       <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
    1732       <p id="rfc.section.A.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on
    1733          the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some
    1734          experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;"
    1735          to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
    1736       </p>
    1737       <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    1738       <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
    1739       </p>
    1740       <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
    1741          format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
    1742          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
    1743          the destination protocol.
    1744       </p>
    1745       <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
    1746       <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.24"><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.
    1747       </p>
    1748       <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
    1749       <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
    1750          fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
    1751          and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
    1752       </p>
    1753       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    1754       <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
    1755          applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
    1756          with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
    1757          experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
    1758       </p>
    1759       <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
    1760       </p>
    1761       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    1762       <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>)
    1763       </p>
    1764       <p id="rfc.section.C.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
    1765          servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
    1766          relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
    1767       </p>
    1768       <p id="rfc.section.C.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
    1769       </p>
    1770       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1771       <div id="rfc.figure.u.36"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
     1791               document and not the MIME specification.
     1792            </p>
     1793         </div>
     1794         <div id="conversion.to.canonical.form">
     1795            <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
     1796            <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body-part be converted to canonical form prior to being transferred, as described in <a href="https://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
     1797               break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted
     1798               over HTTP.
     1799            </p>
     1800            <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;2.3.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of
     1801               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
     1802               CR and LF, as is the case for some multi-byte character sets.
     1803            </p>
     1804            <p id="rfc.section.A.2.p.3">Conversion will break any cryptographic checksums applied to the original content unless the original content is already in
     1805               canonical form. Therefore, the canonical form is recommended for any content that uses such checksums in HTTP.
     1806            </p>
     1807         </div>
     1808         <div id="conversion.of.date.formats">
     1809            <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
     1810            <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.
     1811            </p>
     1812         </div>
     1813         <div id="introduction.of.content-encoding">
     1814            <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2>
     1815            <p id="rfc.section.A.4.p.1">MIME does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier on
     1816               the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the representation before forwarding the message. (Some
     1817               experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=&lt;content-coding&gt;"
     1818               to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
     1819            </p>
     1820         </div>
     1821         <div id="no.content-transfer-encoding">
     1822            <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
     1823            <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
     1824            </p>
     1825            <p id="rfc.section.A.5.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
     1826               format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol
     1827               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
     1828               the destination protocol.
     1829            </p>
     1830         </div>
     1831         <div id="introduction.of.transfer-encoding">
     1832            <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
     1833            <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 9.7</a> of <a href="#Part1" id="rfc.xref.Part1.24"><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.
     1834            </p>
     1835         </div>
     1836         <div id="mhtml.line.length">
     1837            <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
     1838            <p id="rfc.section.A.7.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not
     1839               fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations
     1840               and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section&nbsp;2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein.
     1841            </p>
     1842         </div>
     1843      </div>
     1844      <div id="additional.features">
     1845         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#additional.features">Additional Features</a></h1>
     1846         <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
     1847            applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
     1848            with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
     1849            experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
     1850         </p>
     1851         <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
     1852         </p>
     1853      </div>
     1854      <div id="changes.from.rfc.2616">
     1855         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     1856         <p id="rfc.section.C.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section&nbsp;2.1</a>)
     1857         </p>
     1858         <p id="rfc.section.C.p.2">Remove base URI setting semantics for Content-Location due to poor implementation support, which was caused by too many broken
     1859            servers emitting bogus Content-Location header fields, and also the potentially undesirable effect of potentially breaking
     1860            relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
     1861         </p>
     1862         <p id="rfc.section.C.p.3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
     1863         </p>
     1864      </div>
     1865      <div id="collected.abnf">
     1866         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1867         <div id="rfc.figure.u.36"></div><pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
    17721868<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v
    1773 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
    1774  qvalue ] *( OWS "," [ OWS ( charset / "*" ) [ OWS ";" OWS "q="
    1775  qvalue ] ] )
     1869<a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( ( charset / "*" ) [ OWS ";" OWS
     1870 "q=" qvalue ] ) *( OWS "," [ OWS ( ( charset / "*" ) [ OWS ";" OWS
     1871 "q=" qvalue ] ) ] )
    17761872<a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding:" OWS Accept-Encoding-v
    17771873<a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = [ ( "," / ( codings [ OWS ";" OWS "q=" qvalue ] )
    1778  ) *( OWS "," [ OWS codings [ OWS ";" OWS "q=" qvalue ] ] ) ]
     1874 ) *( OWS "," [ OWS ( codings [ OWS ";" OWS "q=" qvalue ] ) ] ) ]
    17791875<a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language:" OWS Accept-Language-v
    1780 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = *( "," OWS ) language-range [ OWS ";" OWS "q="
    1781  qvalue ] *( OWS "," [ OWS language-range [ OWS ";" OWS "q=" qvalue ]
    1782  ] )
     1876<a href="#header.accept-language" class="smpl">Accept-Language-v</a> = *( "," OWS ) ( language-range [ OWS ";" OWS "q="
     1877 qvalue ] ) *( OWS "," [ OWS ( language-range [ OWS ";" OWS "q="
     1878 qvalue ] ) ] )
    17831879<a href="#header.accept" class="smpl">Accept-v</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
    1784  OWS media-range [ accept-params ] ] ) ]
     1880 OWS ( media-range [ accept-params ] ) ] ) ]
    17851881
    17861882<a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding:" OWS Content-Encoding-v
     
    18371933
    18381934<a href="#core.rules" class="smpl">word</a> = &lt;word, defined in [Part1], Section 1.2.2&gt;
    1839 </pre> <div id="rfc.figure.u.37"></div>
    1840       <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
     1935</pre><div id="rfc.figure.u.37"></div>
     1936         <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
    18411937; Accept-Charset defined but not used
    18421938; Accept-Encoding defined but not used
     
    18521948; Last-Modified defined but not used
    18531949; MIME-Version defined but not used
    1854 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1855       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
    1856       </h2>
    1857       <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1858       </p>
    1859       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    1860       </h2>
    1861       <p id="rfc.section.E.2.p.1">Closed issues: </p>
    1862       <ul>
    1863          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
    1864          </li>
    1865          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/14">http://tools.ietf.org/wg/httpbis/trac/ticket/14</a>&gt;: "Clarification regarding quoting of charset values" (&lt;<a href="http://purl.org/NET/http-errata#charactersets">http://purl.org/NET/http-errata#charactersets</a>&gt;)
    1866          </li>
    1867          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/16">http://tools.ietf.org/wg/httpbis/trac/ticket/16</a>&gt;: "Remove 'identity' token references" (&lt;<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>&gt;)
    1868          </li>
    1869          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/25">http://tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
    1870          </li>
    1871          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    1872          </li>
    1873          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/46">http://tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
    1874          </li>
    1875          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
    1876          </li>
    1877          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/65">http://tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    1878          </li>
    1879          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/66">http://tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
    1880          </li>
    1881          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative"
    1882          </li>
    1883          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    1884          </li>
    1885       </ul>
    1886       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
    1887       </h2>
    1888       <p id="rfc.section.E.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1889       </p>
    1890       <ul>
    1891          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1892       </ul>
    1893       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
    1894       <p id="rfc.section.E.4.p.1">Closed issues: </p>
    1895       <ul>
    1896          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    1897          </li>
    1898          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
    1899          </li>
    1900          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
    1901          </li>
    1902       </ul>
    1903       <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    1904       </p>
    1905       <ul>
    1906          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    1907       </ul>
    1908       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
    1909       <p id="rfc.section.E.5.p.1">Closed issues: </p>
    1910       <ul>
    1911          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    1912          </li>
    1913          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/113">http://tools.ietf.org/wg/httpbis/trac/ticket/113</a>&gt;: "language tag matching (Accept-Language) vs RFC4647"
    1914          </li>
    1915          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
    1916          </li>
    1917       </ul>
    1918       <p id="rfc.section.E.5.p.2">Other changes: </p>
    1919       <ul>
    1920          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
    1921          </li>
    1922       </ul>
    1923       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
    1924       <p id="rfc.section.E.6.p.1">Closed issues: </p>
    1925       <ul>
    1926          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
    1927          </li>
    1928       </ul>
    1929       <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1930       </p>
    1931       <ul>
    1932          <li>Use "/" instead of "|" for alternatives.</li>
    1933          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1934          <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    1935       </ul>
    1936       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
    1937       <p id="rfc.section.E.7.p.1">Closed issues: </p>
    1938       <ul>
    1939          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
    1940          </li>
    1941       </ul>
    1942       <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1943       </p>
    1944       <ul>
    1945          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1946       </ul>
    1947       <p id="rfc.section.E.7.p.3">Other changes: </p>
    1948       <ul>
    1949          <li>Move definition of quality values into Part 1.</li>
    1950       </ul>
    1951       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
    1952       <p id="rfc.section.E.8.p.1">Closed issues: </p>
    1953       <ul>
    1954          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
    1955          </li>
    1956          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    1957          </li>
    1958       </ul>
    1959       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
    1960       <p id="rfc.section.E.9.p.1">Closed issues: </p>
    1961       <ul>
    1962          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
    1963          </li>
    1964          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>&gt;: "Clarify rules for determining what entities a response carries"
    1965          </li>
    1966          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/154">http://tools.ietf.org/wg/httpbis/trac/ticket/154</a>&gt;: "Content-Location base-setting problems"
    1967          </li>
    1968          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    1969          </li>
    1970          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
    1971          </li>
    1972          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>&gt;: "move definitions of gzip/deflate/compress to part 1"
    1973          </li>
    1974       </ul>
    1975       <p id="rfc.section.E.9.p.2">Partly resolved issues: </p>
    1976       <ul>
    1977          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
    1978          </li>
    1979          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/149">http://tools.ietf.org/wg/httpbis/trac/ticket/149</a>&gt;: "update IANA requirements wrt Content-Coding values" (add the IANA Considerations subsection)
    1980          </li>
    1981       </ul>
    1982       <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
    1983       <p id="rfc.section.E.10.p.1">Closed issues: </p>
    1984       <ul>
    1985          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
    1986          </li>
    1987          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/181">http://tools.ietf.org/wg/httpbis/trac/ticket/181</a>&gt;: "Accept-Language: which RFC4647 filtering?"
    1988          </li>
    1989       </ul>
    1990       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
    1991       <p id="rfc.section.E.11.p.1">Closed issues: </p>
    1992       <ul>
    1993          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
    1994          </li>
    1995          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/143">http://tools.ietf.org/wg/httpbis/trac/ticket/143</a>&gt;: "IANA registry for content/transfer encodings"
    1996          </li>
    1997          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    1998          </li>
    1999          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
    2000          </li>
    2001       </ul>
    2002       <p id="rfc.section.E.11.p.2">Partly resolved issues: </p>
    2003       <ul>
    2004          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    2005          </li>
    2006       </ul>
    2007       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
    2008       <p id="rfc.section.E.12.p.1">Closed issues: </p>
    2009       <ul>
    2010          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
    2011          </li>
    2012          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
    2013          </li>
    2014          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>&gt;: "Delimiting messages with multipart/byteranges"
    2015          </li>
    2016          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
    2017          </li>
    2018          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/136">http://tools.ietf.org/wg/httpbis/trac/ticket/136</a>&gt;: "confusing req. language for Content-Location"
    2019          </li>
    2020          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/167">http://tools.ietf.org/wg/httpbis/trac/ticket/167</a>&gt;: "Content-Location on 304 responses"
    2021          </li>
    2022          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/183">http://tools.ietf.org/wg/httpbis/trac/ticket/183</a>&gt;: "'requested resource' in content-encoding definition"
    2023          </li>
    2024          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
    2025          </li>
    2026       </ul>
    2027       <p id="rfc.section.E.12.p.2">Partly resolved issues: </p>
    2028       <ul>
    2029          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
    2030          </li>
    2031       </ul>
    2032       <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
    2033       <p id="rfc.section.E.13.p.1">Closed issues: </p>
    2034       <ul>
    2035          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
    2036          </li>
    2037       </ul>
     1950</pre></div>
     1951      <div id="change.log">
     1952         <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1953         <div>
     1954            <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
     1955            </h2>
     1956            <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1957            </p>
     1958         </div>
     1959         <div>
     1960            <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
     1961            </h2>
     1962            <p id="rfc.section.E.2.p.1">Closed issues: </p>
     1963            <ul>
     1964               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
     1965               </li>
     1966               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/14">http://tools.ietf.org/wg/httpbis/trac/ticket/14</a>&gt;: "Clarification regarding quoting of charset values" (&lt;<a href="http://purl.org/NET/http-errata#charactersets">http://purl.org/NET/http-errata#charactersets</a>&gt;)
     1967               </li>
     1968               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/16">http://tools.ietf.org/wg/httpbis/trac/ticket/16</a>&gt;: "Remove 'identity' token references" (&lt;<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>&gt;)
     1969               </li>
     1970               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/25">http://tools.ietf.org/wg/httpbis/trac/ticket/25</a>&gt;: "Accept-Encoding BNF"
     1971               </li>
     1972               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     1973               </li>
     1974               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/46">http://tools.ietf.org/wg/httpbis/trac/ticket/46</a>&gt;: "RFC1700 references"
     1975               </li>
     1976               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
     1977               </li>
     1978               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/65">http://tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
     1979               </li>
     1980               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/66">http://tools.ietf.org/wg/httpbis/trac/ticket/66</a>&gt;: "ISO-8859-1 Reference"
     1981               </li>
     1982               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative"
     1983               </li>
     1984               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
     1985               </li>
     1986            </ul>
     1987         </div>
     1988         <div>
     1989            <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
     1990            </h2>
     1991            <p id="rfc.section.E.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     1992            </p>
     1993            <ul>
     1994               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1995            </ul>
     1996         </div>
     1997         <div id="changes.since.02">
     1998            <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
     1999            <p id="rfc.section.E.4.p.1">Closed issues: </p>
     2000            <ul>
     2001               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
     2002               </li>
     2003               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
     2004               </li>
     2005               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
     2006               </li>
     2007            </ul>
     2008            <p id="rfc.section.E.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     2009            </p>
     2010            <ul>
     2011               <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     2012            </ul>
     2013         </div>
     2014         <div id="changes.since.03">
     2015            <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
     2016            <p id="rfc.section.E.5.p.1">Closed issues: </p>
     2017            <ul>
     2018               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
     2019               </li>
     2020               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/113">http://tools.ietf.org/wg/httpbis/trac/ticket/113</a>&gt;: "language tag matching (Accept-Language) vs RFC4647"
     2021               </li>
     2022               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/121">http://tools.ietf.org/wg/httpbis/trac/ticket/121</a>&gt;: "RFC 1806 has been replaced by RFC2183"
     2023               </li>
     2024            </ul>
     2025            <p id="rfc.section.E.5.p.2">Other changes: </p>
     2026            <ul>
     2027               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" -- rephrase the annotation and reference <a href="#BCP97" id="rfc.xref.BCP97.4"><cite title="Handling Normative References to Standards-Track Documents">[BCP97]</cite></a>.
     2028               </li>
     2029            </ul>
     2030         </div>
     2031         <div id="changes.since.04">
     2032            <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
     2033            <p id="rfc.section.E.6.p.1">Closed issues: </p>
     2034            <ul>
     2035               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
     2036               </li>
     2037            </ul>
     2038            <p id="rfc.section.E.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2039            </p>
     2040            <ul>
     2041               <li>Use "/" instead of "|" for alternatives.</li>
     2042               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     2043               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
     2044            </ul>
     2045         </div>
     2046         <div id="changes.since.05">
     2047            <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
     2048            <p id="rfc.section.E.7.p.1">Closed issues: </p>
     2049            <ul>
     2050               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
     2051               </li>
     2052            </ul>
     2053            <p id="rfc.section.E.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2054            </p>
     2055            <ul>
     2056               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     2057            </ul>
     2058            <p id="rfc.section.E.7.p.3">Other changes: </p>
     2059            <ul>
     2060               <li>Move definition of quality values into Part 1.</li>
     2061            </ul>
     2062         </div>
     2063         <div id="changes.since.06">
     2064            <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
     2065            <p id="rfc.section.E.8.p.1">Closed issues: </p>
     2066            <ul>
     2067               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
     2068               </li>
     2069               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
     2070               </li>
     2071            </ul>
     2072         </div>
     2073         <div id="changes.since.07">
     2074            <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
     2075            <p id="rfc.section.E.9.p.1">Closed issues: </p>
     2076            <ul>
     2077               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
     2078               </li>
     2079               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>&gt;: "Clarify rules for determining what entities a response carries"
     2080               </li>
     2081               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/154">http://tools.ietf.org/wg/httpbis/trac/ticket/154</a>&gt;: "Content-Location base-setting problems"
     2082               </li>
     2083               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
     2084               </li>
     2085               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/188">http://tools.ietf.org/wg/httpbis/trac/ticket/188</a>&gt;: "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
     2086               </li>
     2087               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/189">http://tools.ietf.org/wg/httpbis/trac/ticket/189</a>&gt;: "move definitions of gzip/deflate/compress to part 1"
     2088               </li>
     2089            </ul>
     2090            <p id="rfc.section.E.9.p.2">Partly resolved issues: </p>
     2091            <ul>
     2092               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
     2093               </li>
     2094               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/149">http://tools.ietf.org/wg/httpbis/trac/ticket/149</a>&gt;: "update IANA requirements wrt Content-Coding values" (add the IANA Considerations subsection)
     2095               </li>
     2096            </ul>
     2097         </div>
     2098         <div id="changes.since.08">
     2099            <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
     2100            <p id="rfc.section.E.10.p.1">Closed issues: </p>
     2101            <ul>
     2102               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
     2103               </li>
     2104               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/181">http://tools.ietf.org/wg/httpbis/trac/ticket/181</a>&gt;: "Accept-Language: which RFC4647 filtering?"
     2105               </li>
     2106            </ul>
     2107         </div>
     2108         <div id="changes.since.09">
     2109            <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
     2110            <p id="rfc.section.E.11.p.1">Closed issues: </p>
     2111            <ul>
     2112               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
     2113               </li>
     2114               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/143">http://tools.ietf.org/wg/httpbis/trac/ticket/143</a>&gt;: "IANA registry for content/transfer encodings"
     2115               </li>
     2116               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
     2117               </li>
     2118               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
     2119               </li>
     2120            </ul>
     2121            <p id="rfc.section.E.11.p.2">Partly resolved issues: </p>
     2122            <ul>
     2123               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
     2124               </li>
     2125            </ul>
     2126         </div>
     2127         <div id="changes.since.10">
     2128            <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
     2129            <p id="rfc.section.E.12.p.1">Closed issues: </p>
     2130            <ul>
     2131               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
     2132               </li>
     2133               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
     2134               </li>
     2135               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>&gt;: "Delimiting messages with multipart/byteranges"
     2136               </li>
     2137               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
     2138               </li>
     2139               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/136">http://tools.ietf.org/wg/httpbis/trac/ticket/136</a>&gt;: "confusing req. language for Content-Location"
     2140               </li>
     2141               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/167">http://tools.ietf.org/wg/httpbis/trac/ticket/167</a>&gt;: "Content-Location on 304 responses"
     2142               </li>
     2143               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/183">http://tools.ietf.org/wg/httpbis/trac/ticket/183</a>&gt;: "'requested resource' in content-encoding definition"
     2144               </li>
     2145               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
     2146               </li>
     2147            </ul>
     2148            <p id="rfc.section.E.12.p.2">Partly resolved issues: </p>
     2149            <ul>
     2150               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
     2151               </li>
     2152            </ul>
     2153         </div>
     2154         <div id="changes.since.11">
     2155            <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
     2156            <p id="rfc.section.E.13.p.1">Closed issues: </p>
     2157            <ul>
     2158               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
     2159               </li>
     2160            </ul>
     2161         </div>
     2162      </div>
    20382163      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    20392164      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
     
    20412166      <div class="print2col">
    20422167         <ul class="ind">
    2043             <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    2044                   <li class="indline1">Accept header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">5.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept.3">7.1</a></li>
    2045                   <li class="indline1">Accept-Charset header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-charset.1">5.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">7.1</a></li>
    2046                   <li class="indline1">Accept-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
    2047                   <li class="indline1">Accept-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">7.1</a></li>
     2168            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
     2169                  <li>Accept header&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.a.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
     2170                  <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></li>
     2171                  <li>Accept-Encoding header&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
     2172                  <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>
    20482173               </ul>
    20492174            </li>
    2050             <li class="indline0"><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul class="ind">
    2051                   <li class="indline1"><em>BCP97</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.BCP97.1">10.1</a>, <a class="iref" href="#rfc.xref.BCP97.2">10.1</a>, <a class="iref" href="#rfc.xref.BCP97.3">10.1</a>, <a class="iref" href="#BCP97"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.BCP97.4">E.5</a></li>
     2175            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
     2176                  <li><em>BCP97</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP97.1">10.1</a>, <a href="#rfc.xref.BCP97.2">10.1</a>, <a href="#rfc.xref.BCP97.3">10.1</a>, <a href="#BCP97"><b>10.2</b></a>, <a href="#rfc.xref.BCP97.4">E.5</a></li>
    20522177               </ul>
    20532178            </li>
    2054             <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    2055                   <li class="indline1">Coding Format&nbsp;&nbsp;
    2056                      <ul class="ind">
    2057                         <li class="indline1">compress&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">2.2</a></li>
    2058                         <li class="indline1">deflate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">2.2</a></li>
    2059                         <li class="indline1">gzip&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5">2.2</a></li>
    2060                         <li class="indline1">identity&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">2.2</a></li>
     2179            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
     2180                  <li>Coding Format&nbsp;&nbsp;
     2181                     <ul>
     2182                        <li>compress&nbsp;&nbsp;<a href="#rfc.iref.c.3">2.2</a></li>
     2183                        <li>deflate&nbsp;&nbsp;<a href="#rfc.iref.c.4">2.2</a></li>
     2184                        <li>gzip&nbsp;&nbsp;<a href="#rfc.iref.c.5">2.2</a></li>
     2185                        <li>identity&nbsp;&nbsp;<a href="#rfc.iref.c.6">2.2</a></li>
    20612186                     </ul>
    20622187                  </li>
    2063                   <li class="indline1">compress (Coding Format)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">2.2</a></li>
    2064                   <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.1</a></li>
    2065                   <li class="indline1">Content-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">7.1</a></li>
    2066                   <li class="indline1">Content-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">7.1</a></li>
    2067                   <li class="indline1">Content-Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">4.1</a>, <a class="iref" href="#rfc.iref.c.9"><b>6.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">7.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C</a></li>
    2068                   <li class="indline1">Content-MD5 header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.10"><b>6.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">7.1</a></li>
    2069                   <li class="indline1">Content-Type header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">4.1</a>, <a class="iref" href="#rfc.iref.c.11"><b>6.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">7.1</a></li>
     2188                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.2">2.2</a></li>
     2189                  <li>content negotiation&nbsp;&nbsp;<a href="#rfc.iref.c.1">1.1</a></li>
     2190                  <li>Content-Encoding header&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.7"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
     2191                  <li>Content-Language header&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.8"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
     2192                  <li>Content-Location header&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.9"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
     2193                  <li>Content-MD5 header&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.c.10"><b>6.8</b></a>, <a href="#rfc.xref.header.content-md5.2">7.1</a></li>
     2194                  <li>Content-Type header&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.11"><b>6.9</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
    20702195               </ul>
    20712196            </li>
    2072             <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">
    2073                   <li class="indline1">deflate (Coding Format)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.d.1">2.2</a></li>
     2197            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
     2198                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">2.2</a></li>
    20742199               </ul>
    20752200            </li>
    2076             <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    2077                   <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    2078                      <ul class="ind">
    2079                         <li class="indline1"><tt>Accept</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>6.1</b></a></li>
    2080                         <li class="indline1"><tt>Accept-Charset</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>6.2</b></a></li>
    2081                         <li class="indline1"><tt>Accept-Charset-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>6.2</b></a></li>
    2082                         <li class="indline1"><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>6.3</b></a></li>
    2083                         <li class="indline1"><tt>Accept-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>6.3</b></a></li>
    2084                         <li class="indline1"><tt>accept-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>6.1</b></a></li>
    2085                         <li class="indline1"><tt>Accept-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>6.4</b></a></li>
    2086                         <li class="indline1"><tt>Accept-Language-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>6.4</b></a></li>
    2087                         <li class="indline1"><tt>accept-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>6.1</b></a></li>
    2088                         <li class="indline1"><tt>Accept-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>6.1</b></a></li>
    2089                         <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>2.3</b></a></li>
    2090                         <li class="indline1"><tt>charset</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2.1</b></a></li>
    2091                         <li class="indline1"><tt>codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>6.3</b></a></li>
    2092                         <li class="indline1"><tt>content-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>
    2093                         <li class="indline1"><tt>Content-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>6.5</b></a></li>
    2094                         <li class="indline1"><tt>Content-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>6.5</b></a></li>
    2095                         <li class="indline1"><tt>Content-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>6.6</b></a></li>
    2096                         <li class="indline1"><tt>Content-Language-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>6.6</b></a></li>
    2097                         <li class="indline1"><tt>Content-Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>6.7</b></a></li>
    2098                         <li class="indline1"><tt>Content-Location-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>6.7</b></a></li>
    2099                         <li class="indline1"><tt>Content-MD5</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>6.8</b></a></li>
    2100                         <li class="indline1"><tt>Content-MD5-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>6.8</b></a></li>
    2101                         <li class="indline1"><tt>Content-Type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>6.9</b></a></li>
    2102                         <li class="indline1"><tt>Content-Type-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>6.9</b></a></li>
    2103                         <li class="indline1"><tt>language-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>6.4</b></a></li>
    2104                         <li class="indline1"><tt>language-tag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>2.4</b></a></li>
    2105                         <li class="indline1"><tt>media-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>6.1</b></a></li>
    2106                         <li class="indline1"><tt>media-type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>2.3</b></a></li>
    2107                         <li class="indline1"><tt>MIME-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>A.1</b></a></li>
    2108                         <li class="indline1"><tt>MIME-Version-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>A.1</b></a></li>
    2109                         <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>2.3</b></a></li>
    2110                         <li class="indline1"><tt>subtype</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>2.3</b></a></li>
    2111                         <li class="indline1"><tt>type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>2.3</b></a></li>
    2112                         <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>2.3</b></a></li>
     2201            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
     2202                  <li><tt>Grammar</tt>&nbsp;&nbsp;
     2203                     <ul>
     2204                        <li><tt>Accept</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.1</b></a></li>
     2205                        <li><tt>Accept-Charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.2</b></a></li>
     2206                        <li><tt>Accept-Charset-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.2</b></a></li>
     2207                        <li><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>6.3</b></a></li>
     2208                        <li><tt>Accept-Encoding-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>6.3</b></a></li>
     2209                        <li><tt>accept-ext</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.1</b></a></li>
     2210                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.4</b></a></li>
     2211                        <li><tt>Accept-Language-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.4</b></a></li>
     2212                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.1</b></a></li>
     2213                        <li><tt>Accept-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.1</b></a></li>
     2214                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>2.3</b></a></li>
     2215                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2.1</b></a></li>
     2216                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>6.3</b></a></li>
     2217                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.2</b></a></li>
     2218                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.5</b></a></li>
     2219                        <li><tt>Content-Encoding-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>6.5</b></a></li>
     2220                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>6.6</b></a></li>
     2221                        <li><tt>Content-Language-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>6.6</b></a></li>
     2222                        <li><tt>Content-Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>6.7</b></a></li>
     2223                        <li><tt>Content-Location-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>6.7</b></a></li>
     2224                        <li><tt>Content-MD5</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>6.8</b></a></li>
     2225                        <li><tt>Content-MD5-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>6.8</b></a></li>
     2226                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>6.9</b></a></li>
     2227                        <li><tt>Content-Type-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>6.9</b></a></li>
     2228                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.4</b></a></li>
     2229                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>2.4</b></a></li>
     2230                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.1</b></a></li>
     2231                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.3</b></a></li>
     2232                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>A.1</b></a></li>
     2233                        <li><tt>MIME-Version-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>A.1</b></a></li>
     2234                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>2.3</b></a></li>
     2235                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.3</b></a></li>
     2236                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.3</b></a></li>
     2237                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>2.3</b></a></li>
    21132238                     </ul>
    21142239                  </li>
    2115                   <li class="indline1">gzip (Coding Format)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3">2.2</a></li>
     2240                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.3">2.2</a></li>
    21162241               </ul>
    21172242            </li>
    2118             <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    2119                   <li class="indline1">Headers&nbsp;&nbsp;
    2120                      <ul class="ind">
    2121                         <li class="indline1">Accept&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">5.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a>, <a class="iref" href="#rfc.xref.header.accept.3">7.1</a></li>
    2122                         <li class="indline1">Accept-Charset&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-charset.1">5.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">7.1</a></li>
    2123                         <li class="indline1">Accept-Encoding&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a>, <a class="iref" href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
    2124                         <li class="indline1">Accept-Language&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a>, <a class="iref" href="#rfc.xref.header.accept-language.2">7.1</a></li>
    2125                         <li class="indline1">Content-Encoding&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">7.1</a></li>
    2126                         <li class="indline1">Content-Language&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">7.1</a></li>
    2127                         <li class="indline1">Content-Location&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">4.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>6.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">7.1</a>, <a class="iref" href="#rfc.xref.header.content-location.3">C</a></li>
    2128                         <li class="indline1">Content-MD5&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>6.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">7.1</a></li>
    2129                         <li class="indline1">Content-Type&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">4.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>6.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">7.1</a></li>
    2130                         <li class="indline1">MIME-Version&nbsp;&nbsp;<a class="iref" href="#rfc.xref.mime-version.1">7.1</a>, <a class="iref" href="#rfc.iref.h.10"><b>A.1</b></a></li>
     2243            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
     2244                  <li>Headers&nbsp;&nbsp;
     2245                     <ul>
     2246                        <li>Accept&nbsp;&nbsp;<a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.h.1"><b>6.1</b></a>, <a href="#rfc.xref.header.accept.3">7.1</a></li>
     2247                        <li>Accept-Charset&nbsp;&nbsp;<a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.h.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">7.1</a></li>
     2248                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.h.3"><b>6.3</b></a>, <a href="#rfc.xref.header.accept-encoding.3">7.1</a></li>
     2249                        <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>
     2250                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.h.5"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a>, <a href="#rfc.xref.header.content-encoding.4">7.1</a></li>
     2251                        <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>
     2252                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.h.7"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
     2253                        <li>Content-MD5&nbsp;&nbsp;<a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.h.8"><b>6.8</b></a>, <a href="#rfc.xref.header.content-md5.2">7.1</a></li>
     2254                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.h.9"><b>6.9</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
     2255                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.h.10"><b>A.1</b></a></li>
    21312256                     </ul>
    21322257                  </li>
    21332258               </ul>
    21342259            </li>
    2135             <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    2136                   <li class="indline1">identity (Coding Format)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.1">2.2</a></li>
    2137                   <li class="indline1"><em>ISO-8859-1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>10.1</b></a></li>
     2260            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
     2261                  <li>identity (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.i.1">2.2</a></li>
     2262                  <li><em>ISO-8859-1</em>&nbsp;&nbsp;<a href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a href="#ISO-8859-1"><b>10.1</b></a></li>
    21382263               </ul>
    21392264            </li>
    2140             <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    2141                   <li class="indline1">MIME-Version header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.mime-version.1">7.1</a>, <a class="iref" href="#rfc.iref.m.1"><b>A.1</b></a></li>
     2265            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
     2266                  <li>MIME-Version header&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.m.1"><b>A.1</b></a></li>
    21422267               </ul>
    21432268            </li>
    2144             <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2145                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.3</a>, <a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.10">2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">2.2.1</a>, <a class="iref" href="#rfc.xref.Part1.14">2.2.1</a>, <a class="iref" href="#rfc.xref.Part1.15">3.1</a>, <a class="iref" href="#rfc.xref.Part1.16">3.2</a>, <a class="iref" href="#rfc.xref.Part1.17">6.1</a>, <a class="iref" href="#rfc.xref.Part1.18">6.3</a>, <a class="iref" href="#rfc.xref.Part1.19">6.7</a>, <a class="iref" href="#rfc.xref.Part1.20">7.2</a>, <a class="iref" href="#rfc.xref.Part1.21">7.2</a>, <a class="iref" href="#rfc.xref.Part1.22">7.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.23">A.3</a>, <a class="iref" href="#rfc.xref.Part1.24">A.6</a><ul class="ind">
    2146                         <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.3</a></li>
    2147                         <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.3.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.3.1</a></li>
    2148                         <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.3.2</a></li>
    2149                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">3.2</a></li>
    2150                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.19">6.7</a></li>
    2151                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.23">A.3</a></li>
    2152                         <li class="indline1"><em>Section 6.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">2.2.1</a></li>
    2153                         <li class="indline1"><em>Section 6.2.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2.2</a>, <a class="iref" href="#rfc.xref.Part1.20">7.2</a></li>
    2154                         <li class="indline1"><em>Section 6.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">2.2.1</a></li>
    2155                         <li class="indline1"><em>Section 6.2.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2.2</a>, <a class="iref" href="#rfc.xref.Part1.21">7.2</a></li>
    2156                         <li class="indline1"><em>Section 6.2.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.12">2.2</a>, <a class="iref" href="#rfc.xref.Part1.22">7.2</a></li>
    2157                         <li class="indline1"><em>Section 6.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.9">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.17">6.1</a>, <a class="iref" href="#rfc.xref.Part1.18">6.3</a></li>
    2158                         <li class="indline1"><em>Section 9.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.7">1.3.2</a>, <a class="iref" href="#rfc.xref.Part1.15">3.1</a></li>
    2159                         <li class="indline1"><em>Section 9.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.24">A.6</a></li>
     2269            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
     2270                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a>, <a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.13">2.2.1</a>, <a href="#rfc.xref.Part1.14">2.2.1</a>, <a href="#rfc.xref.Part1.15">3.1</a>, <a href="#rfc.xref.Part1.16">3.2</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a>, <a href="#rfc.xref.Part1.19">6.7</a>, <a href="#rfc.xref.Part1.20">7.2</a>, <a href="#rfc.xref.Part1.21">7.2</a>, <a href="#rfc.xref.Part1.22">7.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.23">A.3</a>, <a href="#rfc.xref.Part1.24">A.6</a><ul>
     2271                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a></li>
     2272                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.3.1</a>, <a href="#rfc.xref.Part1.3">1.3.1</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a></li>
     2273                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.3.2</a>, <a href="#rfc.xref.Part1.8">1.3.2</a></li>
     2274                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">3.2</a></li>
     2275                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">6.7</a></li>
     2276                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">A.3</a></li>
     2277                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">2.2.1</a></li>
     2278                        <li><em>Section 6.2.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">2.2</a>, <a href="#rfc.xref.Part1.20">7.2</a></li>
     2279                        <li><em>Section 6.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">2.2.1</a></li>
     2280                        <li><em>Section 6.2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">2.2</a>, <a href="#rfc.xref.Part1.21">7.2</a></li>
     2281                        <li><em>Section 6.2.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">2.2</a>, <a href="#rfc.xref.Part1.22">7.2</a></li>
     2282                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.3.2</a>, <a href="#rfc.xref.Part1.17">6.1</a>, <a href="#rfc.xref.Part1.18">6.3</a></li>
     2283                        <li><em>Section 9.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.3.2</a>, <a href="#rfc.xref.Part1.15">3.1</a></li>
     2284                        <li><em>Section 9.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">A.6</a></li>
    21602285                     </ul>
    21612286                  </li>
    2162                   <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind">
    2163                         <li class="indline1"><em>Section 9.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">5.1</a></li>
     2287                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a>, <a href="#Part2"><b>10.1</b></a><ul>
     2288                        <li><em>Section 9.9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">5.1</a></li>
    21642289                     </ul>
    21652290                  </li>
    2166                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a>, <a class="iref" href="#Part4"><b>10.1</b></a><ul class="ind">
    2167                         <li class="indline1"><em>Section 6.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a></li>
     2291                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.3.2</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
     2292                        <li><em>Section 6.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.3.2</a>, <a href="#rfc.xref.Part4.2">4.1</a></li>
    21682293                     </ul>
    21692294                  </li>
    2170                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a>, <a class="iref" href="#Part5"><b>10.1</b></a><ul class="ind">
    2171                         <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a></li>
     2295                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1.3.2</a>, <a href="#rfc.xref.Part5.2">3.1</a>, <a href="#Part5"><b>10.1</b></a><ul>
     2296                        <li><em>Section 5.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1.3.2</a>, <a href="#rfc.xref.Part5.2">3.1</a></li>
    21722297                     </ul>
    21732298                  </li>
    2174                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.1</a>, <a class="iref" href="#Part6"><b>10.1</b></a><ul class="ind">
    2175                         <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3.2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a></li>
    2176                         <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">5.1</a></li>
     2299                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1.3.2</a>, <a href="#rfc.xref.Part6.2">4.1</a>, <a href="#rfc.xref.Part6.3">5.1</a>, <a href="#Part6"><b>10.1</b></a><ul>
     2300                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1.3.2</a>, <a href="#rfc.xref.Part6.2">4.1</a></li>
     2301                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.3">5.1</a></li>
    21772302                     </ul>
    21782303                  </li>
    2179                   <li class="indline1">payload&nbsp;&nbsp;<a class="iref" href="#rfc.iref.p.1">3</a></li>
     2304                  <li>payload&nbsp;&nbsp;<a href="#rfc.iref.p.1">3</a></li>
    21802305               </ul>
    21812306            </li>
    2182             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    2183                   <li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">4</a></li>
    2184                   <li class="indline1"><em>RFC1864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1864.1">6.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">6.8</a>, <a class="iref" href="#RFC1864"><b>10.1</b></a></li>
    2185                   <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<a class="iref" href="#RFC1945"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>
    2186                   <li class="indline1"><em>RFC1950</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1950.1">7.2</a>, <a class="iref" href="#RFC1950"><b>10.1</b></a></li>
    2187                   <li class="indline1"><em>RFC1951</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1951.1">7.2</a>, <a class="iref" href="#RFC1951"><b>10.1</b></a></li>
    2188                   <li class="indline1"><em>RFC1952</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1952.1">7.2</a>, <a class="iref" href="#RFC1952"><b>10.1</b></a></li>
    2189                   <li class="indline1"><em>RFC2045</em>&nbsp;&nbsp;<a class="iref" href="#RFC2045"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.RFC2045.1">A</a>, <a class="iref" href="#rfc.xref.RFC2045.2">A.1</a></li>
    2190                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a>, <a class="iref" href="#rfc.xref.RFC2046.3">4.2</a>, <a class="iref" href="#RFC2046"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.4">A.2</a><ul class="ind">
    2191                         <li class="indline1"><em>Section 4.5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.3">4.2</a></li>
    2192                         <li class="indline1"><em>Section 5.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a></li>
     2307            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     2308                  <li>representation&nbsp;&nbsp;<a href="#rfc.iref.r.1">4</a></li>
     2309                  <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>
     2310                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li>
     2311                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">7.2</a>, <a href="#RFC1950"><b>10.1</b></a></li>
     2312                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">7.2</a>, <a href="#RFC1951"><b>10.1</b></a></li>
     2313                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">7.2</a>, <a href="#RFC1952"><b>10.1</b></a></li>
     2314                  <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#RFC2045"><b>10.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a></li>
     2315                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">2.3</a>, <a href="#rfc.xref.RFC2046.2">2.3.2</a>, <a href="#rfc.xref.RFC2046.3">4.2</a>, <a href="#RFC2046"><b>10.1</b></a>, <a href="#rfc.xref.RFC2046.4">A.2</a><ul>
     2316                        <li><em>Section 4.5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.3">4.2</a></li>
     2317                        <li><em>Section 5.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.2">2.3.2</a></li>
    21932318                     </ul>
    21942319                  </li>
    2195                   <li class="indline1"><em>RFC2049</em>&nbsp;&nbsp;<a class="iref" href="#RFC2049"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">
    2196                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li>
     2320                  <li><em>RFC2049</em>&nbsp;&nbsp;<a href="#RFC2049"><b>10.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul>
     2321                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2049.1">A.2</a></li>
    21972322                     </ul>
    21982323                  </li>
    2199                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">10.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">10.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">10.1</a>, <a class="iref" href="#RFC2068"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a></li>
    2200                   <li class="indline1"><em>RFC2076</em>&nbsp;&nbsp;<a class="iref" href="#RFC2076"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>
    2201                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>10.1</b></a></li>
    2202                   <li class="indline1"><em>RFC2277</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>10.2</b></a></li>
    2203                   <li class="indline1"><em>RFC2295</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2295.1">5</a>, <a class="iref" href="#RFC2295"><b>10.2</b></a></li>
    2204                   <li class="indline1"><em>RFC2388</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>10.2</b></a></li>
    2205                   <li class="indline1"><em>RFC2557</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2557.1">6.7</a>, <a class="iref" href="#RFC2557"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.2">A.7</a><ul class="ind">
    2206                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2557.1">6.7</a></li>
     2324                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">10.1</a>, <a href="#rfc.xref.RFC2068.2">10.1</a>, <a href="#rfc.xref.RFC2068.3">10.1</a>, <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a></li>
     2325                  <li><em>RFC2076</em>&nbsp;&nbsp;<a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li>
     2326                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>10.1</b></a></li>
     2327                  <li><em>RFC2277</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2277.1">2.1</a>, <a href="#RFC2277"><b>10.2</b></a></li>
     2328                  <li><em>RFC2295</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2295.1">5</a>, <a href="#RFC2295"><b>10.2</b></a></li>
     2329                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">2.3.2</a>, <a href="#RFC2388"><b>10.2</b></a></li>
     2330                  <li><em>RFC2557</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a>, <a href="#RFC2557"><b>10.2</b></a>, <a href="#rfc.xref.RFC2557.2">A.7</a><ul>
     2331                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2557.1">6.7</a></li>
    22072332                     </ul>
    22082333                  </li>
    2209                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">6.4</a>, <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a><ul class="ind">
    2210                         <li class="indline1"><em>Section 14.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.2">6.4</a></li>
     2334                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">6.4</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.3">E.1</a><ul>
     2335                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">6.4</a></li>
    22112336                     </ul>
    22122337                  </li>
    2213                   <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>10.2</b></a></li>
    2214                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">7.1</a>, <a class="iref" href="#RFC3864"><b>10.2</b></a></li>
    2215                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#RFC4288"><b>10.2</b></a></li>
    2216                   <li class="indline1"><em>RFC4647</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4647.1">6.4</a>, <a class="iref" href="#rfc.xref.RFC4647.2">6.4</a>, <a class="iref" href="#rfc.xref.RFC4647.3">6.4</a>, <a class="iref" href="#rfc.xref.RFC4647.4">6.4</a>, <a class="iref" href="#RFC4647"><b>10.1</b></a><ul class="ind">
    2217                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4647.1">6.4</a></li>
    2218                         <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4647.2">6.4</a></li>
    2219                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4647.3">6.4</a></li>
    2220                         <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4647.4">6.4</a></li>
     2338                  <li><em>RFC3629</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3629.1">2.1</a>, <a href="#RFC3629"><b>10.2</b></a></li>
     2339                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li>
     2340                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4288.1">2.3</a>, <a href="#RFC4288"><b>10.2</b></a></li>
     2341                  <li><em>RFC4647</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a>, <a href="#rfc.xref.RFC4647.2">6.4</a>, <a href="#rfc.xref.RFC4647.3">6.4</a>, <a href="#rfc.xref.RFC4647.4">6.4</a>, <a href="#RFC4647"><b>10.1</b></a><ul>
     2342                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.1">6.4</a></li>
     2343                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.2">6.4</a></li>
     2344                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.3">6.4</a></li>
     2345                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4647.4">6.4</a></li>
    22212346                     </ul>
    22222347                  </li>
    2223                   <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.2.1</a>, <a class="iref" href="#RFC5226"><b>10.2</b></a><ul class="ind">
    2224                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.2.1</a></li>
     2348                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
     2349                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2.1</a></li>
    22252350                     </ul>
    22262351                  </li>
    2227                   <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.3</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.3</a>, <a class="iref" href="#RFC5234"><b>10.1</b></a><ul class="ind">
    2228                         <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.3</a></li>
     2352                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.3</a>, <a href="#rfc.xref.RFC5234.2">1.3</a>, <a href="#RFC5234"><b>10.1</b></a><ul>
     2353                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.3</a></li>
    22292354                     </ul>
    22302355                  </li>
    2231                   <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#RFC5322"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC5322.1">A</a></li>
    2232                   <li class="indline1"><em>RFC5646</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5646.1">2.4</a>, <a class="iref" href="#rfc.xref.RFC5646.2">2.4</a>, <a class="iref" href="#rfc.xref.RFC5646.3">2.4</a>, <a class="iref" href="#RFC5646"><b>10.1</b></a><ul class="ind">
    2233                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5646.2">2.4</a></li>
     2356                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#RFC5322"><b>10.2</b></a>, <a href="#rfc.xref.RFC5322.1">A</a></li>
     2357                  <li><em>RFC5646</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.1">2.4</a>, <a href="#rfc.xref.RFC5646.2">2.4</a>, <a href="#rfc.xref.RFC5646.3">2.4</a>, <a href="#RFC5646"><b>10.1</b></a><ul>
     2358                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5646.2">2.4</a></li>
    22342359                     </ul>
    22352360                  </li>
     
    22382363         </ul>
    22392364      </div>
     2365      <div class="avoidbreak">
     2366         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     2367         <p><b>Roy T. Fielding</b>
     2368            (editor)
     2369            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
     2370         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
     2371         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
     2372         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
     2373         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
     2374         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
     2375         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
     2376         <p><b>Yves Lafon</b>
     2377            (editor)
     2378            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
     2379         <p><b>Julian F. Reschke</b>
     2380            (editor)
     2381            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
     2382      </div>
    22402383   </body>
    22412384</html>
Note: See TracChangeset for help on using the changeset viewer.