Ignore:
Timestamp:
09/05/14 14:39:08 (6 years ago)
Author:
julian.reschke@…
Message:

updated AUTH48 versions of RFC7230 and RFC7231 (#553)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/rfc7231.diff.html

    r2663 r2665  
    125125      <tr><td class="lineno" valign="top"></td><td class="left">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89</td><td> </td><td class="right">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89</td><td class="lineno" valign="top"></td></tr>
    126126      <tr><td class="lineno" valign="top"></td><td class="left">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td> </td><td class="right">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    127       <tr><td><a name="diff0008" /></td></tr>
    128       <tr><td class="lineno" valign="top"></td><td class="lblock">     A.6.  MHTML and Line<span class="delete"> </span>Length Limitations  . . . . . . . . . . . . 90</td><td> </td><td class="rblock">     A.6.  MHTML and Line<span class="insert">-</span>Length Limitations  . . . . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
     127      <tr><td class="lineno" valign="top"></td><td class="left">     A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90</td><td> </td><td class="right">     A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    129128      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90</td><td> </td><td class="right">   Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    130129      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 93</td><td> </td><td class="right">   Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 93</td><td class="lineno" valign="top"></td></tr>
     
    132131      <tr><td class="lineno" valign="top"></td><td class="left">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96</td><td> </td><td class="right">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96</td><td class="lineno" valign="top"></td></tr>
    133132      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    134       <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
    135       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    136       <tr><td class="lineno" valign="top"></td><td class="left">   Each Hypertext Transfer Protocol (HTTP) message is either a request</td><td> </td><td class="right">   Each Hypertext Transfer Protocol (HTTP) message is either a request</td><td class="lineno" valign="top"></td></tr>
    137       <tr><td class="lineno" valign="top"></td><td class="left">   or a response.  A server listens on a connection for a request,</td><td> </td><td class="right">   or a response.  A server listens on a connection for a request,</td><td class="lineno" valign="top"></td></tr>
    138       <tr><td class="lineno" valign="top"></td><td class="left">   parses each message received, interprets the message semantics in</td><td> </td><td class="right">   parses each message received, interprets the message semantics in</td><td class="lineno" valign="top"></td></tr>
    139       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    140       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 8, line 48</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 8, line 48</em></th><td></td></tr>
    141       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    142       <tr><td class="lineno" valign="top"></td><td class="left">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td> </td><td class="right">     media-type = type "/" subtype *( OWS ";" OWS parameter )</td><td class="lineno" valign="top"></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="left">     type       = token</td><td> </td><td class="right">     type       = token</td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="left">     subtype    = token</td><td> </td><td class="right">     subtype    = token</td><td class="lineno" valign="top"></td></tr>
    145       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    146       <tr><td class="lineno" valign="top"></td><td class="left">   The type/subtype MAY be followed by parameters in the form of</td><td> </td><td class="right">   The type/subtype MAY be followed by parameters in the form of</td><td class="lineno" valign="top"></td></tr>
    147       <tr><td class="lineno" valign="top"></td><td class="left">   name=value pairs.</td><td> </td><td class="right">   name=value pairs.</td><td class="lineno" valign="top"></td></tr>
    148       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    149       <tr><td class="lineno" valign="top"></td><td class="left">     parameter      = token "=" ( token / quoted-string )</td><td> </td><td class="right">     parameter      = token "=" ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr>
    150       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    151       <tr><td><a name="diff0009" /></td></tr>
    152       <tr><td class="lineno" valign="top"></td><td class="lblock">   The type, subtype, and parameter name tokens are <span class="delete">case-insensitive.</span></td><td> </td><td class="rblock">   The type, subtype, and parameter name tokens are <span class="insert">case insensitive.</span></td><td class="lineno" valign="top"></td></tr>
    153       <tr><td class="lineno" valign="top"></td><td class="lblock">   Parameter values might or might not be <span class="delete">case-sensitive,</span> depending on</td><td> </td><td class="rblock">   Parameter values might or might not be <span class="insert">case sensitive,</span> depending on</td><td class="lineno" valign="top"></td></tr>
    154       <tr><td class="lineno" valign="top"></td><td class="left">   the semantics of the parameter name.  The presence or absence of a</td><td> </td><td class="right">   the semantics of the parameter name.  The presence or absence of a</td><td class="lineno" valign="top"></td></tr>
    155       <tr><td class="lineno" valign="top"></td><td class="left">   parameter might be significant to the processing of a media-type,</td><td> </td><td class="right">   parameter might be significant to the processing of a media-type,</td><td class="lineno" valign="top"></td></tr>
    156       <tr><td class="lineno" valign="top"></td><td class="left">   depending on its definition within the media type registry.</td><td> </td><td class="right">   depending on its definition within the media type registry.</td><td class="lineno" valign="top"></td></tr>
    157       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    158       <tr><td class="lineno" valign="top"></td><td class="left">   A parameter value that matches the token production can be</td><td> </td><td class="right">   A parameter value that matches the token production can be</td><td class="lineno" valign="top"></td></tr>
    159       <tr><td class="lineno" valign="top"></td><td class="left">   transmitted either as a token or within a quoted-string.  The quoted</td><td> </td><td class="right">   transmitted either as a token or within a quoted-string.  The quoted</td><td class="lineno" valign="top"></td></tr>
    160       <tr><td class="lineno" valign="top"></td><td class="left">   and unquoted values are equivalent.  For example, the following</td><td> </td><td class="right">   and unquoted values are equivalent.  For example, the following</td><td class="lineno" valign="top"></td></tr>
    161       <tr><td class="lineno" valign="top"></td><td class="left">   examples are all equivalent, but the first is preferred for</td><td> </td><td class="right">   examples are all equivalent, but the first is preferred for</td><td class="lineno" valign="top"></td></tr>
    162       <tr><td class="lineno" valign="top"></td><td class="left">   consistency:</td><td> </td><td class="right">   consistency:</td><td class="lineno" valign="top"></td></tr>
    163       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    164       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    165       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 9, line 33</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 9, line 33</em></th><td></td></tr>
    166       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    167       <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.2.  Charset</td><td> </td><td class="right">3.1.1.2.  Charset</td><td class="lineno" valign="top"></td></tr>
    168       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    169       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses charset names to indicate or negotiate the character</td><td> </td><td class="right">   HTTP uses charset names to indicate or negotiate the character</td><td class="lineno" valign="top"></td></tr>
    170       <tr><td class="lineno" valign="top"></td><td class="left">   encoding scheme of a textual representation [RFC6365].  A charset is</td><td> </td><td class="right">   encoding scheme of a textual representation [RFC6365].  A charset is</td><td class="lineno" valign="top"></td></tr>
    171       <tr><td class="lineno" valign="top"></td><td class="left">   identified by a case-insensitive token.</td><td> </td><td class="right">   identified by a case-insensitive token.</td><td class="lineno" valign="top"></td></tr>
    172       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    173       <tr><td class="lineno" valign="top"></td><td class="left">     charset = token</td><td> </td><td class="right">     charset = token</td><td class="lineno" valign="top"></td></tr>
    174       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    175       <tr><td class="lineno" valign="top"></td><td class="left">   Charset names ought to be registered in the IANA "Character Sets"</td><td> </td><td class="right">   Charset names ought to be registered in the IANA "Character Sets"</td><td class="lineno" valign="top"></td></tr>
    176       <tr><td><a name="diff0010" /></td></tr>
    177       <tr><td class="lineno" valign="top"></td><td class="lblock">   registry <span class="delete">(&lt;http://www.iana.org/assignments/character-sets&gt;)</span> according</td><td> </td><td class="rblock">   registry <span class="insert">&lt;http://www.iana.org/assignments/character-sets&gt;</span> according</td><td class="lineno" valign="top"></td></tr>
    178       <tr><td class="lineno" valign="top"></td><td class="left">   to the procedures defined in [RFC2978].</td><td> </td><td class="right">   to the procedures defined in [RFC2978].</td><td class="lineno" valign="top"></td></tr>
    179       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    180       <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.3.  Canonicalization and Text Defaults</td><td> </td><td class="right">3.1.1.3.  Canonicalization and Text Defaults</td><td class="lineno" valign="top"></td></tr>
    181       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    182       <tr><td class="lineno" valign="top"></td><td class="left">   Internet media types are registered with a canonical form in order to</td><td> </td><td class="right">   Internet media types are registered with a canonical form in order to</td><td class="lineno" valign="top"></td></tr>
    183       <tr><td class="lineno" valign="top"></td><td class="left">   be interoperable among systems with varying native encoding formats.</td><td> </td><td class="right">   be interoperable among systems with varying native encoding formats.</td><td class="lineno" valign="top"></td></tr>
    184       <tr><td class="lineno" valign="top"></td><td class="left">   Representations selected or transferred via HTTP ought to be in</td><td> </td><td class="right">   Representations selected or transferred via HTTP ought to be in</td><td class="lineno" valign="top"></td></tr>
    185       <tr><td class="lineno" valign="top"></td><td class="left">   canonical form, for many of the same reasons described by the</td><td> </td><td class="right">   canonical form, for many of the same reasons described by the</td><td class="lineno" valign="top"></td></tr>
    186       <tr><td class="lineno" valign="top"></td><td class="left">   Multipurpose Internet Mail Extensions (MIME) [RFC2045].  However, the</td><td> </td><td class="right">   Multipurpose Internet Mail Extensions (MIME) [RFC2045].  However, the</td><td class="lineno" valign="top"></td></tr>
    187       <tr><td class="lineno" valign="top"></td><td class="left">   performance characteristics of email deployments (i.e., store and</td><td> </td><td class="right">   performance characteristics of email deployments (i.e., store and</td><td class="lineno" valign="top"></td></tr>
    188       <tr><td class="lineno" valign="top"></td><td class="left">   forward messages to peers) are significantly different from those</td><td> </td><td class="right">   forward messages to peers) are significantly different from those</td><td class="lineno" valign="top"></td></tr>
    189       <tr><td class="lineno" valign="top"></td><td class="left">   common to HTTP and the Web (server-based information services).</td><td> </td><td class="right">   common to HTTP and the Web (server-based information services).</td><td class="lineno" valign="top"></td></tr>
    190       <tr><td class="lineno" valign="top"></td><td class="left">   Furthermore, MIME's constraints for the sake of compatibility with</td><td> </td><td class="right">   Furthermore, MIME's constraints for the sake of compatibility with</td><td class="lineno" valign="top"></td></tr>
    191       <tr><td class="lineno" valign="top"></td><td class="left">   older mail transfer protocols do not apply to HTTP (see Appendix A).</td><td> </td><td class="right">   older mail transfer protocols do not apply to HTTP (see Appendix A).</td><td class="lineno" valign="top"></td></tr>
    192       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    193       <tr><td class="lineno" valign="top"></td><td class="left">   MIME's canonical form requires that media subtypes of the "text" type</td><td> </td><td class="right">   MIME's canonical form requires that media subtypes of the "text" type</td><td class="lineno" valign="top"></td></tr>
    194       <tr><td class="lineno" valign="top"></td><td class="left">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td> </td><td class="right">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td class="lineno" valign="top"></td></tr>
    195       <tr><td><a name="diff0011" /></td></tr>
    196       <tr><td class="lineno" valign="top"></td><td class="lblock">   media with plain <span class="delete">CR</span> or <span class="delete">LF</span> alone representing a line break, when such</td><td> </td><td class="rblock">   media with plain <span class="insert">carriage return (CR)</span> or <span class="insert">line feed (LF)</span> alone</td><td class="lineno" valign="top"></td></tr>
    197       <tr><td class="lineno" valign="top"></td><td class="lblock">   line breaks are consistent for an entire representation.  An HTTP</td><td> </td><td class="rblock">   representing a line break, when such line breaks are consistent for</td><td class="lineno" valign="top"></td></tr>
    198       <tr><td class="lineno" valign="top"></td><td class="lblock">   sender MAY generate, and a recipient MUST be able to parse, line</td><td> </td><td class="rblock">   an entire representation.  An HTTP sender MAY generate, and a</td><td class="lineno" valign="top"></td></tr>
    199       <tr><td class="lineno" valign="top"></td><td class="lblock">   breaks in text media that consist of CRLF, bare CR, or bare LF.  In</td><td> </td><td class="rblock">   recipient MUST be able to parse, line breaks in text media that</td><td class="lineno" valign="top"></td></tr>
    200       <tr><td class="lineno" valign="top"></td><td class="lblock">   addition, text media in HTTP is not limited to charsets that use</td><td> </td><td class="rblock">   consist of CRLF, bare CR, or bare LF.  In addition, text media in</td><td class="lineno" valign="top"></td></tr>
    201       <tr><td class="lineno" valign="top"></td><td class="lblock">   octets 13 and 10 for CR and LF, respectively.  This flexibility</td><td> </td><td class="rblock">   HTTP is not limited to charsets that use octets 13 and 10 for CR and</td><td class="lineno" valign="top"></td></tr>
    202       <tr><td class="lineno" valign="top"></td><td class="lblock">   regarding line breaks applies only to text within a representation</td><td> </td><td class="rblock">   LF, respectively.  This flexibility regarding line breaks applies</td><td class="lineno" valign="top"></td></tr>
    203       <tr><td class="lineno" valign="top"></td><td class="lblock">   that has been assigned a "text" media type; it does not apply to</td><td> </td><td class="rblock">   only to text within a representation that has been assigned a "text"</td><td class="lineno" valign="top"></td></tr>
    204       <tr><td class="lineno" valign="top"></td><td class="lblock">   "multipart" types or HTTP elements outside the payload body (e.g.,</td><td> </td><td class="rblock">   media type; it does not apply to "multipart" types or HTTP elements</td><td class="lineno" valign="top"></td></tr>
    205       <tr><td class="lineno" valign="top"></td><td class="lblock">   header fields).</td><td> </td><td class="rblock">   outside the payload body (e.g., header fields).</td><td class="lineno" valign="top"></td></tr>
    206       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    207       <tr><td class="lineno" valign="top"></td><td class="left">   If a representation is encoded with a content-coding, the underlying</td><td> </td><td class="right">   If a representation is encoded with a content-coding, the underlying</td><td class="lineno" valign="top"></td></tr>
    208       <tr><td class="lineno" valign="top"></td><td class="left">   data ought to be in a form defined above prior to being encoded.</td><td> </td><td class="right">   data ought to be in a form defined above prior to being encoded.</td><td class="lineno" valign="top"></td></tr>
    209       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    210       <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.4.  Multipart Types</td><td> </td><td class="right">3.1.1.4.  Multipart Types</td><td class="lineno" valign="top"></td></tr>
    211       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    212       <tr><td class="lineno" valign="top"></td><td class="left">   MIME provides for a number of "multipart" types -- encapsulations of</td><td> </td><td class="right">   MIME provides for a number of "multipart" types -- encapsulations of</td><td class="lineno" valign="top"></td></tr>
    213       <tr><td class="lineno" valign="top"></td><td class="left">   one or more representations within a single message body.  All</td><td> </td><td class="right">   one or more representations within a single message body.  All</td><td class="lineno" valign="top"></td></tr>
    214       <tr><td class="lineno" valign="top"></td><td class="left">   multipart types share a common syntax, as defined in Section 5.1.1 of</td><td> </td><td class="right">   multipart types share a common syntax, as defined in Section 5.1.1 of</td><td class="lineno" valign="top"></td></tr>
    215       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC2046], and include a boundary parameter as part of the media type</td><td> </td><td class="right">   [RFC2046], and include a boundary parameter as part of the media type</td><td class="lineno" valign="top"></td></tr>
    216       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    217       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 11, line 35</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 11, line 35</em></th><td></td></tr>
    218       <tr><td class="lineno" valign="top"></td><td class="left">   Content coding values indicate an encoding transformation that has</td><td> </td><td class="right">   Content coding values indicate an encoding transformation that has</td><td class="lineno" valign="top"></td></tr>
    219       <tr><td class="lineno" valign="top"></td><td class="left">   been or can be applied to a representation.  Content codings are</td><td> </td><td class="right">   been or can be applied to a representation.  Content codings are</td><td class="lineno" valign="top"></td></tr>
    220       <tr><td class="lineno" valign="top"></td><td class="left">   primarily used to allow a representation to be compressed or</td><td> </td><td class="right">   primarily used to allow a representation to be compressed or</td><td class="lineno" valign="top"></td></tr>
    221       <tr><td class="lineno" valign="top"></td><td class="left">   otherwise usefully transformed without losing the identity of its</td><td> </td><td class="right">   otherwise usefully transformed without losing the identity of its</td><td class="lineno" valign="top"></td></tr>
    222       <tr><td class="lineno" valign="top"></td><td class="left">   underlying media type and without loss of information.  Frequently,</td><td> </td><td class="right">   underlying media type and without loss of information.  Frequently,</td><td class="lineno" valign="top"></td></tr>
    223       <tr><td class="lineno" valign="top"></td><td class="left">   the representation is stored in coded form, transmitted directly, and</td><td> </td><td class="right">   the representation is stored in coded form, transmitted directly, and</td><td class="lineno" valign="top"></td></tr>
    224       <tr><td class="lineno" valign="top"></td><td class="left">   only decoded by the final recipient.</td><td> </td><td class="right">   only decoded by the final recipient.</td><td class="lineno" valign="top"></td></tr>
    225       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    226       <tr><td class="lineno" valign="top"></td><td class="left">     content-coding   = token</td><td> </td><td class="right">     content-coding   = token</td><td class="lineno" valign="top"></td></tr>
    227       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    228       <tr><td><a name="diff0012" /></td></tr>
    229       <tr><td class="lineno" valign="top"></td><td class="lblock">   All content-coding values are case<span class="delete">-</span>insensitive and ought to be</td><td> </td><td class="rblock">   All content-coding values are case<span class="insert"> </span>insensitive and ought to be</td><td class="lineno" valign="top"></td></tr>
    230       <tr><td class="lineno" valign="top"></td><td class="left">   registered within the "HTTP Content Coding Registry", as defined in</td><td> </td><td class="right">   registered within the "HTTP Content Coding Registry", as defined in</td><td class="lineno" valign="top"></td></tr>
    231       <tr><td class="lineno" valign="top"></td><td class="left">   Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)</td><td> </td><td class="right">   Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)</td><td class="lineno" valign="top"></td></tr>
    232       <tr><td class="lineno" valign="top"></td><td class="left">   and Content-Encoding (Section 3.1.2.2) header fields.</td><td> </td><td class="right">   and Content-Encoding (Section 3.1.2.2) header fields.</td><td class="lineno" valign="top"></td></tr>
    233       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    234       <tr><td class="lineno" valign="top"></td><td class="left">   The following content-coding values are defined by this</td><td> </td><td class="right">   The following content-coding values are defined by this</td><td class="lineno" valign="top"></td></tr>
    235       <tr><td class="lineno" valign="top"></td><td class="left">   specification:</td><td> </td><td class="right">   specification:</td><td class="lineno" valign="top"></td></tr>
    236       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    237       <tr><td class="lineno" valign="top"></td><td class="left">      compress (and x-compress): See Section 4.2.1 of [RFC7230].</td><td> </td><td class="right">      compress (and x-compress): See Section 4.2.1 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    238       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    239       <tr><td class="lineno" valign="top"></td><td class="left">      deflate: See Section 4.2.2 of [RFC7230].</td><td> </td><td class="right">      deflate: See Section 4.2.2 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    240       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    241       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
    242       <tr><td class="lineno" valign="top"></td><td class="left">   Content-Language is to allow a user to identify and differentiate</td><td> </td><td class="right">   Content-Language is to allow a user to identify and differentiate</td><td class="lineno" valign="top"></td></tr>
    243       <tr><td class="lineno" valign="top"></td><td class="left">   representations according to the users' own preferred language.</td><td> </td><td class="right">   representations according to the users' own preferred language.</td><td class="lineno" valign="top"></td></tr>
    244       <tr><td class="lineno" valign="top"></td><td class="left">   Thus, if the content is intended only for a Danish-literate audience,</td><td> </td><td class="right">   Thus, if the content is intended only for a Danish-literate audience,</td><td class="lineno" valign="top"></td></tr>
    245       <tr><td class="lineno" valign="top"></td><td class="left">   the appropriate field is</td><td> </td><td class="right">   the appropriate field is</td><td class="lineno" valign="top"></td></tr>
    246       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    247       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Language: da</td><td> </td><td class="right">     Content-Language: da</td><td class="lineno" valign="top"></td></tr>
    248       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    249       <tr><td class="lineno" valign="top"></td><td class="left">   If no Content-Language is specified, the default is that the content</td><td> </td><td class="right">   If no Content-Language is specified, the default is that the content</td><td class="lineno" valign="top"></td></tr>
    250       <tr><td class="lineno" valign="top"></td><td class="left">   is intended for all language audiences.  This might mean that the</td><td> </td><td class="right">   is intended for all language audiences.  This might mean that the</td><td class="lineno" valign="top"></td></tr>
    251       <tr><td class="lineno" valign="top"></td><td class="left">   sender does not consider it to be specific to any natural language,</td><td> </td><td class="right">   sender does not consider it to be specific to any natural language,</td><td class="lineno" valign="top"></td></tr>
    252       <tr><td><a name="diff0013" /></td></tr>
    253       <tr><td class="lineno" valign="top"></td><td class="lblock">   or that the sender does not know <span class="delete">for which language it is intend</span>ed.</td><td> </td><td class="rblock">   or that the sender does not know <span class="insert">which language is being us</span>ed.</td><td class="lineno" valign="top"></td></tr>
    254       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    255       <tr><td class="lineno" valign="top"></td><td class="left">   Multiple languages MAY be listed for content that is intended for</td><td> </td><td class="right">   Multiple languages MAY be listed for content that is intended for</td><td class="lineno" valign="top"></td></tr>
    256       <tr><td class="lineno" valign="top"></td><td class="left">   multiple audiences.  For example, a rendition of the "Treaty of</td><td> </td><td class="right">   multiple audiences.  For example, a rendition of the "Treaty of</td><td class="lineno" valign="top"></td></tr>
    257       <tr><td class="lineno" valign="top"></td><td class="left">   Waitangi", presented simultaneously in the original Maori and English</td><td> </td><td class="right">   Waitangi", presented simultaneously in the original Maori and English</td><td class="lineno" valign="top"></td></tr>
    258       <tr><td class="lineno" valign="top"></td><td class="left">   versions, would call for</td><td> </td><td class="right">   versions, would call for</td><td class="lineno" valign="top"></td></tr>
    259       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    260       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Language: mi, en</td><td> </td><td class="right">     Content-Language: mi, en</td><td class="lineno" valign="top"></td></tr>
    261       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    262       <tr><td class="lineno" valign="top"></td><td class="left">   However, just because multiple languages are present within a</td><td> </td><td class="right">   However, just because multiple languages are present within a</td><td class="lineno" valign="top"></td></tr>
    263       <tr><td class="lineno" valign="top"></td><td class="left">   representation does not mean that it is intended for multiple</td><td> </td><td class="right">   representation does not mean that it is intended for multiple</td><td class="lineno" valign="top"></td></tr>
    264       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    265       <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 19, line 21</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 19, line 21</em></th><td></td></tr>
    266       <tr><td class="lineno" valign="top"></td><td class="left">   representations for a response (the dimensions over which it might</td><td> </td><td class="right">   representations for a response (the dimensions over which it might</td><td class="lineno" valign="top"></td></tr>
    267       <tr><td class="lineno" valign="top"></td><td class="left">   vary, such as language, content-coding, etc.) compared to various</td><td> </td><td class="right">   vary, such as language, content-coding, etc.) compared to various</td><td class="lineno" valign="top"></td></tr>
    268       <tr><td class="lineno" valign="top"></td><td class="left">   information supplied in the request, including both the explicit</td><td> </td><td class="right">   information supplied in the request, including both the explicit</td><td class="lineno" valign="top"></td></tr>
    269       <tr><td class="lineno" valign="top"></td><td class="left">   negotiation fields of Section 5.3 and implicit characteristics, such</td><td> </td><td class="right">   negotiation fields of Section 5.3 and implicit characteristics, such</td><td class="lineno" valign="top"></td></tr>
    270       <tr><td class="lineno" valign="top"></td><td class="left">   as the client's network address or parts of the User-Agent field.</td><td> </td><td class="right">   as the client's network address or parts of the User-Agent field.</td><td class="lineno" valign="top"></td></tr>
    271       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    272       <tr><td class="lineno" valign="top"></td><td class="left">   Proactive negotiation is advantageous when the algorithm for</td><td> </td><td class="right">   Proactive negotiation is advantageous when the algorithm for</td><td class="lineno" valign="top"></td></tr>
    273       <tr><td class="lineno" valign="top"></td><td class="left">   selecting from among the available representations is difficult to</td><td> </td><td class="right">   selecting from among the available representations is difficult to</td><td class="lineno" valign="top"></td></tr>
    274       <tr><td class="lineno" valign="top"></td><td class="left">   describe to a user agent, or when the server desires to send its</td><td> </td><td class="right">   describe to a user agent, or when the server desires to send its</td><td class="lineno" valign="top"></td></tr>
    275       <tr><td class="lineno" valign="top"></td><td class="left">   "best guess" to the user agent along with the first response (hoping</td><td> </td><td class="right">   "best guess" to the user agent along with the first response (hoping</td><td class="lineno" valign="top"></td></tr>
    276       <tr><td><a name="diff0014" /></td></tr>
    277       <tr><td class="lineno" valign="top"></td><td class="lblock">   to avoid the round<span class="delete"> </span>trip delay of a subsequent request if the "best</td><td> </td><td class="rblock">   to avoid the round<span class="insert">-</span>trip delay of a subsequent request if the "best</td><td class="lineno" valign="top"></td></tr>
    278       <tr><td class="lineno" valign="top"></td><td class="left">   guess" is good enough for the user).  In order to improve the</td><td> </td><td class="right">   guess" is good enough for the user).  In order to improve the</td><td class="lineno" valign="top"></td></tr>
    279       <tr><td class="lineno" valign="top"></td><td class="left">   server's guess, a user agent MAY send request header fields that</td><td> </td><td class="right">   server's guess, a user agent MAY send request header fields that</td><td class="lineno" valign="top"></td></tr>
    280       <tr><td class="lineno" valign="top"></td><td class="left">   describe its preferences.</td><td> </td><td class="right">   describe its preferences.</td><td class="lineno" valign="top"></td></tr>
    281       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    282       <tr><td class="lineno" valign="top"></td><td class="left">   Proactive negotiation has serious disadvantages:</td><td> </td><td class="right">   Proactive negotiation has serious disadvantages:</td><td class="lineno" valign="top"></td></tr>
    283       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    284       <tr><td class="lineno" valign="top"></td><td class="left">   o  It is impossible for the server to accurately determine what might</td><td> </td><td class="right">   o  It is impossible for the server to accurately determine what might</td><td class="lineno" valign="top"></td></tr>
    285       <tr><td class="lineno" valign="top"></td><td class="left">      be "best" for any given user, since that would require complete</td><td> </td><td class="right">      be "best" for any given user, since that would require complete</td><td class="lineno" valign="top"></td></tr>
    286       <tr><td class="lineno" valign="top"></td><td class="left">      knowledge of both the capabilities of the user agent and the</td><td> </td><td class="right">      knowledge of both the capabilities of the user agent and the</td><td class="lineno" valign="top"></td></tr>
    287       <tr><td class="lineno" valign="top"></td><td class="left">      intended use for the response (e.g., does the user want to view it</td><td> </td><td class="right">      intended use for the response (e.g., does the user want to view it</td><td class="lineno" valign="top"></td></tr>
    288       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    289       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>
    290       <tr><td class="lineno" valign="top"></td><td class="left">   example, a client can send conditional request header fields</td><td> </td><td class="right">   example, a client can send conditional request header fields</td><td class="lineno" valign="top"></td></tr>
    291       <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.2) to make the requested action conditional on the current</td><td> </td><td class="right">   (Section 5.2) to make the requested action conditional on the current</td><td class="lineno" valign="top"></td></tr>
    292       <tr><td class="lineno" valign="top"></td><td class="left">   state of the target resource ([RFC7232]).</td><td> </td><td class="right">   state of the target resource ([RFC7232]).</td><td class="lineno" valign="top"></td></tr>
    293       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    294       <tr><td class="lineno" valign="top"></td><td class="left">     method = token</td><td> </td><td class="right">     method = token</td><td class="lineno" valign="top"></td></tr>
    295       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    296       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP was originally designed to be usable as an interface to</td><td> </td><td class="right">   HTTP was originally designed to be usable as an interface to</td><td class="lineno" valign="top"></td></tr>
    297       <tr><td class="lineno" valign="top"></td><td class="left">   distributed object systems.  The request method was envisioned as</td><td> </td><td class="right">   distributed object systems.  The request method was envisioned as</td><td class="lineno" valign="top"></td></tr>
    298       <tr><td class="lineno" valign="top"></td><td class="left">   applying semantics to a target resource in much the same way as</td><td> </td><td class="right">   applying semantics to a target resource in much the same way as</td><td class="lineno" valign="top"></td></tr>
    299       <tr><td class="lineno" valign="top"></td><td class="left">   invoking a defined method on an identified object would apply</td><td> </td><td class="right">   invoking a defined method on an identified object would apply</td><td class="lineno" valign="top"></td></tr>
    300       <tr><td><a name="diff0015" /></td></tr>
    301       <tr><td class="lineno" valign="top"></td><td class="lblock">   semantics.  The method token is case<span class="delete">-</span>sensitive because it might be</td><td> </td><td class="rblock">   semantics.  The method token is case<span class="insert"> </span>sensitive because it might be</td><td class="lineno" valign="top"></td></tr>
    302       <tr><td class="lineno" valign="top"></td><td class="left">   used as a gateway to object-based systems with case-sensitive method</td><td> </td><td class="right">   used as a gateway to object-based systems with case-sensitive method</td><td class="lineno" valign="top"></td></tr>
    303       <tr><td class="lineno" valign="top"></td><td class="left">   names.</td><td> </td><td class="right">   names.</td><td class="lineno" valign="top"></td></tr>
    304       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    305       <tr><td class="lineno" valign="top"></td><td class="left">   Unlike distributed objects, the standardized request methods in HTTP</td><td> </td><td class="right">   Unlike distributed objects, the standardized request methods in HTTP</td><td class="lineno" valign="top"></td></tr>
    306       <tr><td><a name="diff0016" /></td></tr>
    307       <tr><td class="lineno" valign="top"></td><td class="lblock">   are not resource<span class="delete">-</span>specific, since uniform interfaces provide for</td><td> </td><td class="rblock">   are not resource<span class="insert"> </span>specific, since uniform interfaces provide for</td><td class="lineno" valign="top"></td></tr>
    308       <tr><td class="lineno" valign="top"></td><td class="left">   better visibility and reuse in network-based systems [REST].  Once</td><td> </td><td class="right">   better visibility and reuse in network-based systems [REST].  Once</td><td class="lineno" valign="top"></td></tr>
    309       <tr><td class="lineno" valign="top"></td><td class="left">   defined, a standardized method ought to have the same semantics when</td><td> </td><td class="right">   defined, a standardized method ought to have the same semantics when</td><td class="lineno" valign="top"></td></tr>
    310       <tr><td class="lineno" valign="top"></td><td class="left">   applied to any resource, though each resource determines for itself</td><td> </td><td class="right">   applied to any resource, though each resource determines for itself</td><td class="lineno" valign="top"></td></tr>
    311       <tr><td class="lineno" valign="top"></td><td class="left">   whether those semantics are implemented or allowed.</td><td> </td><td class="right">   whether those semantics are implemented or allowed.</td><td class="lineno" valign="top"></td></tr>
    312       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    313       <tr><td class="lineno" valign="top"></td><td class="left">   This specification defines a number of standardized methods that are</td><td> </td><td class="right">   This specification defines a number of standardized methods that are</td><td class="lineno" valign="top"></td></tr>
    314       <tr><td class="lineno" valign="top"></td><td class="left">   commonly used in HTTP, as outlined by the following table.  By</td><td> </td><td class="right">   commonly used in HTTP, as outlined by the following table.  By</td><td class="lineno" valign="top"></td></tr>
    315       <tr><td><a name="diff0017" /></td></tr>
    316       <tr><td class="lineno" valign="top"></td><td class="lblock">   convention, standardized methods are defined in all-uppercase <span class="delete">US-</span></td><td> </td><td class="rblock">   convention, standardized methods are defined in all-uppercase ASCII</td><td class="lineno" valign="top"></td></tr>
    317       <tr><td class="lineno" valign="top"></td><td class="lblock">   ASCII letters.</td><td> </td><td class="rblock">   letters.</td><td class="lineno" valign="top"></td></tr>
    318       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    319       <tr><td class="lineno" valign="top"></td><td class="left">   +---------+-------------------------------------------------+-------+</td><td> </td><td class="right">   +---------+-------------------------------------------------+-------+</td><td class="lineno" valign="top"></td></tr>
    320       <tr><td class="lineno" valign="top"></td><td class="left">   | Method  | Description                                     | Sec.  |</td><td> </td><td class="right">   | Method  | Description                                     | Sec.  |</td><td class="lineno" valign="top"></td></tr>
    321       <tr><td class="lineno" valign="top"></td><td class="left">   +---------+-------------------------------------------------+-------+</td><td> </td><td class="right">   +---------+-------------------------------------------------+-------+</td><td class="lineno" valign="top"></td></tr>
    322       <tr><td class="lineno" valign="top"></td><td class="left">   | GET     | Transfer a current representation of the target | 4.3.1 |</td><td> </td><td class="right">   | GET     | Transfer a current representation of the target | 4.3.1 |</td><td class="lineno" valign="top"></td></tr>
    323       <tr><td class="lineno" valign="top"></td><td class="left">   |         | resource.                                       |       |</td><td> </td><td class="right">   |         | resource.                                       |       |</td><td class="lineno" valign="top"></td></tr>
    324       <tr><td class="lineno" valign="top"></td><td class="left">   | HEAD    | Same as GET, but only transfer the status line  | 4.3.2 |</td><td> </td><td class="right">   | HEAD    | Same as GET, but only transfer the status line  | 4.3.2 |</td><td class="lineno" valign="top"></td></tr>
    325       <tr><td class="lineno" valign="top"></td><td class="left">   |         | and header section.                             |       |</td><td> </td><td class="right">   |         | and header section.                             |       |</td><td class="lineno" valign="top"></td></tr>
    326       <tr><td class="lineno" valign="top"></td><td class="left">   | POST    | Perform resource-specific processing on the     | 4.3.3 |</td><td> </td><td class="right">   | POST    | Perform resource-specific processing on the     | 4.3.3 |</td><td class="lineno" valign="top"></td></tr>
    327       <tr><td class="lineno" valign="top"></td><td class="left">   |         | request payload.                                |       |</td><td> </td><td class="right">   |         | request payload.                                |       |</td><td class="lineno" valign="top"></td></tr>
    328       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    329       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>
    330       <tr><td class="lineno" valign="top"></td><td class="left">   |         | target resource.                                |       |</td><td> </td><td class="right">   |         | target resource.                                |       |</td><td class="lineno" valign="top"></td></tr>
    331       <tr><td class="lineno" valign="top"></td><td class="left">   | TRACE   | Perform a message loop-back test along the path | 4.3.8 |</td><td> </td><td class="right">   | TRACE   | Perform a message loop-back test along the path | 4.3.8 |</td><td class="lineno" valign="top"></td></tr>
    332       <tr><td class="lineno" valign="top"></td><td class="left">   |         | to the target resource.                         |       |</td><td> </td><td class="right">   |         | to the target resource.                         |       |</td><td class="lineno" valign="top"></td></tr>
    333       <tr><td class="lineno" valign="top"></td><td class="left">   +---------+-------------------------------------------------+-------+</td><td> </td><td class="right">   +---------+-------------------------------------------------+-------+</td><td class="lineno" valign="top"></td></tr>
    334       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    335       <tr><td class="lineno" valign="top"></td><td class="left">   All general-purpose servers MUST support the methods GET and HEAD.</td><td> </td><td class="right">   All general-purpose servers MUST support the methods GET and HEAD.</td><td class="lineno" valign="top"></td></tr>
    336       <tr><td class="lineno" valign="top"></td><td class="left">   All other methods are OPTIONAL.</td><td> </td><td class="right">   All other methods are OPTIONAL.</td><td class="lineno" valign="top"></td></tr>
    337       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    338       <tr><td class="lineno" valign="top"></td><td class="left">   Additional methods, outside the scope of this specification, have</td><td> </td><td class="right">   Additional methods, outside the scope of this specification, have</td><td class="lineno" valign="top"></td></tr>
    339       <tr><td class="lineno" valign="top"></td><td class="left">   been standardized for use in HTTP.  All such methods ought to be</td><td> </td><td class="right">   been standardized for use in HTTP.  All such methods ought to be</td><td class="lineno" valign="top"></td></tr>
    340       <tr><td><a name="diff0018" /></td></tr>
    341       <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="delete">Method</span></td><td> </td><td class="rblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="insert">Method"</span></td><td class="lineno" valign="top"></td></tr>
    342       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry"</span> maintained by IANA, as defined in Section 8.1.</td><td> </td><td class="rblock"><span class="insert">   registry</span> maintained by IANA, as defined in Section 8.1.</td><td class="lineno" valign="top"></td></tr>
    343       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    344       <tr><td class="lineno" valign="top"></td><td class="left">   The set of methods allowed by a target resource can be listed in an</td><td> </td><td class="right">   The set of methods allowed by a target resource can be listed in an</td><td class="lineno" valign="top"></td></tr>
    345       <tr><td class="lineno" valign="top"></td><td class="left">   Allow header field (Section 7.4.1).  However, the set of allowed</td><td> </td><td class="right">   Allow header field (Section 7.4.1).  However, the set of allowed</td><td class="lineno" valign="top"></td></tr>
    346       <tr><td class="lineno" valign="top"></td><td class="left">   methods can change dynamically.  When a request method is received</td><td> </td><td class="right">   methods can change dynamically.  When a request method is received</td><td class="lineno" valign="top"></td></tr>
    347       <tr><td class="lineno" valign="top"></td><td class="left">   that is unrecognized or not implemented by an origin server, the</td><td> </td><td class="right">   that is unrecognized or not implemented by an origin server, the</td><td class="lineno" valign="top"></td></tr>
    348       <tr><td class="lineno" valign="top"></td><td class="left">   origin server SHOULD respond with the 501 (Not Implemented) status</td><td> </td><td class="right">   origin server SHOULD respond with the 501 (Not Implemented) status</td><td class="lineno" valign="top"></td></tr>
    349       <tr><td class="lineno" valign="top"></td><td class="left">   code.  When a request method is received that is known by an origin</td><td> </td><td class="right">   code.  When a request method is received that is known by an origin</td><td class="lineno" valign="top"></td></tr>
    350       <tr><td class="lineno" valign="top"></td><td class="left">   server but not allowed for the target resource, the origin server</td><td> </td><td class="right">   server but not allowed for the target resource, the origin server</td><td class="lineno" valign="top"></td></tr>
    351       <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD respond with the 405 (Method Not Allowed) status code.</td><td> </td><td class="right">   SHOULD respond with the 405 (Method Not Allowed) status code.</td><td class="lineno" valign="top"></td></tr>
    352       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    353       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    354       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>
    355       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    356       <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.  Safe Methods</td><td> </td><td class="right">4.2.1.  Safe Methods</td><td class="lineno" valign="top"></td></tr>
    357       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    358       <tr><td class="lineno" valign="top"></td><td class="left">   Request methods are considered "safe" if their defined semantics are</td><td> </td><td class="right">   Request methods are considered "safe" if their defined semantics are</td><td class="lineno" valign="top"></td></tr>
    359       <tr><td class="lineno" valign="top"></td><td class="left">   essentially read-only; i.e., the client does not request, and does</td><td> </td><td class="right">   essentially read-only; i.e., the client does not request, and does</td><td class="lineno" valign="top"></td></tr>
    360       <tr><td class="lineno" valign="top"></td><td class="left">   not expect, any state change on the origin server as a result of</td><td> </td><td class="right">   not expect, any state change on the origin server as a result of</td><td class="lineno" valign="top"></td></tr>
    361       <tr><td class="lineno" valign="top"></td><td class="left">   applying a safe method to a target resource.  Likewise, reasonable</td><td> </td><td class="right">   applying a safe method to a target resource.  Likewise, reasonable</td><td class="lineno" valign="top"></td></tr>
    362       <tr><td class="lineno" valign="top"></td><td class="left">   use of a safe method is not expected to cause any harm, loss of</td><td> </td><td class="right">   use of a safe method is not expected to cause any harm, loss of</td><td class="lineno" valign="top"></td></tr>
    363       <tr><td class="lineno" valign="top"></td><td class="left">   property, or unusual burden on the origin server.</td><td> </td><td class="right">   property, or unusual burden on the origin server.</td><td class="lineno" valign="top"></td></tr>
    364       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    365       <tr><td><a name="diff0019" /></td></tr>
    366       <tr><td class="lineno" valign="top"></td><td class="lblock">   This definition of safe method<span class="delete">s</span> does not prevent an implementation</td><td> </td><td class="rblock">   This definition of safe method does not prevent an implementation</td><td class="lineno" valign="top"></td></tr>
    367       <tr><td class="lineno" valign="top"></td><td class="left">   from including behavior that is potentially harmful, that is not</td><td> </td><td class="right">   from including behavior that is potentially harmful, that is not</td><td class="lineno" valign="top"></td></tr>
    368       <tr><td class="lineno" valign="top"></td><td class="left">   entirely read-only, or that causes side effects while invoking a safe</td><td> </td><td class="right">   entirely read-only, or that causes side effects while invoking a safe</td><td class="lineno" valign="top"></td></tr>
    369       <tr><td class="lineno" valign="top"></td><td class="left">   method.  What is important, however, is that the client did not</td><td> </td><td class="right">   method.  What is important, however, is that the client did not</td><td class="lineno" valign="top"></td></tr>
    370       <tr><td class="lineno" valign="top"></td><td class="left">   request that additional behavior and cannot be held accountable for</td><td> </td><td class="right">   request that additional behavior and cannot be held accountable for</td><td class="lineno" valign="top"></td></tr>
    371       <tr><td class="lineno" valign="top"></td><td class="left">   it.  For example, most servers append request information to access</td><td> </td><td class="right">   it.  For example, most servers append request information to access</td><td class="lineno" valign="top"></td></tr>
    372       <tr><td class="lineno" valign="top"></td><td class="left">   log files at the completion of every response, regardless of the</td><td> </td><td class="right">   log files at the completion of every response, regardless of the</td><td class="lineno" valign="top"></td></tr>
    373       <tr><td class="lineno" valign="top"></td><td class="left">   method, and that is considered safe even though the log storage might</td><td> </td><td class="right">   method, and that is considered safe even though the log storage might</td><td class="lineno" valign="top"></td></tr>
    374       <tr><td class="lineno" valign="top"></td><td class="left">   become full and crash the server.  Likewise, a safe request initiated</td><td> </td><td class="right">   become full and crash the server.  Likewise, a safe request initiated</td><td class="lineno" valign="top"></td></tr>
    375       <tr><td class="lineno" valign="top"></td><td class="left">   by selecting an advertisement on the Web will often have the side</td><td> </td><td class="right">   by selecting an advertisement on the Web will often have the side</td><td class="lineno" valign="top"></td></tr>
    376       <tr><td class="lineno" valign="top"></td><td class="left">   effect of charging an advertising account.</td><td> </td><td class="right">   effect of charging an advertising account.</td><td class="lineno" valign="top"></td></tr>
    377       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    378       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
    379       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    380       <tr><td class="lineno" valign="top"></td><td class="left">5.1.1.  Expect</td><td> </td><td class="right">5.1.1.  Expect</td><td class="lineno" valign="top"></td></tr>
    381       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    382       <tr><td class="lineno" valign="top"></td><td class="left">   The "Expect" header field in a request indicates a certain set of</td><td> </td><td class="right">   The "Expect" header field in a request indicates a certain set of</td><td class="lineno" valign="top"></td></tr>
    383       <tr><td class="lineno" valign="top"></td><td class="left">   behaviors (expectations) that need to be supported by the server in</td><td> </td><td class="right">   behaviors (expectations) that need to be supported by the server in</td><td class="lineno" valign="top"></td></tr>
    384       <tr><td class="lineno" valign="top"></td><td class="left">   order to properly handle this request.  The only such expectation</td><td> </td><td class="right">   order to properly handle this request.  The only such expectation</td><td class="lineno" valign="top"></td></tr>
    385       <tr><td class="lineno" valign="top"></td><td class="left">   defined by this specification is 100-continue.</td><td> </td><td class="right">   defined by this specification is 100-continue.</td><td class="lineno" valign="top"></td></tr>
    386       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    387       <tr><td class="lineno" valign="top"></td><td class="left">     Expect  = "100-continue"</td><td> </td><td class="right">     Expect  = "100-continue"</td><td class="lineno" valign="top"></td></tr>
    388       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    389       <tr><td><a name="diff0020" /></td></tr>
    390       <tr><td class="lineno" valign="top"></td><td class="lblock">   The Expect field-value is case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock">   The Expect field-value is case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr>
    391       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    392       <tr><td class="lineno" valign="top"></td><td class="left">   A server that receives an Expect field-value other than 100-continue</td><td> </td><td class="right">   A server that receives an Expect field-value other than 100-continue</td><td class="lineno" valign="top"></td></tr>
    393       <tr><td class="lineno" valign="top"></td><td class="left">   MAY respond with a 417 (Expectation Failed) status code to indicate</td><td> </td><td class="right">   MAY respond with a 417 (Expectation Failed) status code to indicate</td><td class="lineno" valign="top"></td></tr>
    394       <tr><td class="lineno" valign="top"></td><td class="left">   that the unexpected expectation cannot be met.</td><td> </td><td class="right">   that the unexpected expectation cannot be met.</td><td class="lineno" valign="top"></td></tr>
    395       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    396       <tr><td class="lineno" valign="top"></td><td class="left">   A 100-continue expectation informs recipients that the client is</td><td> </td><td class="right">   A 100-continue expectation informs recipients that the client is</td><td class="lineno" valign="top"></td></tr>
    397       <tr><td class="lineno" valign="top"></td><td class="left">   about to send a (presumably large) message body in this request and</td><td> </td><td class="right">   about to send a (presumably large) message body in this request and</td><td class="lineno" valign="top"></td></tr>
    398       <tr><td class="lineno" valign="top"></td><td class="left">   wishes to receive a 100 (Continue) interim response if the request-</td><td> </td><td class="right">   wishes to receive a 100 (Continue) interim response if the request-</td><td class="lineno" valign="top"></td></tr>
    399       <tr><td class="lineno" valign="top"></td><td class="left">   line and header fields are not sufficient to cause an immediate</td><td> </td><td class="right">   line and header fields are not sufficient to cause an immediate</td><td class="lineno" valign="top"></td></tr>
    400       <tr><td class="lineno" valign="top"></td><td class="left">   success, redirect, or error response.  This allows the client to wait</td><td> </td><td class="right">   success, redirect, or error response.  This allows the client to wait</td><td class="lineno" valign="top"></td></tr>
    401       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    402       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>
    403       <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+---------------+</td><td> </td><td class="right">   +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    404       <tr><td class="lineno" valign="top"></td><td class="left">   | From              | Section 5.5.1 |</td><td> </td><td class="right">   | From              | Section 5.5.1 |</td><td class="lineno" valign="top"></td></tr>
    405       <tr><td class="lineno" valign="top"></td><td class="left">   | Referer           | Section 5.5.2 |</td><td> </td><td class="right">   | Referer           | Section 5.5.2 |</td><td class="lineno" valign="top"></td></tr>
    406       <tr><td class="lineno" valign="top"></td><td class="left">   | User-Agent        | Section 5.5.3 |</td><td> </td><td class="right">   | User-Agent        | Section 5.5.3 |</td><td class="lineno" valign="top"></td></tr>
    407       <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+---------------+</td><td> </td><td class="right">   +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    408       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    409       <tr><td class="lineno" valign="top"></td><td class="left">5.5.1.  From</td><td> </td><td class="right">5.5.1.  From</td><td class="lineno" valign="top"></td></tr>
    410       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    411       <tr><td class="lineno" valign="top"></td><td class="left">   The "From" header field contains an Internet email address for a</td><td> </td><td class="right">   The "From" header field contains an Internet email address for a</td><td class="lineno" valign="top"></td></tr>
    412       <tr><td class="lineno" valign="top"></td><td class="left">   human user who controls the requesting user agent.  The address ought</td><td> </td><td class="right">   human user who controls the requesting user agent.  The address ought</td><td class="lineno" valign="top"></td></tr>
    413       <tr><td><a name="diff0021" /></td></tr>
    414       <tr><td class="lineno" valign="top"></td><td class="lblock">   to be machine<span class="delete">-</span>usable, as defined by "mailbox" in Section 3.4 of</td><td> </td><td class="rblock">   to be machine<span class="insert"> </span>usable, as defined by "mailbox" in Section 3.4 of</td><td class="lineno" valign="top"></td></tr>
    415       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5322]:</td><td> </td><td class="right">   [RFC5322]:</td><td class="lineno" valign="top"></td></tr>
    416       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    417       <tr><td class="lineno" valign="top"></td><td class="left">     From    = mailbox</td><td> </td><td class="right">     From    = mailbox</td><td class="lineno" valign="top"></td></tr>
    418       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    419       <tr><td class="lineno" valign="top"></td><td class="left">     mailbox = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;</td><td> </td><td class="right">     mailbox = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;</td><td class="lineno" valign="top"></td></tr>
    420       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    421       <tr><td class="lineno" valign="top"></td><td class="left">   An example is:</td><td> </td><td class="right">   An example is:</td><td class="lineno" valign="top"></td></tr>
    422       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    423       <tr><td class="lineno" valign="top"></td><td class="left">     From: webmaster@example.org</td><td> </td><td class="right">     From: webmaster@example.org</td><td class="lineno" valign="top"></td></tr>
    424       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    425       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    426       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 45, line 32</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 45, line 32</em></th><td></td></tr>
    427       <tr><td class="lineno" valign="top"></td><td class="left">   restricting cross-site request forgery (CSRF), but not all requests</td><td> </td><td class="right">   restricting cross-site request forgery (CSRF), but not all requests</td><td class="lineno" valign="top"></td></tr>
    428       <tr><td class="lineno" valign="top"></td><td class="left">   contain it.</td><td> </td><td class="right">   contain it.</td><td class="lineno" valign="top"></td></tr>
    429       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    430       <tr><td class="lineno" valign="top"></td><td class="left">   Example:</td><td> </td><td class="right">   Example:</td><td class="lineno" valign="top"></td></tr>
    431       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    432       <tr><td class="lineno" valign="top"></td><td class="left">     Referer: http://www.example.org/hypertext/Overview.html</td><td> </td><td class="right">     Referer: http://www.example.org/hypertext/Overview.html</td><td class="lineno" valign="top"></td></tr>
    433       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    434       <tr><td class="lineno" valign="top"></td><td class="left">   If the target URI was obtained from a source that does not have its</td><td> </td><td class="right">   If the target URI was obtained from a source that does not have its</td><td class="lineno" valign="top"></td></tr>
    435       <tr><td class="lineno" valign="top"></td><td class="left">   own URI (e.g., input from the user keyboard, or an entry within the</td><td> </td><td class="right">   own URI (e.g., input from the user keyboard, or an entry within the</td><td class="lineno" valign="top"></td></tr>
    436       <tr><td class="lineno" valign="top"></td><td class="left">   user's bookmarks/favorites), the user agent MUST either exclude the</td><td> </td><td class="right">   user's bookmarks/favorites), the user agent MUST either exclude the</td><td class="lineno" valign="top"></td></tr>
    437       <tr><td><a name="diff0022" /></td></tr>
    438       <tr><td class="lineno" valign="top"></td><td class="lblock">   Referer <span class="delete">field </span>or send it with a value of "about:blank".</td><td> </td><td class="rblock">   Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr>
    439       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    440       <tr><td class="lineno" valign="top"></td><td class="left">   The Referer field has the potential to reveal information about the</td><td> </td><td class="right">   The Referer field has the potential to reveal information about the</td><td class="lineno" valign="top"></td></tr>
    441       <tr><td class="lineno" valign="top"></td><td class="left">   request context or browsing history of the user, which is a privacy</td><td> </td><td class="right">   request context or browsing history of the user, which is a privacy</td><td class="lineno" valign="top"></td></tr>
    442       <tr><td class="lineno" valign="top"></td><td class="left">   concern if the referring resource's identifier reveals personal</td><td> </td><td class="right">   concern if the referring resource's identifier reveals personal</td><td class="lineno" valign="top"></td></tr>
    443       <tr><td class="lineno" valign="top"></td><td class="left">   information (such as an account name) or a resource that is supposed</td><td> </td><td class="right">   information (such as an account name) or a resource that is supposed</td><td class="lineno" valign="top"></td></tr>
    444       <tr><td class="lineno" valign="top"></td><td class="left">   to be confidential (such as behind a firewall or internal to a</td><td> </td><td class="right">   to be confidential (such as behind a firewall or internal to a</td><td class="lineno" valign="top"></td></tr>
    445       <tr><td class="lineno" valign="top"></td><td class="left">   secured service).  Most general-purpose user agents do not send the</td><td> </td><td class="right">   secured service).  Most general-purpose user agents do not send the</td><td class="lineno" valign="top"></td></tr>
    446       <tr><td class="lineno" valign="top"></td><td class="left">   Referer header field when the referring resource is a local "file" or</td><td> </td><td class="right">   Referer header field when the referring resource is a local "file" or</td><td class="lineno" valign="top"></td></tr>
    447       <tr><td class="lineno" valign="top"></td><td class="left">   "data" URI.  A user agent MUST NOT send a Referer header field in an</td><td> </td><td class="right">   "data" URI.  A user agent MUST NOT send a Referer header field in an</td><td class="lineno" valign="top"></td></tr>
    448       <tr><td class="lineno" valign="top"></td><td class="left">   unsecured HTTP request if the referring page was received with a</td><td> </td><td class="right">   unsecured HTTP request if the referring page was received with a</td><td class="lineno" valign="top"></td></tr>
    449       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    450       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 46, line 15</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 46, line 15</em></th><td></td></tr>
    451       <tr><td class="lineno" valign="top"></td><td class="left">   pseudonyms or truncating the query and/or path components.  An</td><td> </td><td class="right">   pseudonyms or truncating the query and/or path components.  An</td><td class="lineno" valign="top"></td></tr>
    452       <tr><td class="lineno" valign="top"></td><td class="left">   intermediary SHOULD NOT modify or delete the Referer header field</td><td> </td><td class="right">   intermediary SHOULD NOT modify or delete the Referer header field</td><td class="lineno" valign="top"></td></tr>
    453       <tr><td class="lineno" valign="top"></td><td class="left">   when the field value shares the same scheme and host as the request</td><td> </td><td class="right">   when the field value shares the same scheme and host as the request</td><td class="lineno" valign="top"></td></tr>
    454       <tr><td class="lineno" valign="top"></td><td class="left">   target.</td><td> </td><td class="right">   target.</td><td class="lineno" valign="top"></td></tr>
    455       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    456       <tr><td class="lineno" valign="top"></td><td class="left">5.5.3.  User-Agent</td><td> </td><td class="right">5.5.3.  User-Agent</td><td class="lineno" valign="top"></td></tr>
    457       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    458       <tr><td class="lineno" valign="top"></td><td class="left">   The "User-Agent" header field contains information about the user</td><td> </td><td class="right">   The "User-Agent" header field contains information about the user</td><td class="lineno" valign="top"></td></tr>
    459       <tr><td class="lineno" valign="top"></td><td class="left">   agent originating the request, which is often used by servers to help</td><td> </td><td class="right">   agent originating the request, which is often used by servers to help</td><td class="lineno" valign="top"></td></tr>
    460       <tr><td class="lineno" valign="top"></td><td class="left">   identify the scope of reported interoperability problems, to work</td><td> </td><td class="right">   identify the scope of reported interoperability problems, to work</td><td class="lineno" valign="top"></td></tr>
    461       <tr><td><a name="diff0023" /></td></tr>
    462       <tr><td class="lineno" valign="top"></td><td class="lblock">   around or tailor responses to avoid particular user<span class="delete"> </span>agent</td><td> </td><td class="rblock">   around or tailor responses to avoid particular user<span class="insert">-</span>agent</td><td class="lineno" valign="top"></td></tr>
    463       <tr><td class="lineno" valign="top"></td><td class="left">   limitations, and for analytics regarding browser or operating system</td><td> </td><td class="right">   limitations, and for analytics regarding browser or operating system</td><td class="lineno" valign="top"></td></tr>
    464       <tr><td class="lineno" valign="top"></td><td class="left">   use.  A user agent SHOULD send a User-Agent field in each request</td><td> </td><td class="right">   use.  A user agent SHOULD send a User-Agent field in each request</td><td class="lineno" valign="top"></td></tr>
    465       <tr><td class="lineno" valign="top"></td><td class="left">   unless specifically configured not to do so.</td><td> </td><td class="right">   unless specifically configured not to do so.</td><td class="lineno" valign="top"></td></tr>
    466       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    467       <tr><td class="lineno" valign="top"></td><td class="left">     User-Agent = product *( RWS ( product / comment ) )</td><td> </td><td class="right">     User-Agent = product *( RWS ( product / comment ) )</td><td class="lineno" valign="top"></td></tr>
    468       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    469       <tr><td class="lineno" valign="top"></td><td class="left">   The User-Agent field-value consists of one or more product</td><td> </td><td class="right">   The User-Agent field-value consists of one or more product</td><td class="lineno" valign="top"></td></tr>
    470       <tr><td class="lineno" valign="top"></td><td class="left">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td> </td><td class="right">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td class="lineno" valign="top"></td></tr>
    471       <tr><td><a name="diff0024" /></td></tr>
    472       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230]), which together identify the user<span class="delete"> </span>agent software and its</td><td> </td><td class="rblock">   [RFC7230]), which together identify the user<span class="insert">-</span>agent software and its</td><td class="lineno" valign="top"></td></tr>
    473       <tr><td class="lineno" valign="top"></td><td class="left">   significant subproducts.  By convention, the product identifiers are</td><td> </td><td class="right">   significant subproducts.  By convention, the product identifiers are</td><td class="lineno" valign="top"></td></tr>
    474       <tr><td class="lineno" valign="top"></td><td class="left">   listed in decreasing order of their significance for identifying the</td><td> </td><td class="right">   listed in decreasing order of their significance for identifying the</td><td class="lineno" valign="top"></td></tr>
    475       <tr><td><a name="diff0025" /></td></tr>
    476       <tr><td class="lineno" valign="top"></td><td class="lblock">   user<span class="delete"> </span>agent software.  Each product identifier consists of a name and</td><td> </td><td class="rblock">   user<span class="insert">-</span>agent software.  Each product identifier consists of a name and</td><td class="lineno" valign="top"></td></tr>
    477       <tr><td class="lineno" valign="top"></td><td class="left">   optional version.</td><td> </td><td class="right">   optional version.</td><td class="lineno" valign="top"></td></tr>
    478       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    479       <tr><td class="lineno" valign="top"></td><td class="left">     product         = token ["/" product-version]</td><td> </td><td class="right">     product         = token ["/" product-version]</td><td class="lineno" valign="top"></td></tr>
    480       <tr><td class="lineno" valign="top"></td><td class="left">     product-version = token</td><td> </td><td class="right">     product-version = token</td><td class="lineno" valign="top"></td></tr>
    481       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    482       <tr><td class="lineno" valign="top"></td><td class="left">   A sender SHOULD limit generated product identifiers to what is</td><td> </td><td class="right">   A sender SHOULD limit generated product identifiers to what is</td><td class="lineno" valign="top"></td></tr>
    483       <tr><td class="lineno" valign="top"></td><td class="left">   necessary to identify the product; a sender MUST NOT generate</td><td> </td><td class="right">   necessary to identify the product; a sender MUST NOT generate</td><td class="lineno" valign="top"></td></tr>
    484       <tr><td class="lineno" valign="top"></td><td class="left">   advertising or other nonessential information within the product</td><td> </td><td class="right">   advertising or other nonessential information within the product</td><td class="lineno" valign="top"></td></tr>
    485       <tr><td class="lineno" valign="top"></td><td class="left">   identifier.  A sender SHOULD NOT generate information in product-</td><td> </td><td class="right">   identifier.  A sender SHOULD NOT generate information in product-</td><td class="lineno" valign="top"></td></tr>
    486       <tr><td class="lineno" valign="top"></td><td class="left">   version that is not a version identifier (i.e., successive versions</td><td> </td><td class="right">   version that is not a version identifier (i.e., successive versions</td><td class="lineno" valign="top"></td></tr>
    487       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    488       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 47, line 9</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 47, line 9</em></th><td></td></tr>
    489       <tr><td class="lineno" valign="top"></td><td class="left">   subproducts by third parties.  Overly long and detailed User-Agent</td><td> </td><td class="right">   subproducts by third parties.  Overly long and detailed User-Agent</td><td class="lineno" valign="top"></td></tr>
    490       <tr><td class="lineno" valign="top"></td><td class="left">   field values increase request latency and the risk of a user being</td><td> </td><td class="right">   field values increase request latency and the risk of a user being</td><td class="lineno" valign="top"></td></tr>
    491       <tr><td class="lineno" valign="top"></td><td class="left">   identified against their wishes ("fingerprinting").</td><td> </td><td class="right">   identified against their wishes ("fingerprinting").</td><td class="lineno" valign="top"></td></tr>
    492       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    493       <tr><td class="lineno" valign="top"></td><td class="left">   Likewise, implementations are encouraged not to use the product</td><td> </td><td class="right">   Likewise, implementations are encouraged not to use the product</td><td class="lineno" valign="top"></td></tr>
    494       <tr><td class="lineno" valign="top"></td><td class="left">   tokens of other implementations in order to declare compatibility</td><td> </td><td class="right">   tokens of other implementations in order to declare compatibility</td><td class="lineno" valign="top"></td></tr>
    495       <tr><td class="lineno" valign="top"></td><td class="left">   with them, as this circumvents the purpose of the field.  If a user</td><td> </td><td class="right">   with them, as this circumvents the purpose of the field.  If a user</td><td class="lineno" valign="top"></td></tr>
    496       <tr><td class="lineno" valign="top"></td><td class="left">   agent masquerades as a different user agent, recipients can assume</td><td> </td><td class="right">   agent masquerades as a different user agent, recipients can assume</td><td class="lineno" valign="top"></td></tr>
    497       <tr><td class="lineno" valign="top"></td><td class="left">   that the user intentionally desires to see responses tailored for</td><td> </td><td class="right">   that the user intentionally desires to see responses tailored for</td><td class="lineno" valign="top"></td></tr>
    498       <tr><td class="lineno" valign="top"></td><td class="left">   that identified user agent, even if they might not work as well for</td><td> </td><td class="right">   that identified user agent, even if they might not work as well for</td><td class="lineno" valign="top"></td></tr>
    499       <tr><td><a name="diff0026" /></td></tr>
    500       <tr><td class="lineno" valign="top"></td><td class="lblock">   the actual user agent being <span class="delete">us</span>ed.</td><td> </td><td class="rblock">   the actual user agent being <span class="insert">implement</span>ed.</td><td class="lineno" valign="top"></td></tr>
    501       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    502       <tr><td class="lineno" valign="top"></td><td class="left">6.  Response Status Codes</td><td> </td><td class="right">6.  Response Status Codes</td><td class="lineno" valign="top"></td></tr>
    503       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    504       <tr><td class="lineno" valign="top"></td><td class="left">   The status-code element is a three-digit integer code giving the</td><td> </td><td class="right">   The status-code element is a three-digit integer code giving the</td><td class="lineno" valign="top"></td></tr>
    505       <tr><td class="lineno" valign="top"></td><td class="left">   result of the attempt to understand and satisfy the request.</td><td> </td><td class="right">   result of the attempt to understand and satisfy the request.</td><td class="lineno" valign="top"></td></tr>
    506       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    507       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP status codes are extensible.  HTTP clients are not required to</td><td> </td><td class="right">   HTTP status codes are extensible.  HTTP clients are not required to</td><td class="lineno" valign="top"></td></tr>
    508       <tr><td class="lineno" valign="top"></td><td class="left">   understand the meaning of all registered status codes, though such</td><td> </td><td class="right">   understand the meaning of all registered status codes, though such</td><td class="lineno" valign="top"></td></tr>
    509       <tr><td class="lineno" valign="top"></td><td class="left">   understanding is obviously desirable.  However, a client MUST</td><td> </td><td class="right">   understanding is obviously desirable.  However, a client MUST</td><td class="lineno" valign="top"></td></tr>
    510       <tr><td class="lineno" valign="top"></td><td class="left">   understand the class of any status code, as indicated by the first</td><td> </td><td class="right">   understand the class of any status code, as indicated by the first</td><td class="lineno" valign="top"></td></tr>
    511       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    512       <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
    513       <tr><td class="lineno" valign="top"></td><td class="left">   this specification because HTTP tries to remain orthogonal to the</td><td> </td><td class="right">   this specification because HTTP tries to remain orthogonal to the</td><td class="lineno" valign="top"></td></tr>
    514       <tr><td class="lineno" valign="top"></td><td class="left">   definition of its payloads.  In practice, the representation is</td><td> </td><td class="right">   definition of its payloads.  In practice, the representation is</td><td class="lineno" valign="top"></td></tr>
    515       <tr><td class="lineno" valign="top"></td><td class="left">   provided in some easily parsed format believed to be acceptable to</td><td> </td><td class="right">   provided in some easily parsed format believed to be acceptable to</td><td class="lineno" valign="top"></td></tr>
    516       <tr><td class="lineno" valign="top"></td><td class="left">   the user agent, as determined by shared design or content</td><td> </td><td class="right">   the user agent, as determined by shared design or content</td><td class="lineno" valign="top"></td></tr>
    517       <tr><td class="lineno" valign="top"></td><td class="left">   negotiation, or in some commonly accepted hypertext format.</td><td> </td><td class="right">   negotiation, or in some commonly accepted hypertext format.</td><td class="lineno" valign="top"></td></tr>
    518       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    519       <tr><td class="lineno" valign="top"></td><td class="left">   A 300 response is cacheable by default; i.e., unless otherwise</td><td> </td><td class="right">   A 300 response is cacheable by default; i.e., unless otherwise</td><td class="lineno" valign="top"></td></tr>
    520       <tr><td class="lineno" valign="top"></td><td class="left">   indicated by the method definition or explicit cache controls (see</td><td> </td><td class="right">   indicated by the method definition or explicit cache controls (see</td><td class="lineno" valign="top"></td></tr>
    521       <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.2.2 of [RFC7234]).</td><td> </td><td class="right">   Section 4.2.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
    522       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    523       <tr><td><a name="diff0027" /></td></tr>
    524       <tr><td class="lineno" valign="top"></td><td class="lblock">      Note: The original proposal for the 300 <span class="delete">status code</span> defined the</td><td> </td><td class="rblock">      Note: The original proposal for the 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr>
    525       <tr><td class="lineno" valign="top"></td><td class="lblock">      URI header field as providing a list of alternative</td><td> </td><td class="rblock">      header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr>
    526       <tr><td class="lineno" valign="top"></td><td class="lblock">      representations, such that it would be usable for 200, 300, and</td><td> </td><td class="rblock">      such that it would be usable for 200, 300, and 406 responses and</td><td class="lineno" valign="top"></td></tr>
    527       <tr><td class="lineno" valign="top"></td><td class="lblock">      406 responses and be transferred in responses to the HEAD method.</td><td> </td><td class="rblock">      be transferred in responses to the HEAD method.  However, lack of</td><td class="lineno" valign="top"></td></tr>
    528       <tr><td class="lineno" valign="top"></td><td class="lblock">      However, lack of deployment and disagreement over syntax led to</td><td> </td><td class="rblock">      deployment and disagreement over syntax led to both URI and</td><td class="lineno" valign="top"></td></tr>
    529       <tr><td class="lineno" valign="top"></td><td class="lblock">      both URI and Alternates (a subsequent proposal) being dropped from</td><td> </td><td class="rblock">      Alternates (a subsequent proposal) being dropped from this</td><td class="lineno" valign="top"></td></tr>
    530       <tr><td class="lineno" valign="top"></td><td class="lblock">      this specification.  It is possible to communicate the list using</td><td> </td><td class="rblock">      specification.  It is possible to communicate the list using a set</td><td class="lineno" valign="top"></td></tr>
    531       <tr><td class="lineno" valign="top"></td><td class="lblock">      a set of Link header fields [RFC5988], each with a relationship of</td><td> </td><td class="rblock">      of Link header fields [RFC5988], each with a relationship of</td><td class="lineno" valign="top"></td></tr>
    532       <tr><td class="lineno" valign="top"></td><td class="left">      "alternate", though deployment is a chicken-and-egg problem.</td><td> </td><td class="right">      "alternate", though deployment is a chicken-and-egg problem.</td><td class="lineno" valign="top"></td></tr>
    533       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    534       <tr><td class="lineno" valign="top"></td><td class="left">6.4.2.  301 Moved Permanently</td><td> </td><td class="right">6.4.2.  301 Moved Permanently</td><td class="lineno" valign="top"></td></tr>
    535       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    536       <tr><td class="lineno" valign="top"></td><td class="left">   The 301 (Moved Permanently) status code indicates that the target</td><td> </td><td class="right">   The 301 (Moved Permanently) status code indicates that the target</td><td class="lineno" valign="top"></td></tr>
    537       <tr><td class="lineno" valign="top"></td><td class="left">   resource has been assigned a new permanent URI and any future</td><td> </td><td class="right">   resource has been assigned a new permanent URI and any future</td><td class="lineno" valign="top"></td></tr>
    538       <tr><td class="lineno" valign="top"></td><td class="left">   references to this resource ought to use one of the enclosed URIs.</td><td> </td><td class="right">   references to this resource ought to use one of the enclosed URIs.</td><td class="lineno" valign="top"></td></tr>
    539       <tr><td class="lineno" valign="top"></td><td class="left">   Clients with link-editing capabilities ought to automatically re-link</td><td> </td><td class="right">   Clients with link-editing capabilities ought to automatically re-link</td><td class="lineno" valign="top"></td></tr>
    540       <tr><td class="lineno" valign="top"></td><td class="left">   references to the effective request URI to one or more of the new</td><td> </td><td class="right">   references to the effective request URI to one or more of the new</td><td class="lineno" valign="top"></td></tr>
    541       <tr><td class="lineno" valign="top"></td><td class="left">   references sent by the server, where possible.</td><td> </td><td class="right">   references sent by the server, where possible.</td><td class="lineno" valign="top"></td></tr>
    542       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    543       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
    544       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    545       <tr><td class="lineno" valign="top"></td><td class="left">   The server SHOULD generate a Location header field in the response</td><td> </td><td class="right">   The server SHOULD generate a Location header field in the response</td><td class="lineno" valign="top"></td></tr>
    546       <tr><td class="lineno" valign="top"></td><td class="left">   containing a URI reference for the different URI.  The user agent MAY</td><td> </td><td class="right">   containing a URI reference for the different URI.  The user agent MAY</td><td class="lineno" valign="top"></td></tr>
    547       <tr><td class="lineno" valign="top"></td><td class="left">   use the Location field value for automatic redirection.  The server's</td><td> </td><td class="right">   use the Location field value for automatic redirection.  The server's</td><td class="lineno" valign="top"></td></tr>
    548       <tr><td class="lineno" valign="top"></td><td class="left">   response payload usually contains a short hypertext note with a</td><td> </td><td class="right">   response payload usually contains a short hypertext note with a</td><td class="lineno" valign="top"></td></tr>
    549       <tr><td class="lineno" valign="top"></td><td class="left">   hyperlink to the different URI(s).</td><td> </td><td class="right">   hyperlink to the different URI(s).</td><td class="lineno" valign="top"></td></tr>
    550       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    551       <tr><td class="lineno" valign="top"></td><td class="left">      Note: This status code is similar to 302 (Found), except that it</td><td> </td><td class="right">      Note: This status code is similar to 302 (Found), except that it</td><td class="lineno" valign="top"></td></tr>
    552       <tr><td class="lineno" valign="top"></td><td class="left">      does not allow changing the request method from POST to GET.  This</td><td> </td><td class="right">      does not allow changing the request method from POST to GET.  This</td><td class="lineno" valign="top"></td></tr>
    553       <tr><td class="lineno" valign="top"></td><td class="left">      specification defines no equivalent counterpart for 301 (Moved</td><td> </td><td class="right">      specification defines no equivalent counterpart for 301 (Moved</td><td class="lineno" valign="top"></td></tr>
    554       <tr><td><a name="diff0028" /></td></tr>
    555       <tr><td class="lineno" valign="top"></td><td class="lblock">      Permanently) ([RFC7238]<span class="delete">, however,</span> defines the status code 308</td><td> </td><td class="rblock">      Permanently) ([RFC7238]<span class="insert">; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr>
    556       <tr><td class="lineno" valign="top"></td><td class="left">      (Permanent Redirect) for this purpose).</td><td> </td><td class="right">      (Permanent Redirect) for this purpose).</td><td class="lineno" valign="top"></td></tr>
    557       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    558       <tr><td class="lineno" valign="top"></td><td class="left">6.5.  Client Error 4xx</td><td> </td><td class="right">6.5.  Client Error 4xx</td><td class="lineno" valign="top"></td></tr>
    559       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    560       <tr><td class="lineno" valign="top"></td><td class="left">   The 4xx (Client Error) class of status code indicates that the client</td><td> </td><td class="right">   The 4xx (Client Error) class of status code indicates that the client</td><td class="lineno" valign="top"></td></tr>
    561       <tr><td class="lineno" valign="top"></td><td class="left">   seems to have erred.  Except when responding to a HEAD request, the</td><td> </td><td class="right">   seems to have erred.  Except when responding to a HEAD request, the</td><td class="lineno" valign="top"></td></tr>
    562       <tr><td class="lineno" valign="top"></td><td class="left">   server SHOULD send a representation containing an explanation of the</td><td> </td><td class="right">   server SHOULD send a representation containing an explanation of the</td><td class="lineno" valign="top"></td></tr>
    563       <tr><td class="lineno" valign="top"></td><td class="left">   error situation, and whether it is a temporary or permanent</td><td> </td><td class="right">   error situation, and whether it is a temporary or permanent</td><td class="lineno" valign="top"></td></tr>
    564       <tr><td class="lineno" valign="top"></td><td class="left">   condition.  These status codes are applicable to any request method.</td><td> </td><td class="right">   condition.  These status codes are applicable to any request method.</td><td class="lineno" valign="top"></td></tr>
    565       <tr><td class="lineno" valign="top"></td><td class="left">   User agents SHOULD display any included representation to the user.</td><td> </td><td class="right">   User agents SHOULD display any included representation to the user.</td><td class="lineno" valign="top"></td></tr>
    566       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    567       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 60, line 13</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 60, line 13</em></th><td></td></tr>
    568       <tr><td class="lineno" valign="top"></td><td class="left">   from which the user or user agent can choose the one most</td><td> </td><td class="right">   from which the user or user agent can choose the one most</td><td class="lineno" valign="top"></td></tr>
    569       <tr><td class="lineno" valign="top"></td><td class="left">   appropriate.  A user agent MAY automatically select the most</td><td> </td><td class="right">   appropriate.  A user agent MAY automatically select the most</td><td class="lineno" valign="top"></td></tr>
    570       <tr><td class="lineno" valign="top"></td><td class="left">   appropriate choice from that list.  However, this specification does</td><td> </td><td class="right">   appropriate choice from that list.  However, this specification does</td><td class="lineno" valign="top"></td></tr>
    571       <tr><td class="lineno" valign="top"></td><td class="left">   not define any standard for such automatic selection, as described in</td><td> </td><td class="right">   not define any standard for such automatic selection, as described in</td><td class="lineno" valign="top"></td></tr>
    572       <tr><td class="lineno" valign="top"></td><td class="left">   Section 6.4.1.</td><td> </td><td class="right">   Section 6.4.1.</td><td class="lineno" valign="top"></td></tr>
    573       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    574       <tr><td class="lineno" valign="top"></td><td class="left">6.5.7.  408 Request Timeout</td><td> </td><td class="right">6.5.7.  408 Request Timeout</td><td class="lineno" valign="top"></td></tr>
    575       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    576       <tr><td class="lineno" valign="top"></td><td class="left">   The 408 (Request Timeout) status code indicates that the server did</td><td> </td><td class="right">   The 408 (Request Timeout) status code indicates that the server did</td><td class="lineno" valign="top"></td></tr>
    577       <tr><td class="lineno" valign="top"></td><td class="left">   not receive a complete request message within the time that it was</td><td> </td><td class="right">   not receive a complete request message within the time that it was</td><td class="lineno" valign="top"></td></tr>
    578       <tr><td><a name="diff0029" /></td></tr>
    579       <tr><td class="lineno" valign="top"></td><td class="lblock">   prepared to wait.  A server SHOULD send the <span class="delete">"close"</span> connection option</td><td> </td><td class="rblock">   prepared to wait.  A server SHOULD send the <span class="insert">close</span> connection option</td><td class="lineno" valign="top"></td></tr>
    580       <tr><td class="lineno" valign="top"></td><td class="left">   (Section 6.1 of [RFC7230]) in the response, since 408 implies that</td><td> </td><td class="right">   (Section 6.1 of [RFC7230]) in the response, since 408 implies that</td><td class="lineno" valign="top"></td></tr>
    581       <tr><td class="lineno" valign="top"></td><td class="left">   the server has decided to close the connection rather than continue</td><td> </td><td class="right">   the server has decided to close the connection rather than continue</td><td class="lineno" valign="top"></td></tr>
    582       <tr><td class="lineno" valign="top"></td><td class="left">   waiting.  If the client has an outstanding request in transit, the</td><td> </td><td class="right">   waiting.  If the client has an outstanding request in transit, the</td><td class="lineno" valign="top"></td></tr>
    583       <tr><td class="lineno" valign="top"></td><td class="left">   client MAY repeat that request on a new connection.</td><td> </td><td class="right">   client MAY repeat that request on a new connection.</td><td class="lineno" valign="top"></td></tr>
    584       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    585       <tr><td class="lineno" valign="top"></td><td class="left">6.5.8.  409 Conflict</td><td> </td><td class="right">6.5.8.  409 Conflict</td><td class="lineno" valign="top"></td></tr>
    586       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    587       <tr><td class="lineno" valign="top"></td><td class="left">   The 409 (Conflict) status code indicates that the request could not</td><td> </td><td class="right">   The 409 (Conflict) status code indicates that the request could not</td><td class="lineno" valign="top"></td></tr>
    588       <tr><td class="lineno" valign="top"></td><td class="left">   be completed due to a conflict with the current state of the target</td><td> </td><td class="right">   be completed due to a conflict with the current state of the target</td><td class="lineno" valign="top"></td></tr>
    589       <tr><td class="lineno" valign="top"></td><td class="left">   resource.  This code is used in situations where the user might be</td><td> </td><td class="right">   resource.  This code is used in situations where the user might be</td><td class="lineno" valign="top"></td></tr>
    590       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    591       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr>
    592       <tr><td class="lineno" valign="top"></td><td class="left">   to be in UTC.  A sender that generates HTTP-date values from a local</td><td> </td><td class="right">   to be in UTC.  A sender that generates HTTP-date values from a local</td><td class="lineno" valign="top"></td></tr>
    593       <tr><td class="lineno" valign="top"></td><td class="left">   clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td> </td><td class="right">   clock ought to use NTP ([RFC5905]) or some similar protocol to</td><td class="lineno" valign="top"></td></tr>
    594       <tr><td class="lineno" valign="top"></td><td class="left">   synchronize its clock to UTC.</td><td> </td><td class="right">   synchronize its clock to UTC.</td><td class="lineno" valign="top"></td></tr>
    595       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    596       <tr><td class="lineno" valign="top"></td><td class="left">   Preferred format:</td><td> </td><td class="right">   Preferred format:</td><td class="lineno" valign="top"></td></tr>
    597       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    598       <tr><td class="lineno" valign="top"></td><td class="left">     IMF-fixdate  = day-name "," SP date1 SP time-of-day SP GMT</td><td> </td><td class="right">     IMF-fixdate  = day-name "," SP date1 SP time-of-day SP GMT</td><td class="lineno" valign="top"></td></tr>
    599       <tr><td class="lineno" valign="top"></td><td class="left">     ; fixed length/zone/capitalization subset of the format</td><td> </td><td class="right">     ; fixed length/zone/capitalization subset of the format</td><td class="lineno" valign="top"></td></tr>
    600       <tr><td class="lineno" valign="top"></td><td class="left">     ; defined in Section 3.3 of [RFC5322]</td><td> </td><td class="right">     ; defined in Section 3.3 of [RFC5322]</td><td class="lineno" valign="top"></td></tr>
    601       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    602       <tr><td><a name="diff0030" /></td></tr>
    603       <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    604       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x54.75.65 ; "Tue", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x54.75.65 ; "Tue", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    605       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x57.65.64 ; "Wed", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x57.65.64 ; "Wed", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    606       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x54.68.75 ; "Thu", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x54.68.75 ; "Thu", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    607       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x46.72.69 ; "Fri", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x46.72.69 ; "Fri", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    608       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x53.61.74 ; "Sat", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x53.61.74 ; "Sat", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    609       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x53.75.6E ; "Sun", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x53.75.6E ; "Sun", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    610       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    611       <tr><td class="lineno" valign="top"></td><td class="left">     date1        = day SP month SP year</td><td> </td><td class="right">     date1        = day SP month SP year</td><td class="lineno" valign="top"></td></tr>
    612       <tr><td class="lineno" valign="top"></td><td class="left">                  ; e.g., 02 Jun 1982</td><td> </td><td class="right">                  ; e.g., 02 Jun 1982</td><td class="lineno" valign="top"></td></tr>
    613       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    614       <tr><td class="lineno" valign="top"></td><td class="left">     day          = 2DIGIT</td><td> </td><td class="right">     day          = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    615       <tr><td><a name="diff0031" /></td></tr>
    616       <tr><td class="lineno" valign="top"></td><td class="lblock">     month        = %x4A.61.6E ; "Jan", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     month        = %x4A.61.6E ; "Jan", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    617       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x46.65.62 ; "Feb", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x46.65.62 ; "Feb", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    618       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4D.61.72 ; "Mar", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4D.61.72 ; "Mar", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    619       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x41.70.72 ; "Apr", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x41.70.72 ; "Apr", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    620       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4D.61.79 ; "May", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4D.61.79 ; "May", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    621       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4A.75.6E ; "Jun", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4A.75.6E ; "Jun", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    622       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4A.75.6C ; "Jul", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4A.75.6C ; "Jul", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    623       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x41.75.67 ; "Aug", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x41.75.67 ; "Aug", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    624       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x53.65.70 ; "Sep", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x53.65.70 ; "Sep", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    625       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4F.63.74 ; "Oct", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4F.63.74 ; "Oct", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    626       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x4E.6F.76 ; "Nov", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x4E.6F.76 ; "Nov", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    627       <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x44.65.63 ; "Dec", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x44.65.63 ; "Dec", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    628       <tr><td class="lineno" valign="top"></td><td class="left">     year         = 4DIGIT</td><td> </td><td class="right">     year         = 4DIGIT</td><td class="lineno" valign="top"></td></tr>
    629       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    630       <tr><td><a name="diff0032" /></td></tr>
    631       <tr><td class="lineno" valign="top"></td><td class="lblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr>
    632       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    633       <tr><td class="lineno" valign="top"></td><td class="left">     time-of-day  = hour ":" minute ":" second</td><td> </td><td class="right">     time-of-day  = hour ":" minute ":" second</td><td class="lineno" valign="top"></td></tr>
    634       <tr><td class="lineno" valign="top"></td><td class="left">                  ; 00:00:00 - 23:59:60 (leap second)</td><td> </td><td class="right">                  ; 00:00:00 - 23:59:60 (leap second)</td><td class="lineno" valign="top"></td></tr>
    635       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    636       <tr><td class="lineno" valign="top"></td><td class="left">     hour         = 2DIGIT</td><td> </td><td class="right">     hour         = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    637       <tr><td class="lineno" valign="top"></td><td class="left">     minute       = 2DIGIT</td><td> </td><td class="right">     minute       = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    638       <tr><td class="lineno" valign="top"></td><td class="left">     second       = 2DIGIT</td><td> </td><td class="right">     second       = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    639       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    640       <tr><td class="lineno" valign="top"></td><td class="left">   Obsolete formats:</td><td> </td><td class="right">   Obsolete formats:</td><td class="lineno" valign="top"></td></tr>
    641       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    642       <tr><td class="lineno" valign="top"></td><td class="left">     obs-date     = rfc850-date / asctime-date</td><td> </td><td class="right">     obs-date     = rfc850-date / asctime-date</td><td class="lineno" valign="top"></td></tr>
    643       <tr><td class="lineno" valign="top"></td><td class="left">     rfc850-date  = day-name-l "," SP date2 SP time-of-day SP GMT</td><td> </td><td class="right">     rfc850-date  = day-name-l "," SP date2 SP time-of-day SP GMT</td><td class="lineno" valign="top"></td></tr>
    644       <tr><td class="lineno" valign="top"></td><td class="left">     date2        = day "-" month "-" 2DIGIT</td><td> </td><td class="right">     date2        = day "-" month "-" 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    645       <tr><td class="lineno" valign="top"></td><td class="left">                  ; e.g., 02-Jun-82</td><td> </td><td class="right">                  ; e.g., 02-Jun-82</td><td class="lineno" valign="top"></td></tr>
    646       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    647       <tr><td><a name="diff0033" /></td></tr>
    648       <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    649       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    650       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    651       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x54.68.75.72.73.64.61.79    ; "Thursday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x54.68.75.72.73.64.61.79    ; "Thursday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    652       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x46.72.69.64.61.79          ; "Friday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x46.72.69.64.61.79          ; "Friday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    653       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x53.61.74.75.72.64.61.79    ; "Saturday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x53.61.74.75.72.64.61.79    ; "Saturday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    654       <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x53.75.6E.64.61.79          ; "Sunday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x53.75.6E.64.61.79          ; "Sunday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    655       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    656       <tr><td class="lineno" valign="top"></td><td class="left">     asctime-date = day-name SP date3 SP time-of-day SP year</td><td> </td><td class="right">     asctime-date = day-name SP date3 SP time-of-day SP year</td><td class="lineno" valign="top"></td></tr>
    657       <tr><td class="lineno" valign="top"></td><td class="left">     date3        = month SP ( 2DIGIT / ( SP 1DIGIT ))</td><td> </td><td class="right">     date3        = month SP ( 2DIGIT / ( SP 1DIGIT ))</td><td class="lineno" valign="top"></td></tr>
    658       <tr><td class="lineno" valign="top"></td><td class="left">                  ; e.g., Jun  2</td><td> </td><td class="right">                  ; e.g., Jun  2</td><td class="lineno" valign="top"></td></tr>
    659       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    660       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP-date is case sensitive.  A sender MUST NOT generate additional</td><td> </td><td class="right">   HTTP-date is case sensitive.  A sender MUST NOT generate additional</td><td class="lineno" valign="top"></td></tr>
    661       <tr><td class="lineno" valign="top"></td><td class="left">   whitespace in an HTTP-date beyond that specifically included as SP in</td><td> </td><td class="right">   whitespace in an HTTP-date beyond that specifically included as SP in</td><td class="lineno" valign="top"></td></tr>
    662       <tr><td class="lineno" valign="top"></td><td class="left">   the grammar.  The semantics of day-name, day, month, year, and time-</td><td> </td><td class="right">   the grammar.  The semantics of day-name, day, month, year, and time-</td><td class="lineno" valign="top"></td></tr>
    663       <tr><td class="lineno" valign="top"></td><td class="left">   of-day are the same as those defined for the Internet Message Format</td><td> </td><td class="right">   of-day are the same as those defined for the Internet Message Format</td><td class="lineno" valign="top"></td></tr>
    664       <tr><td class="lineno" valign="top"></td><td class="left">   constructs with the corresponding name ([RFC5322], Section 3.3).</td><td> </td><td class="right">   constructs with the corresponding name ([RFC5322], Section 3.3).</td><td class="lineno" valign="top"></td></tr>
    665       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    666       <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr>
    667       <tr><td class="lineno" valign="top"></td><td class="left">     Retry-After: 120</td><td> </td><td class="right">     Retry-After: 120</td><td class="lineno" valign="top"></td></tr>
    668       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    669       <tr><td class="lineno" valign="top"></td><td class="left">   In the latter example, the delay is 2 minutes.</td><td> </td><td class="right">   In the latter example, the delay is 2 minutes.</td><td class="lineno" valign="top"></td></tr>
    670       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    671       <tr><td class="lineno" valign="top"></td><td class="left">7.1.4.  Vary</td><td> </td><td class="right">7.1.4.  Vary</td><td class="lineno" valign="top"></td></tr>
    672       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    673       <tr><td class="lineno" valign="top"></td><td class="left">   The "Vary" header field in a response describes what parts of a</td><td> </td><td class="right">   The "Vary" header field in a response describes what parts of a</td><td class="lineno" valign="top"></td></tr>
    674       <tr><td class="lineno" valign="top"></td><td class="left">   request message, aside from the method, Host header field, and</td><td> </td><td class="right">   request message, aside from the method, Host header field, and</td><td class="lineno" valign="top"></td></tr>
    675       <tr><td class="lineno" valign="top"></td><td class="left">   request target, might influence the origin server's process for</td><td> </td><td class="right">   request target, might influence the origin server's process for</td><td class="lineno" valign="top"></td></tr>
    676       <tr><td class="lineno" valign="top"></td><td class="left">   selecting and representing this response.  The value consists of</td><td> </td><td class="right">   selecting and representing this response.  The value consists of</td><td class="lineno" valign="top"></td></tr>
    677       <tr><td><a name="diff0034" /></td></tr>
    678       <tr><td class="lineno" valign="top"></td><td class="lblock">   either a single asterisk ("*") or a list of header field names (case<span class="delete">-</span></td><td> </td><td class="rblock">   either a single asterisk ("*") or a list of header field names (case</td><td class="lineno" valign="top"></td></tr>
    679       <tr><td class="lineno" valign="top"></td><td class="left">   insensitive).</td><td> </td><td class="right">   insensitive).</td><td class="lineno" valign="top"></td></tr>
    680       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    681       <tr><td class="lineno" valign="top"></td><td class="left">     Vary = "*" / 1#field-name</td><td> </td><td class="right">     Vary = "*" / 1#field-name</td><td class="lineno" valign="top"></td></tr>
    682       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    683       <tr><td class="lineno" valign="top"></td><td class="left">   A Vary field value of "*" signals that anything about the request</td><td> </td><td class="right">   A Vary field value of "*" signals that anything about the request</td><td class="lineno" valign="top"></td></tr>
    684       <tr><td class="lineno" valign="top"></td><td class="left">   might play a role in selecting the response representation, possibly</td><td> </td><td class="right">   might play a role in selecting the response representation, possibly</td><td class="lineno" valign="top"></td></tr>
    685       <tr><td class="lineno" valign="top"></td><td class="left">   including elements outside the message syntax (e.g., the client's</td><td> </td><td class="right">   including elements outside the message syntax (e.g., the client's</td><td class="lineno" valign="top"></td></tr>
    686       <tr><td class="lineno" valign="top"></td><td class="left">   network address).  A recipient will not be able to determine whether</td><td> </td><td class="right">   network address).  A recipient will not be able to determine whether</td><td class="lineno" valign="top"></td></tr>
    687       <tr><td class="lineno" valign="top"></td><td class="left">   this response is appropriate for a later request without forwarding</td><td> </td><td class="right">   this response is appropriate for a later request without forwarding</td><td class="lineno" valign="top"></td></tr>
    688       <tr><td class="lineno" valign="top"></td><td class="left">   the request to the origin server.  A proxy MUST NOT generate a Vary</td><td> </td><td class="right">   the request to the origin server.  A proxy MUST NOT generate a Vary</td><td class="lineno" valign="top"></td></tr>
    689       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    690       <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>
    691       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    692       <tr><td class="lineno" valign="top"></td><td class="left">   An origin server might send Vary with a list of fields for two</td><td> </td><td class="right">   An origin server might send Vary with a list of fields for two</td><td class="lineno" valign="top"></td></tr>
    693       <tr><td class="lineno" valign="top"></td><td class="left">   purposes:</td><td> </td><td class="right">   purposes:</td><td class="lineno" valign="top"></td></tr>
    694       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    695       <tr><td class="lineno" valign="top"></td><td class="left">   1.  To inform cache recipients that they MUST NOT use this response</td><td> </td><td class="right">   1.  To inform cache recipients that they MUST NOT use this response</td><td class="lineno" valign="top"></td></tr>
    696       <tr><td class="lineno" valign="top"></td><td class="left">       to satisfy a later request unless the later request has the same</td><td> </td><td class="right">       to satisfy a later request unless the later request has the same</td><td class="lineno" valign="top"></td></tr>
    697       <tr><td class="lineno" valign="top"></td><td class="left">       values for the listed fields as the original request (Section 4.1</td><td> </td><td class="right">       values for the listed fields as the original request (Section 4.1</td><td class="lineno" valign="top"></td></tr>
    698       <tr><td class="lineno" valign="top"></td><td class="left">       of [RFC7234]).  In other words, Vary expands the cache key</td><td> </td><td class="right">       of [RFC7234]).  In other words, Vary expands the cache key</td><td class="lineno" valign="top"></td></tr>
    699       <tr><td class="lineno" valign="top"></td><td class="left">       required to match a new request to the stored cache entry.</td><td> </td><td class="right">       required to match a new request to the stored cache entry.</td><td class="lineno" valign="top"></td></tr>
    700       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    701       <tr><td><a name="diff0035" /></td></tr>
    702       <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  To inform user<span class="delete"> </span>agent recipients that this response is subject to</td><td> </td><td class="rblock">   2.  To inform user<span class="insert">-</span>agent recipients that this response is subject to</td><td class="lineno" valign="top"></td></tr>
    703       <tr><td class="lineno" valign="top"></td><td class="left">       content negotiation (Section 5.3) and that a different</td><td> </td><td class="right">       content negotiation (Section 5.3) and that a different</td><td class="lineno" valign="top"></td></tr>
    704       <tr><td class="lineno" valign="top"></td><td class="left">       representation might be sent in a subsequent request if</td><td> </td><td class="right">       representation might be sent in a subsequent request if</td><td class="lineno" valign="top"></td></tr>
    705       <tr><td class="lineno" valign="top"></td><td class="left">       additional parameters are provided in the listed header fields</td><td> </td><td class="right">       additional parameters are provided in the listed header fields</td><td class="lineno" valign="top"></td></tr>
    706       <tr><td class="lineno" valign="top"></td><td class="left">       (proactive negotiation).</td><td> </td><td class="right">       (proactive negotiation).</td><td class="lineno" valign="top"></td></tr>
    707       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    708       <tr><td class="lineno" valign="top"></td><td class="left">   An origin server SHOULD send a Vary header field when its algorithm</td><td> </td><td class="right">   An origin server SHOULD send a Vary header field when its algorithm</td><td class="lineno" valign="top"></td></tr>
    709       <tr><td class="lineno" valign="top"></td><td class="left">   for selecting a representation varies based on aspects of the request</td><td> </td><td class="right">   for selecting a representation varies based on aspects of the request</td><td class="lineno" valign="top"></td></tr>
    710       <tr><td class="lineno" valign="top"></td><td class="left">   message other than the method and request target, unless the variance</td><td> </td><td class="right">   message other than the method and request target, unless the variance</td><td class="lineno" valign="top"></td></tr>
    711       <tr><td class="lineno" valign="top"></td><td class="left">   cannot be crossed or the origin server has been deliberately</td><td> </td><td class="right">   cannot be crossed or the origin server has been deliberately</td><td class="lineno" valign="top"></td></tr>
    712       <tr><td class="lineno" valign="top"></td><td class="left">   configured to prevent cache transparency.  For example, there is no</td><td> </td><td class="right">   configured to prevent cache transparency.  For example, there is no</td><td class="lineno" valign="top"></td></tr>
    713       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    714       <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 74, line 7</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 74, line 7</em></th><td></td></tr>
    715       <tr><td class="lineno" valign="top"></td><td class="left">   needlessly fine-grained detail and SHOULD limit the addition of</td><td> </td><td class="right">   needlessly fine-grained detail and SHOULD limit the addition of</td><td class="lineno" valign="top"></td></tr>
    716       <tr><td class="lineno" valign="top"></td><td class="left">   subproducts by third parties.  Overly long and detailed Server field</td><td> </td><td class="right">   subproducts by third parties.  Overly long and detailed Server field</td><td class="lineno" valign="top"></td></tr>
    717       <tr><td class="lineno" valign="top"></td><td class="left">   values increase response latency and potentially reveal internal</td><td> </td><td class="right">   values increase response latency and potentially reveal internal</td><td class="lineno" valign="top"></td></tr>
    718       <tr><td class="lineno" valign="top"></td><td class="left">   implementation details that might make it (slightly) easier for</td><td> </td><td class="right">   implementation details that might make it (slightly) easier for</td><td class="lineno" valign="top"></td></tr>
    719       <tr><td class="lineno" valign="top"></td><td class="left">   attackers to find and exploit known security holes.</td><td> </td><td class="right">   attackers to find and exploit known security holes.</td><td class="lineno" valign="top"></td></tr>
    720       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    721       <tr><td class="lineno" valign="top"></td><td class="left">8.  IANA Considerations</td><td> </td><td class="right">8.  IANA Considerations</td><td class="lineno" valign="top"></td></tr>
    722       <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Method Registry</td><td> </td><td class="right">8.1.  Method Registry</td><td class="lineno" valign="top"></td></tr>
    723       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    724       <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Method Registry" defines the</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Method Registry" defines the</td><td class="lineno" valign="top"></td></tr>
    725       <tr><td><a name="diff0036" /></td></tr>
    726       <tr><td class="lineno" valign="top"></td><td class="lblock">   namespace for the request method token (Section 4).  The <span class="delete">method</span></td><td> </td><td class="rblock">   namespace for the request method token (Section 4).  The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr>
    727       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   registry</span> has been created and is now maintained at</td><td> </td><td class="rblock"><span class="insert">   Registry"</span> has been created and is now maintained at</td><td class="lineno" valign="top"></td></tr>
    728       <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-methods&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-methods&gt;.</td><td class="lineno" valign="top"></td></tr>
    729       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    730       <tr><td class="lineno" valign="top"></td><td class="left">8.1.1.  Procedure</td><td> </td><td class="right">8.1.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    731       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    732       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP method registrations MUST include the following fields:</td><td> </td><td class="right">   HTTP method registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    733       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    734       <tr><td class="lineno" valign="top"></td><td class="left">   o  Method Name (see Section 4)</td><td> </td><td class="right">   o  Method Name (see Section 4)</td><td class="lineno" valign="top"></td></tr>
    735       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    736       <tr><td class="lineno" valign="top"></td><td class="left">   o  Safe ("yes" or "no", see Section 4.2.1)</td><td> </td><td class="right">   o  Safe ("yes" or "no", see Section 4.2.1)</td><td class="lineno" valign="top"></td></tr>
    737       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    738       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    739       <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 74, line 44</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 74, line 44</em></th><td></td></tr>
    740       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    741       <tr><td class="lineno" valign="top"></td><td class="left">   Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td> </td><td class="right">   Since message parsing (Section 3.3 of [RFC7230]) needs to be</td><td class="lineno" valign="top"></td></tr>
    742       <tr><td class="lineno" valign="top"></td><td class="left">   independent of method semantics (aside from responses to HEAD),</td><td> </td><td class="right">   independent of method semantics (aside from responses to HEAD),</td><td class="lineno" valign="top"></td></tr>
    743       <tr><td class="lineno" valign="top"></td><td class="left">   definitions of new methods cannot change the parsing algorithm or</td><td> </td><td class="right">   definitions of new methods cannot change the parsing algorithm or</td><td class="lineno" valign="top"></td></tr>
    744       <tr><td class="lineno" valign="top"></td><td class="left">   prohibit the presence of a message body on either the request or the</td><td> </td><td class="right">   prohibit the presence of a message body on either the request or the</td><td class="lineno" valign="top"></td></tr>
    745       <tr><td class="lineno" valign="top"></td><td class="left">   response message.  Definitions of new methods can specify that only a</td><td> </td><td class="right">   response message.  Definitions of new methods can specify that only a</td><td class="lineno" valign="top"></td></tr>
    746       <tr><td class="lineno" valign="top"></td><td class="left">   zero-length message body is allowed by requiring a Content-Length</td><td> </td><td class="right">   zero-length message body is allowed by requiring a Content-Length</td><td class="lineno" valign="top"></td></tr>
    747       <tr><td class="lineno" valign="top"></td><td class="left">   header field with a value of "0".</td><td> </td><td class="right">   header field with a value of "0".</td><td class="lineno" valign="top"></td></tr>
    748       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    749       <tr><td class="lineno" valign="top"></td><td class="left">   A new method definition needs to indicate whether it is safe</td><td> </td><td class="right">   A new method definition needs to indicate whether it is safe</td><td class="lineno" valign="top"></td></tr>
    750       <tr><td><a name="diff0037" /></td></tr>
    751       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 4.2.1), idempotent (Section 4.2.2), cacheable</td><td> </td><td class="rblock">   (Section 4.2.1), idempotent (Section 4.2.2), <span class="insert">or</span> cacheable</td><td class="lineno" valign="top"></td></tr>
    752       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.2.3),</span> what semantics are to be associated with the payload</td><td> </td><td class="rblock">   (Section <span class="insert">4.2.3).  It needs to indicate</span> what semantics are to be</td><td class="lineno" valign="top"></td></tr>
    753       <tr><td class="lineno" valign="top"></td><td class="lblock">   body if any is present in the request and what refinements the method</td><td> </td><td class="rblock">   associated with the payload body if any is present in the request and</td><td class="lineno" valign="top"></td></tr>
    754       <tr><td class="lineno" valign="top"></td><td class="lblock">   makes to header field or status code semantics.  If the new method is</td><td> </td><td class="rblock">   what refinements the method makes to header field or status code</td><td class="lineno" valign="top"></td></tr>
    755       <tr><td class="lineno" valign="top"></td><td class="lblock">   cacheable, its definition ought to describe how, and under what</td><td> </td><td class="rblock">   semantics.  If the new method is cacheable, its definition ought to</td><td class="lineno" valign="top"></td></tr>
    756       <tr><td class="lineno" valign="top"></td><td class="lblock">   conditions, a cache can store a response and use it to satisfy a</td><td> </td><td class="rblock">   describe how, and under what conditions, a cache can store a response</td><td class="lineno" valign="top"></td></tr>
    757       <tr><td class="lineno" valign="top"></td><td class="lblock">   subsequent request.  The new method ought to describe whether it can</td><td> </td><td class="rblock">   and use it to satisfy a subsequent request.  The new method ought to</td><td class="lineno" valign="top"></td></tr>
    758       <tr><td class="lineno" valign="top"></td><td class="lblock">   be made conditional (Section 5.2) and, if so, how a server responds</td><td> </td><td class="rblock">   describe whether it can be made conditional (Section 5.2) and, if so,</td><td class="lineno" valign="top"></td></tr>
    759       <tr><td class="lineno" valign="top"></td><td class="lblock">   when the condition is false.  Likewise, if the new method might have</td><td> </td><td class="rblock">   how a server responds when the condition is false.  Likewise, if the</td><td class="lineno" valign="top"></td></tr>
    760       <tr><td class="lineno" valign="top"></td><td class="lblock">   some use for partial response semantics ([RFC7233]), it ought to</td><td> </td><td class="rblock">   new method might have some use for partial response semantics</td><td class="lineno" valign="top"></td></tr>
    761       <tr><td class="lineno" valign="top"></td><td class="lblock">   document this, too.</td><td> </td><td class="rblock">   ([RFC7233]), it ought to document this, too.</td><td class="lineno" valign="top"></td></tr>
    762       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    763       <tr><td class="lineno" valign="top"></td><td class="left">      Note: Avoid defining a method name that starts with "M-", since</td><td> </td><td class="right">      Note: Avoid defining a method name that starts with "M-", since</td><td class="lineno" valign="top"></td></tr>
    764       <tr><td class="lineno" valign="top"></td><td class="left">      that prefix might be misinterpreted as having the semantics</td><td> </td><td class="right">      that prefix might be misinterpreted as having the semantics</td><td class="lineno" valign="top"></td></tr>
    765       <tr><td class="lineno" valign="top"></td><td class="left">      assigned to it by [RFC2774].</td><td> </td><td class="right">      assigned to it by [RFC2774].</td><td class="lineno" valign="top"></td></tr>
    766       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    767       <tr><td class="lineno" valign="top"></td><td class="left">8.1.3.  Registrations</td><td> </td><td class="right">8.1.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    768       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    769       <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Method Registry" has been</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Method Registry" has been</td><td class="lineno" valign="top"></td></tr>
    770       <tr><td class="lineno" valign="top"></td><td class="left">   populated with the registrations below:</td><td> </td><td class="right">   populated with the registrations below:</td><td class="lineno" valign="top"></td></tr>
    771       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    772       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    773       <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 75, line 34</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 75, line 34</em></th><td></td></tr>
    774       <tr><td class="lineno" valign="top"></td><td class="left">   | OPTIONS | yes  | yes        | Section 4.3.7 |</td><td> </td><td class="right">   | OPTIONS | yes  | yes        | Section 4.3.7 |</td><td class="lineno" valign="top"></td></tr>
    775       <tr><td class="lineno" valign="top"></td><td class="left">   | POST    | no   | no         | Section 4.3.3 |</td><td> </td><td class="right">   | POST    | no   | no         | Section 4.3.3 |</td><td class="lineno" valign="top"></td></tr>
    776       <tr><td class="lineno" valign="top"></td><td class="left">   | PUT     | no   | yes        | Section 4.3.4 |</td><td> </td><td class="right">   | PUT     | no   | yes        | Section 4.3.4 |</td><td class="lineno" valign="top"></td></tr>
    777       <tr><td class="lineno" valign="top"></td><td class="left">   | TRACE   | yes  | yes        | Section 4.3.8 |</td><td> </td><td class="right">   | TRACE   | yes  | yes        | Section 4.3.8 |</td><td class="lineno" valign="top"></td></tr>
    778       <tr><td class="lineno" valign="top"></td><td class="left">   +---------+------+------------+---------------+</td><td> </td><td class="right">   +---------+------+------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    779       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    780       <tr><td class="lineno" valign="top"></td><td class="left">8.2.  Status Code Registry</td><td> </td><td class="right">8.2.  Status Code Registry</td><td class="lineno" valign="top"></td></tr>
    781       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    782       <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" defines</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" defines</td><td class="lineno" valign="top"></td></tr>
    783       <tr><td class="lineno" valign="top"></td><td class="left">   the namespace for the response status-code token (Section 6).  The</td><td> </td><td class="right">   the namespace for the response status-code token (Section 6).  The</td><td class="lineno" valign="top"></td></tr>
    784       <tr><td><a name="diff0038" /></td></tr>
    785       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">status code</span> registry is maintained at</td><td> </td><td class="rblock">   <span class="insert">"HTTP Status Codes"</span> registry is maintained at</td><td class="lineno" valign="top"></td></tr>
    786       <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td class="lineno" valign="top"></td></tr>
    787       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    788       <tr><td class="lineno" valign="top"></td><td class="left">   This section replaces the registration procedure for HTTP Status</td><td> </td><td class="right">   This section replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr>
    789       <tr><td class="lineno" valign="top"></td><td class="left">   Codes previously defined in Section 7.1 of [RFC2817].</td><td> </td><td class="right">   Codes previously defined in Section 7.1 of [RFC2817].</td><td class="lineno" valign="top"></td></tr>
    790       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    791       <tr><td class="lineno" valign="top"></td><td class="left">8.2.1.  Procedure</td><td> </td><td class="right">8.2.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    792       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    793       <tr><td class="lineno" valign="top"></td><td class="left">   A registration MUST include the following fields:</td><td> </td><td class="right">   A registration MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    794       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    795       <tr><td class="lineno" valign="top"></td><td class="left">   o  Status Code (3 digits)</td><td> </td><td class="right">   o  Status Code (3 digits)</td><td class="lineno" valign="top"></td></tr>
    796       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    797       <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>
    798       <tr><td class="lineno" valign="top"></td><td class="left">   cached without explicit freshness information.  Likewise, the</td><td> </td><td class="right">   cached without explicit freshness information.  Likewise, the</td><td class="lineno" valign="top"></td></tr>
    799       <tr><td class="lineno" valign="top"></td><td class="left">   definition of a status code can place constraints upon cache</td><td> </td><td class="right">   definition of a status code can place constraints upon cache</td><td class="lineno" valign="top"></td></tr>
    800       <tr><td class="lineno" valign="top"></td><td class="left">   behavior.  See [RFC7234] for more information.</td><td> </td><td class="right">   behavior.  See [RFC7234] for more information.</td><td class="lineno" valign="top"></td></tr>
    801       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    802       <tr><td class="lineno" valign="top"></td><td class="left">   Finally, the definition of a new status code ought to indicate</td><td> </td><td class="right">   Finally, the definition of a new status code ought to indicate</td><td class="lineno" valign="top"></td></tr>
    803       <tr><td class="lineno" valign="top"></td><td class="left">   whether the payload has any implied association with an identified</td><td> </td><td class="right">   whether the payload has any implied association with an identified</td><td class="lineno" valign="top"></td></tr>
    804       <tr><td class="lineno" valign="top"></td><td class="left">   resource (Section 3.1.4.1).</td><td> </td><td class="right">   resource (Section 3.1.4.1).</td><td class="lineno" valign="top"></td></tr>
    805       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    806       <tr><td class="lineno" valign="top"></td><td class="left">8.2.3.  Registrations</td><td> </td><td class="right">8.2.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    807       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    808       <tr><td><a name="diff0039" /></td></tr>
    809       <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">status code</span> registry has been updated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Status Codes"</span> registry has been updated with the</td><td class="lineno" valign="top"></td></tr>
    810       <tr><td class="lineno" valign="top"></td><td class="lblock">   below:</td><td> </td><td class="rblock">   registrations below:</td><td class="lineno" valign="top"></td></tr>
    811       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    812       <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+----------------+</td><td> </td><td class="right">   +-------+-------------------------------+----------------+</td><td class="lineno" valign="top"></td></tr>
    813       <tr><td class="lineno" valign="top"></td><td class="left">   | Value | Description                   | Reference      |</td><td> </td><td class="right">   | Value | Description                   | Reference      |</td><td class="lineno" valign="top"></td></tr>
    814       <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+----------------+</td><td> </td><td class="right">   +-------+-------------------------------+----------------+</td><td class="lineno" valign="top"></td></tr>
    815       <tr><td class="lineno" valign="top"></td><td class="left">   | 100   | Continue                      | Section 6.2.1  |</td><td> </td><td class="right">   | 100   | Continue                      | Section 6.2.1  |</td><td class="lineno" valign="top"></td></tr>
    816       <tr><td class="lineno" valign="top"></td><td class="left">   | 101   | Switching Protocols           | Section 6.2.2  |</td><td> </td><td class="right">   | 101   | Switching Protocols           | Section 6.2.2  |</td><td class="lineno" valign="top"></td></tr>
    817       <tr><td class="lineno" valign="top"></td><td class="left">   | 200   | OK                            | Section 6.3.1  |</td><td> </td><td class="right">   | 200   | OK                            | Section 6.3.1  |</td><td class="lineno" valign="top"></td></tr>
    818       <tr><td class="lineno" valign="top"></td><td class="left">   | 201   | Created                       | Section 6.3.2  |</td><td> </td><td class="right">   | 201   | Created                       | Section 6.3.2  |</td><td class="lineno" valign="top"></td></tr>
    819       <tr><td class="lineno" valign="top"></td><td class="left">   | 202   | Accepted                      | Section 6.3.3  |</td><td> </td><td class="right">   | 202   | Accepted                      | Section 6.3.3  |</td><td class="lineno" valign="top"></td></tr>
    820       <tr><td class="lineno" valign="top"></td><td class="left">   | 203   | Non-Authoritative Information | Section 6.3.4  |</td><td> </td><td class="right">   | 203   | Non-Authoritative Information | Section 6.3.4  |</td><td class="lineno" valign="top"></td></tr>
    821       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    822       <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 77, line 49</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 77, line 49</em></th><td></td></tr>
    823       <tr><td class="lineno" valign="top"></td><td class="left">   | 501   | Not Implemented               | Section 6.6.2  |</td><td> </td><td class="right">   | 501   | Not Implemented               | Section 6.6.2  |</td><td class="lineno" valign="top"></td></tr>
    824       <tr><td class="lineno" valign="top"></td><td class="left">   | 502   | Bad Gateway                   | Section 6.6.3  |</td><td> </td><td class="right">   | 502   | Bad Gateway                   | Section 6.6.3  |</td><td class="lineno" valign="top"></td></tr>
    825       <tr><td class="lineno" valign="top"></td><td class="left">   | 503   | Service Unavailable           | Section 6.6.4  |</td><td> </td><td class="right">   | 503   | Service Unavailable           | Section 6.6.4  |</td><td class="lineno" valign="top"></td></tr>
    826       <tr><td class="lineno" valign="top"></td><td class="left">   | 504   | Gateway Timeout               | Section 6.6.5  |</td><td> </td><td class="right">   | 504   | Gateway Timeout               | Section 6.6.5  |</td><td class="lineno" valign="top"></td></tr>
    827       <tr><td class="lineno" valign="top"></td><td class="left">   | 505   | HTTP Version Not Supported    | Section 6.6.6  |</td><td> </td><td class="right">   | 505   | HTTP Version Not Supported    | Section 6.6.6  |</td><td class="lineno" valign="top"></td></tr>
    828       <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-------------------------------+----------------+</td><td> </td><td class="right">   +-------+-------------------------------+----------------+</td><td class="lineno" valign="top"></td></tr>
    829       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    830       <tr><td class="lineno" valign="top"></td><td class="left">8.3.  Header Field Registry</td><td> </td><td class="right">8.3.  Header Field Registry</td><td class="lineno" valign="top"></td></tr>
    831       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    832       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields are registered within the "Message Headers"</td><td> </td><td class="right">   HTTP header fields are registered within the "Message Headers"</td><td class="lineno" valign="top"></td></tr>
    833       <tr><td><a name="diff0040" /></td></tr>
    834       <tr><td class="lineno" valign="top"></td><td class="lblock">   registry located at</td><td> </td><td class="rblock">   registry located at <span class="insert">&lt;http://www.iana.org/assignments/message-headers&gt;</span></td><td class="lineno" valign="top"></td></tr>
    835       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">&lt;http://www.iana.org/assignments/message-headers&gt;,</span> as defined by</td><td> </td><td class="rblock">   as defined by [BCP90].</td><td class="lineno" valign="top"></td></tr>
    836       <tr><td class="lineno" valign="top"></td><td class="lblock">   [BCP90].</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    837       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    838       <tr><td class="lineno" valign="top"></td><td class="left">8.3.1.  Considerations for New Header Fields</td><td> </td><td class="right">8.3.1.  Considerations for New Header Fields</td><td class="lineno" valign="top"></td></tr>
    839       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    840       <tr><td class="lineno" valign="top"></td><td class="left">   Header fields are key:value pairs that can be used to communicate</td><td> </td><td class="right">   Header fields are key:value pairs that can be used to communicate</td><td class="lineno" valign="top"></td></tr>
    841       <tr><td class="lineno" valign="top"></td><td class="left">   data about the message, its payload, the target resource, or the</td><td> </td><td class="right">   data about the message, its payload, the target resource, or the</td><td class="lineno" valign="top"></td></tr>
    842       <tr><td class="lineno" valign="top"></td><td class="left">   connection (i.e., control data).  See Section 3.2 of [RFC7230] for a</td><td> </td><td class="right">   connection (i.e., control data).  See Section 3.2 of [RFC7230] for a</td><td class="lineno" valign="top"></td></tr>
    843       <tr><td class="lineno" valign="top"></td><td class="left">   general definition of header field syntax in HTTP messages.</td><td> </td><td class="right">   general definition of header field syntax in HTTP messages.</td><td class="lineno" valign="top"></td></tr>
    844       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    845       <tr><td class="lineno" valign="top"></td><td class="left">   The requirements for header field names are defined in [BCP90].</td><td> </td><td class="right">   The requirements for header field names are defined in [BCP90].</td><td class="lineno" valign="top"></td></tr>
    846       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    847       <tr><td class="lineno" valign="top"></td><td class="left">   Authors of specifications defining new fields are advised to keep the</td><td> </td><td class="right">   Authors of specifications defining new fields are advised to keep the</td><td class="lineno" valign="top"></td></tr>
    848       <tr><td class="lineno" valign="top"></td><td class="left">   name as short as practical and not to prefix the name with "X-"</td><td> </td><td class="right">   name as short as practical and not to prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr>
    849       <tr><td class="lineno" valign="top"></td><td class="left">   unless the header field will never be used on the Internet.  (The</td><td> </td><td class="right">   unless the header field will never be used on the Internet.  (The</td><td class="lineno" valign="top"></td></tr>
    850       <tr><td class="lineno" valign="top"></td><td class="left">   "X-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="right">   "X-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr>
    851       <tr><td class="lineno" valign="top"></td><td class="left">   intended to only be used as a mechanism for avoiding name collisions</td><td> </td><td class="right">   intended to only be used as a mechanism for avoiding name collisions</td><td class="lineno" valign="top"></td></tr>
    852       <tr><td class="lineno" valign="top"></td><td class="left">   inside proprietary software or intranet processing, since the prefix</td><td> </td><td class="right">   inside proprietary software or intranet processing, since the prefix</td><td class="lineno" valign="top"></td></tr>
    853       <tr><td class="lineno" valign="top"></td><td class="left">   would ensure that private names never collide with a newly registered</td><td> </td><td class="right">   would ensure that private names never collide with a newly registered</td><td class="lineno" valign="top"></td></tr>
    854       <tr><td class="lineno" valign="top"></td><td class="left">   Internet name; see [BCP178] for further information).</td><td> </td><td class="right">   Internet name; see [BCP178] for further information).</td><td class="lineno" valign="top"></td></tr>
    855       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    856       <tr><td class="lineno" valign="top"></td><td class="left">   New header field values typically have their syntax defined using</td><td> </td><td class="right">   New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr>
    857       <tr><td><a name="diff0041" /></td></tr>
    858       <tr><td class="lineno" valign="top"></td><td class="lblock">   ABNF <span class="delete">([RFC5234]), using</span> the extension defined in Section 7 of</td><td> </td><td class="rblock">   ABNF <span class="insert">([RFC5234]) (implementing</span> the extension defined in Section 7 of</td><td class="lineno" valign="top"></td></tr>
    859       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230] as <span class="delete">necessary,</span> and are usually constrained to the range of</td><td> </td><td class="rblock">   [RFC7230] as <span class="insert">necessary),</span> and <span class="insert">they</span> are usually constrained to the</td><td class="lineno" valign="top"></td></tr>
    860       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">US-ASCII</span> characters.  Header fields needing a greater range of</td><td> </td><td class="rblock">   range of <span class="insert">ASCII</span> characters.  Header fields needing a greater range of</td><td class="lineno" valign="top"></td></tr>
    861       <tr><td class="lineno" valign="top"></td><td class="left">   characters can use an encoding such as the one defined in [RFC5987].</td><td> </td><td class="right">   characters can use an encoding such as the one defined in [RFC5987].</td><td class="lineno" valign="top"></td></tr>
    862       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    863       <tr><td class="lineno" valign="top"></td><td class="left">   Leading and trailing whitespace in raw field values is removed upon</td><td> </td><td class="right">   Leading and trailing whitespace in raw field values is removed upon</td><td class="lineno" valign="top"></td></tr>
    864       <tr><td class="lineno" valign="top"></td><td class="left">   field parsing (Section 3.2.4 of [RFC7230]).  Field definitions where</td><td> </td><td class="right">   field parsing (Section 3.2.4 of [RFC7230]).  Field definitions where</td><td class="lineno" valign="top"></td></tr>
    865       <tr><td class="lineno" valign="top"></td><td class="left">   leading or trailing whitespace in values is significant will have to</td><td> </td><td class="right">   leading or trailing whitespace in values is significant will have to</td><td class="lineno" valign="top"></td></tr>
    866       <tr><td class="lineno" valign="top"></td><td class="left">   use a container syntax such as quoted-string (Section 3.2.6 of</td><td> </td><td class="right">   use a container syntax such as quoted-string (Section 3.2.6 of</td><td class="lineno" valign="top"></td></tr>
    867       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]).</td><td> </td><td class="right">   [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
    868       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    869       <tr><td class="lineno" valign="top"></td><td class="left">   Because commas (",") are used as a generic delimiter between field-</td><td> </td><td class="right">   Because commas (",") are used as a generic delimiter between field-</td><td class="lineno" valign="top"></td></tr>
    870       <tr><td class="lineno" valign="top"></td><td class="left">   values, they need to be treated with care if they are allowed in the</td><td> </td><td class="right">   values, they need to be treated with care if they are allowed in the</td><td class="lineno" valign="top"></td></tr>
    871       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    872       <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 80, line 49</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 80, line 49</em></th><td></td></tr>
    873       <tr><td class="lineno" valign="top"></td><td class="left">   | User-Agent        | http     | standard | Section 5.5.3   |</td><td> </td><td class="right">   | User-Agent        | http     | standard | Section 5.5.3   |</td><td class="lineno" valign="top"></td></tr>
    874       <tr><td class="lineno" valign="top"></td><td class="left">   | Vary              | http     | standard | Section 7.1.4   |</td><td> </td><td class="right">   | Vary              | http     | standard | Section 7.1.4   |</td><td class="lineno" valign="top"></td></tr>
    875       <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+-----------------+</td><td> </td><td class="right">   +-------------------+----------+----------+-----------------+</td><td class="lineno" valign="top"></td></tr>
    876       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    877       <tr><td class="lineno" valign="top"></td><td class="left">   The change controller for the above registrations is: "IETF</td><td> </td><td class="right">   The change controller for the above registrations is: "IETF</td><td class="lineno" valign="top"></td></tr>
    878       <tr><td class="lineno" valign="top"></td><td class="left">   (iesg@ietf.org) - Internet Engineering Task Force".</td><td> </td><td class="right">   (iesg@ietf.org) - Internet Engineering Task Force".</td><td class="lineno" valign="top"></td></tr>
    879       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    880       <tr><td class="lineno" valign="top"></td><td class="left">8.4.  Content Coding Registry</td><td> </td><td class="right">8.4.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
    881       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    882       <tr><td class="lineno" valign="top"></td><td class="left">   The "HTTP Content Coding Registry" defines the namespace for content</td><td> </td><td class="right">   The "HTTP Content Coding Registry" defines the namespace for content</td><td class="lineno" valign="top"></td></tr>
    883       <tr><td><a name="diff0042" /></td></tr>
    884       <tr><td class="lineno" valign="top"></td><td class="lblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="delete">content coding registry</span></td><td> </td><td class="rblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="insert">"HTTP Content Coding</span></td><td class="lineno" valign="top"></td></tr>
    885       <tr><td class="lineno" valign="top"></td><td class="lblock">   is maintained at &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="rblock"><span class="insert">   Registry"</span> is maintained at</td><td class="lineno" valign="top"></td></tr>
    886       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td class="lineno" valign="top"></td></tr>
    887       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    888       <tr><td class="lineno" valign="top"></td><td class="left">8.4.1.  Procedure</td><td> </td><td class="right">8.4.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    889       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    890       <tr><td class="lineno" valign="top"></td><td class="left">   Content coding registrations MUST include the following fields:</td><td> </td><td class="right">   Content coding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    891       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    892       <tr><td class="lineno" valign="top"></td><td class="left">   o  Name</td><td> </td><td class="right">   o  Name</td><td class="lineno" valign="top"></td></tr>
    893       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    894       <tr><td class="lineno" valign="top"></td><td class="left">   o  Description</td><td> </td><td class="right">   o  Description</td><td class="lineno" valign="top"></td></tr>
    895       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    896       <tr><td class="lineno" valign="top"></td><td class="left">   o  Pointer to specification text</td><td> </td><td class="right">   o  Pointer to specification text</td><td class="lineno" valign="top"></td></tr>
    897       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    898       <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 81, line 26</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 81, line 26</em></th><td></td></tr>
    899       <tr><td class="lineno" valign="top"></td><td class="left">   codings (Section 4 of [RFC7230]), unless the encoding transformation</td><td> </td><td class="right">   codings (Section 4 of [RFC7230]), unless the encoding transformation</td><td class="lineno" valign="top"></td></tr>
    900       <tr><td class="lineno" valign="top"></td><td class="left">   is identical (as is the case for the compression codings defined in</td><td> </td><td class="right">   is identical (as is the case for the compression codings defined in</td><td class="lineno" valign="top"></td></tr>
    901       <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.2 of [RFC7230]).</td><td> </td><td class="right">   Section 4.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
    902       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    903       <tr><td class="lineno" valign="top"></td><td class="left">   Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right">   Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
    904       <tr><td class="lineno" valign="top"></td><td class="left">   4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td> </td><td class="right">   4.1 of [RFC5226]) and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>
    905       <tr><td class="lineno" valign="top"></td><td class="left">   defined in this section.</td><td> </td><td class="right">   defined in this section.</td><td class="lineno" valign="top"></td></tr>
    906       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    907       <tr><td class="lineno" valign="top"></td><td class="left">8.4.2.  Registrations</td><td> </td><td class="right">8.4.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    908       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    909       <tr><td><a name="diff0043" /></td></tr>
    910       <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP Content Coding Registry" has been updated with the</td><td> </td><td class="rblock">   The "HTTP Content Coding<span class="insert">s</span> Registry" has been updated with the</td><td class="lineno" valign="top"></td></tr>
    911       <tr><td class="lineno" valign="top"></td><td class="left">   registrations below:</td><td> </td><td class="right">   registrations below:</td><td class="lineno" valign="top"></td></tr>
    912       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    913       <tr><td class="lineno" valign="top"></td><td class="left">   +----------+----------------------------------------+---------------+</td><td> </td><td class="right">   +----------+----------------------------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    914       <tr><td class="lineno" valign="top"></td><td class="left">   | Name     | Description                            | Reference     |</td><td> </td><td class="right">   | Name     | Description                            | Reference     |</td><td class="lineno" valign="top"></td></tr>
    915       <tr><td class="lineno" valign="top"></td><td class="left">   +----------+----------------------------------------+---------------+</td><td> </td><td class="right">   +----------+----------------------------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    916       <tr><td class="lineno" valign="top"></td><td class="left">   | identity | Reserved (synonym for "no encoding" in | Section 5.3.4 |</td><td> </td><td class="right">   | identity | Reserved (synonym for "no encoding" in | Section 5.3.4 |</td><td class="lineno" valign="top"></td></tr>
    917       <tr><td class="lineno" valign="top"></td><td class="left">   |          | Accept-Encoding)                       |               |</td><td> </td><td class="right">   |          | Accept-Encoding)                       |               |</td><td class="lineno" valign="top"></td></tr>
    918       <tr><td class="lineno" valign="top"></td><td class="left">   +----------+----------------------------------------+---------------+</td><td> </td><td class="right">   +----------+----------------------------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    919       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    920       <tr><td class="lineno" valign="top"></td><td class="left">9.  Security Considerations</td><td> </td><td class="right">9.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
    921       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    922       <tr><td class="lineno" valign="top"></td><td class="left">   This section is meant to inform developers, information providers,</td><td> </td><td class="right">   This section is meant to inform developers, information providers,</td><td class="lineno" valign="top"></td></tr>
    923       <tr><td class="lineno" valign="top"></td><td class="left">   and users of known security concerns relevant to HTTP semantics and</td><td> </td><td class="right">   and users of known security concerns relevant to HTTP semantics and</td><td class="lineno" valign="top"></td></tr>
    924       <tr><td class="lineno" valign="top"></td><td class="left">   its use for transferring information over the Internet.</td><td> </td><td class="right">   its use for transferring information over the Internet.</td><td class="lineno" valign="top"></td></tr>
    925       <tr><td class="lineno" valign="top"></td><td class="left">   Considerations related to message syntax, parsing, and routing are</td><td> </td><td class="right">   Considerations related to message syntax, parsing, and routing are</td><td class="lineno" valign="top"></td></tr>
    926       <tr><td class="lineno" valign="top"></td><td class="left">   discussed in Section 9 of [RFC7230].</td><td> </td><td class="right">   discussed in Section 9 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    927       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    928       <tr><td class="lineno" valign="top"></td><td class="left">   The list of considerations below is not exhaustive.  Most security</td><td> </td><td class="right">   The list of considerations below is not exhaustive.  Most security</td><td class="lineno" valign="top"></td></tr>
    929       <tr><td class="lineno" valign="top"></td><td class="left">   concerns related to HTTP semantics are about securing server-side</td><td> </td><td class="right">   concerns related to HTTP semantics are about securing server-side</td><td class="lineno" valign="top"></td></tr>
    930       <tr><td><a name="diff0044" /></td></tr>
    931       <tr><td class="lineno" valign="top"></td><td class="lblock">   applications (code behind the HTTP <span class="delete">interface),</span> securing <span class="delete">user agent</span></td><td> </td><td class="rblock">   applications (code behind the HTTP <span class="insert">interface) or</span> securing <span class="insert">user-agent</span></td><td class="lineno" valign="top"></td></tr>
    932       <tr><td class="lineno" valign="top"></td><td class="lblock">   processing of payloads received via <span class="delete">HTTP, or secure</span> use of the</td><td> </td><td class="rblock">   processing of payloads received via <span class="insert">HTTP.  Secure</span> use of the Internet</td><td class="lineno" valign="top"></td></tr>
    933       <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet in general, rather than security of the <span class="delete">protocol.</span>  Various</td><td> </td><td class="rblock">   in general, rather than security of the <span class="insert">protocol, might also be</span></td><td class="lineno" valign="top"></td></tr>
    934       <tr><td class="lineno" valign="top"></td><td class="lblock">   organizations maintain topical information and links to current</td><td> </td><td class="rblock"><span class="insert">   related.</span>  Various organizations maintain topical information and</td><td class="lineno" valign="top"></td></tr>
    935       <tr><td class="lineno" valign="top"></td><td class="lblock">   research on Web application security (e.g., [OWASP]).</td><td> </td><td class="rblock">   links to current research on Web application security (e.g.,</td><td class="lineno" valign="top"></td></tr>
    936       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   [OWASP]).</td><td class="lineno" valign="top"></td></tr>
    937       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    938       <tr><td class="lineno" valign="top"></td><td class="left">9.1.  Attacks Based on File and Path Names</td><td> </td><td class="right">9.1.  Attacks Based on File and Path Names</td><td class="lineno" valign="top"></td></tr>
    939       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    940       <tr><td class="lineno" valign="top"></td><td class="left">   Origin servers frequently make use of their local file system to</td><td> </td><td class="right">   Origin servers frequently make use of their local file system to</td><td class="lineno" valign="top"></td></tr>
    941       <tr><td class="lineno" valign="top"></td><td class="left">   manage the mapping from effective request URI to resource</td><td> </td><td class="right">   manage the mapping from effective request URI to resource</td><td class="lineno" valign="top"></td></tr>
    942       <tr><td class="lineno" valign="top"></td><td class="left">   representations.  Implementers need to be aware that most file</td><td> </td><td class="right">   representations.  Implementers need to be aware that most file</td><td class="lineno" valign="top"></td></tr>
    943       <tr><td class="lineno" valign="top"></td><td class="left">   systems are not designed to protect against malicious file or path</td><td> </td><td class="right">   systems are not designed to protect against malicious file or path</td><td class="lineno" valign="top"></td></tr>
    944       <tr><td class="lineno" valign="top"></td><td class="left">   names and, thus, depend on the origin server to avoid mapping to file</td><td> </td><td class="right">   names and, thus, depend on the origin server to avoid mapping to file</td><td class="lineno" valign="top"></td></tr>
    945       <tr><td class="lineno" valign="top"></td><td class="left">   names, folders, or directories that have special significance to the</td><td> </td><td class="right">   names, folders, or directories that have special significance to the</td><td class="lineno" valign="top"></td></tr>
    946       <tr><td class="lineno" valign="top"></td><td class="left">   system.</td><td> </td><td class="right">   system.</td><td class="lineno" valign="top"></td></tr>
    947       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    948       <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 82, line 25</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 82, line 25</em></th><td></td></tr>
    949       <tr><td class="lineno" valign="top"></td><td class="left">   For example, UNIX, Microsoft Windows, and other operating systems use</td><td> </td><td class="right">   For example, UNIX, Microsoft Windows, and other operating systems use</td><td class="lineno" valign="top"></td></tr>
    950       <tr><td class="lineno" valign="top"></td><td class="left">   ".." as a path component to indicate a directory level above the</td><td> </td><td class="right">   ".." as a path component to indicate a directory level above the</td><td class="lineno" valign="top"></td></tr>
    951       <tr><td class="lineno" valign="top"></td><td class="left">   current one, and they use specially named paths or file names to send</td><td> </td><td class="right">   current one, and they use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr>
    952       <tr><td class="lineno" valign="top"></td><td class="left">   data to system devices.  Similar naming conventions might exist</td><td> </td><td class="right">   data to system devices.  Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr>
    953       <tr><td class="lineno" valign="top"></td><td class="left">   within other types of storage systems.  Likewise, local storage</td><td> </td><td class="right">   within other types of storage systems.  Likewise, local storage</td><td class="lineno" valign="top"></td></tr>
    954       <tr><td class="lineno" valign="top"></td><td class="left">   systems have an annoying tendency to prefer user-friendliness over</td><td> </td><td class="right">   systems have an annoying tendency to prefer user-friendliness over</td><td class="lineno" valign="top"></td></tr>
    955       <tr><td class="lineno" valign="top"></td><td class="left">   security when handling invalid or unexpected characters,</td><td> </td><td class="right">   security when handling invalid or unexpected characters,</td><td class="lineno" valign="top"></td></tr>
    956       <tr><td class="lineno" valign="top"></td><td class="left">   recomposition of decomposed characters, and case-normalization of</td><td> </td><td class="right">   recomposition of decomposed characters, and case-normalization of</td><td class="lineno" valign="top"></td></tr>
    957       <tr><td class="lineno" valign="top"></td><td class="left">   case-insensitive names.</td><td> </td><td class="right">   case-insensitive names.</td><td class="lineno" valign="top"></td></tr>
    958       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    959       <tr><td><a name="diff0045" /></td></tr>
    960       <tr><td class="lineno" valign="top"></td><td class="lblock">   Attacks based on such special names tend to focus on either <span class="delete">denial-</span></td><td> </td><td class="rblock">   Attacks based on such special names tend to focus on either <span class="insert">denial of</span></td><td class="lineno" valign="top"></td></tr>
    961       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   of-service</span> (e.g., telling the server to read from a COM port) or</td><td> </td><td class="rblock"><span class="insert">   service</span> (e.g., telling the server to read from a COM port) or</td><td class="lineno" valign="top"></td></tr>
    962       <tr><td class="lineno" valign="top"></td><td class="left">   disclosure of configuration and source files that are not meant to be</td><td> </td><td class="right">   disclosure of configuration and source files that are not meant to be</td><td class="lineno" valign="top"></td></tr>
    963       <tr><td class="lineno" valign="top"></td><td class="left">   served.</td><td> </td><td class="right">   served.</td><td class="lineno" valign="top"></td></tr>
    964       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    965       <tr><td class="lineno" valign="top"></td><td class="left">9.2.  Attacks Based on Command, Code, or Query Injection</td><td> </td><td class="right">9.2.  Attacks Based on Command, Code, or Query Injection</td><td class="lineno" valign="top"></td></tr>
    966       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    967       <tr><td class="lineno" valign="top"></td><td class="left">   Origin servers often use parameters within the URI as a means of</td><td> </td><td class="right">   Origin servers often use parameters within the URI as a means of</td><td class="lineno" valign="top"></td></tr>
    968       <tr><td class="lineno" valign="top"></td><td class="left">   identifying system services, selecting database entries, or choosing</td><td> </td><td class="right">   identifying system services, selecting database entries, or choosing</td><td class="lineno" valign="top"></td></tr>
    969       <tr><td class="lineno" valign="top"></td><td class="left">   a data source.  However, data received in a request cannot be</td><td> </td><td class="right">   a data source.  However, data received in a request cannot be</td><td class="lineno" valign="top"></td></tr>
    970       <tr><td class="lineno" valign="top"></td><td class="left">   trusted.  An attacker could construct any of the request data</td><td> </td><td class="right">   trusted.  An attacker could construct any of the request data</td><td class="lineno" valign="top"></td></tr>
    971       <tr><td class="lineno" valign="top"></td><td class="left">   elements (method, request-target, header fields, or body) to contain</td><td> </td><td class="right">   elements (method, request-target, header fields, or body) to contain</td><td class="lineno" valign="top"></td></tr>
    972       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    973       <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>
     133      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     134      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>
    974135      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    975136      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td> </td><td class="right">   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td class="lineno" valign="top"></td></tr>
     
    982143      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    983144      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
    984       <tr><td><a name="diff0046" /></td></tr>
     145      <tr><td><a name="diff0008" /></td></tr>
    985146      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    986147      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    987148      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    988149      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    989       <tr><td><a name="diff0047" /></td></tr>
     150      <tr><td><a name="diff0009" /></td></tr>
    990151      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
    991152      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
     
    994155      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="right">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
    995156      <tr><td class="lineno" valign="top"></td><td class="left">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr>
    996       <tr><td><a name="diff0048" /></td></tr>
     157      <tr><td><a name="diff0010" /></td></tr>
    997158      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    998159      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    1000161      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
    1001162      <tr><td class="lineno" valign="top"></td><td class="left">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
    1002       <tr><td><a name="diff0049" /></td></tr>
     163      <tr><td><a name="diff0011" /></td></tr>
    1003164      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1004165      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1005166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1006167      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1007       <tr><td><a name="diff0050" /></td></tr>
     168      <tr><td><a name="diff0012" /></td></tr>
    1008169      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1009170      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    1020181      <tr><td class="lineno" valign="top"></td><td class="left">              Application Protocols", BCP 178, RFC 6648, June 2012.</td><td> </td><td class="right">              Application Protocols", BCP 178, RFC 6648, June 2012.</td><td class="lineno" valign="top"></td></tr>
    1021182      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1022       <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr>
     183      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr>
    1023184      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td> </td><td class="right">   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td class="lineno" valign="top"></td></tr>
    1024185      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    1031192      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1032193      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr>
    1033       <tr><td><a name="diff0051" /></td></tr>
     194      <tr><td><a name="diff0013" /></td></tr>
    1034195      <tr><td class="lineno" valign="top"></td><td class="lblock">              Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock">              Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr>
    1035196      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    1046207      <tr><td class="lineno" valign="top"></td><td class="left">   that differ from MIME.  These differences were carefully chosen to</td><td> </td><td class="right">   that differ from MIME.  These differences were carefully chosen to</td><td class="lineno" valign="top"></td></tr>
    1047208      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1048       <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr>
    1049       <tr><td class="lineno" valign="top"></td><td class="left">   message to an HTTP client.</td><td> </td><td class="right">   message to an HTTP client.</td><td class="lineno" valign="top"></td></tr>
    1050       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1051       <tr><td class="lineno" valign="top"></td><td class="left">   Proxies and gateways from HTTP to MIME-compliant protocols are</td><td> </td><td class="right">   Proxies and gateways from HTTP to MIME-compliant protocols are</td><td class="lineno" valign="top"></td></tr>
    1052       <tr><td class="lineno" valign="top"></td><td class="left">   responsible for ensuring that the message is in the correct format</td><td> </td><td class="right">   responsible for ensuring that the message is in the correct format</td><td class="lineno" valign="top"></td></tr>
    1053       <tr><td class="lineno" valign="top"></td><td class="left">   and encoding for safe transport on that protocol, where "safe</td><td> </td><td class="right">   and encoding for safe transport on that protocol, where "safe</td><td class="lineno" valign="top"></td></tr>
    1054       <tr><td class="lineno" valign="top"></td><td class="left">   transport" is defined by the limitations of the protocol being used.</td><td> </td><td class="right">   transport" is defined by the limitations of the protocol being used.</td><td class="lineno" valign="top"></td></tr>
    1055       <tr><td class="lineno" valign="top"></td><td class="left">   Such a proxy or gateway ought to transform and label the data with an</td><td> </td><td class="right">   Such a proxy or gateway ought to transform and label the data with an</td><td class="lineno" valign="top"></td></tr>
    1056       <tr><td class="lineno" valign="top"></td><td class="left">   appropriate Content-Transfer-Encoding if doing so will improve the</td><td> </td><td class="right">   appropriate Content-Transfer-Encoding if doing so will improve the</td><td class="lineno" valign="top"></td></tr>
    1057       <tr><td class="lineno" valign="top"></td><td class="left">   likelihood of safe transport over the destination protocol.</td><td> </td><td class="right">   likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr>
    1058       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1059       <tr><td><a name="diff0052" /></td></tr>
    1060       <tr><td class="lineno" valign="top"></td><td class="lblock">A.6.  MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6.  MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr>
    1061       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1062       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right">   HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr>
    1063       <tr><td><a name="diff0053" /></td></tr>
    1064       <tr><td class="lineno" valign="top"></td><td class="lblock">   implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock">   implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr>
    1065       <tr><td class="lineno" valign="top"></td><td class="left">   Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right">   Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr>
    1066       <tr><td class="lineno" valign="top"></td><td class="left">   lines.  MHTML messages being transported by HTTP follow all</td><td> </td><td class="right">   lines.  MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr>
    1067       <tr><td><a name="diff0054" /></td></tr>
    1068       <tr><td class="lineno" valign="top"></td><td class="lblock">   conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock">   conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr>
    1069       <tr><td class="lineno" valign="top"></td><td class="left">   canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right">   canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr>
    1070       <tr><td class="lineno" valign="top"></td><td class="left">   payload and, aside from the "multipart/byteranges" type (Appendix A</td><td> </td><td class="right">   payload and, aside from the "multipart/byteranges" type (Appendix A</td><td class="lineno" valign="top"></td></tr>
    1071       <tr><td class="lineno" valign="top"></td><td class="left">   of [RFC7233]), does not interpret the content or any MIME header</td><td> </td><td class="right">   of [RFC7233]), does not interpret the content or any MIME header</td><td class="lineno" valign="top"></td></tr>
    1072       <tr><td class="lineno" valign="top"></td><td class="left">   lines that might be contained therein.</td><td> </td><td class="right">   lines that might be contained therein.</td><td class="lineno" valign="top"></td></tr>
    1073       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1074       <tr><td class="lineno" valign="top"></td><td class="left">Appendix B.  Changes from RFC 2616</td><td> </td><td class="right">Appendix B.  Changes from RFC 2616</td><td class="lineno" valign="top"></td></tr>
    1075       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1076       <tr><td class="lineno" valign="top"></td><td class="left">   The primary changes in this revision have been editorial in nature:</td><td> </td><td class="right">   The primary changes in this revision have been editorial in nature:</td><td class="lineno" valign="top"></td></tr>
    1077       <tr><td class="lineno" valign="top"></td><td class="left">   extracting the messaging syntax and partitioning HTTP semantics into</td><td> </td><td class="right">   extracting the messaging syntax and partitioning HTTP semantics into</td><td class="lineno" valign="top"></td></tr>
    1078       <tr><td class="lineno" valign="top"></td><td class="left">   separate documents for the core features, conditional requests,</td><td> </td><td class="right">   separate documents for the core features, conditional requests,</td><td class="lineno" valign="top"></td></tr>
    1079       <tr><td class="lineno" valign="top"></td><td class="left">   partial requests, caching, and authentication.  The conformance</td><td> </td><td class="right">   partial requests, caching, and authentication.  The conformance</td><td class="lineno" valign="top"></td></tr>
    1080       <tr><td class="lineno" valign="top"></td><td class="left">   language has been revised to clearly target requirements and the</td><td> </td><td class="right">   language has been revised to clearly target requirements and the</td><td class="lineno" valign="top"></td></tr>
    1081       <tr><td class="lineno" valign="top"></td><td class="left">   terminology has been improved to distinguish payload from</td><td> </td><td class="right">   terminology has been improved to distinguish payload from</td><td class="lineno" valign="top"></td></tr>
    1082       <tr><td class="lineno" valign="top"></td><td class="left">   representations and representations from resources.</td><td> </td><td class="right">   representations and representations from resources.</td><td class="lineno" valign="top"></td></tr>
    1083       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1084       <tr><td class="lineno" valign="top"></td><td class="left">   A new requirement has been added that semantics embedded in a URI be</td><td> </td><td class="right">   A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr>
    1085       <tr><td class="lineno" valign="top"></td><td class="left">   disabled when those semantics are inconsistent with the request</td><td> </td><td class="right">   disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr>
    1086       <tr><td><a name="diff0055" /></td></tr>
    1087       <tr><td class="lineno" valign="top"></td><td class="lblock">   method, since this is a common cause of interoperability <span class="delete">failure.</span></td><td> </td><td class="rblock">   method, since this is a common cause of interoperability <span class="insert">failure</span></td><td class="lineno" valign="top"></td></tr>
    1088       <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock">   (Section <span class="insert">2).</span></td><td class="lineno" valign="top"></td></tr>
    1089       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1090       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1091       <tr><td class="lineno" valign="top"></td><td class="left">   An algorithm has been added for determining if a payload is</td><td> </td><td class="right">   An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr>
    1092       <tr><td><a name="diff0056" /></td></tr>
    1093       <tr><td class="lineno" valign="top"></td><td class="lblock">   associated with a specific identifier<span class="delete">.  (Section 3.1.4.1)</span></td><td> </td><td class="rblock">   associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    1094       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1095       <tr><td class="lineno" valign="top"></td><td class="left">   The default charset of ISO-8859-1 for text media types has been</td><td> </td><td class="right">   The default charset of ISO-8859-1 for text media types has been</td><td class="lineno" valign="top"></td></tr>
    1096       <tr><td class="lineno" valign="top"></td><td class="left">   removed; the default is now whatever the media type definition says.</td><td> </td><td class="right">   removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr>
    1097       <tr><td class="lineno" valign="top"></td><td class="left">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr>
    1098       <tr><td><a name="diff0057" /></td></tr>
    1099       <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept-Charset header field.  (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock">   Accept-Charset header field.  (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr>
    1100       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1101       <tr><td class="lineno" valign="top"></td><td class="left">   The definition of Content-Location has been changed to no longer</td><td> </td><td class="right">   The definition of Content-Location has been changed to no longer</td><td class="lineno" valign="top"></td></tr>
    1102       <tr><td class="lineno" valign="top"></td><td class="left">   affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right">   affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr>
    1103       <tr><td class="lineno" valign="top"></td><td class="left">   poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right">   poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr>
    1104       <tr><td><a name="diff0058" /></td></tr>
    1105       <tr><td class="lineno" valign="top"></td><td class="lblock">   breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock">   breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr>
    1106       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr>
    1107       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1108       <tr><td class="lineno" valign="top"></td><td class="left">   To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right">   To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr>
    1109       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right">   [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr>
    1110       <tr><td><a name="diff0059" /></td></tr>
    1111       <tr><td class="lineno" valign="top"></td><td class="lblock">   can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock">   can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
    1112       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr>
    1113       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1114       <tr><td class="lineno" valign="top"></td><td class="left">   Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right">   Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr>
    1115       <tr><td><a name="diff0060" /></td></tr>
    1116       <tr><td class="lineno" valign="top"></td><td class="lblock">   and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock">   and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr>
    1117       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr>
    1118       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1119       <tr><td class="lineno" valign="top"></td><td class="left">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr>
    1120       <tr><td><a name="diff0061" /></td></tr>
    1121       <tr><td class="lineno" valign="top"></td><td class="lblock">   this specification<span class="delete">.  (Section 4.3.6)</span></td><td> </td><td class="rblock">   this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr>
    1122       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1123       <tr><td><a name="diff0062" /></td></tr>
    1124       <tr><td class="lineno" valign="top"></td><td class="lblock">   The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock">   The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr>
    1125       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">safe.</span>  (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock">   (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr>
    1126       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1127       <tr><td class="lineno" valign="top"></td><td class="left">   The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right">   The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr>
    1128       <tr><td><a name="diff0063" /></td></tr>
    1129       <tr><td class="lineno" valign="top"></td><td class="lblock">   widely<span class="delete">-deployed broken implementations.  (Section 5.1.1)</span></td><td> </td><td class="rblock">   widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    1130       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1131       <tr><td class="lineno" valign="top"></td><td class="left">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr>
    1132       <tr><td class="lineno" valign="top"></td><td class="left">   TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right">   TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr>
    1133       <tr><td><a name="diff0064" /></td></tr>
    1134       <tr><td class="lineno" valign="top"></td><td class="lblock">   well<span class="delete">.  (Section 5.1.2)</span></td><td> </td><td class="rblock">   well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    1135       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1136       <tr><td class="lineno" valign="top"></td><td class="left">   The "about:blank" URI has been suggested as a value for the Referer</td><td> </td><td class="right">   The "about:blank" URI has been suggested as a value for the Referer</td><td class="lineno" valign="top"></td></tr>
    1137       <tr><td class="lineno" valign="top"></td><td class="left">   header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right">   header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr>
    1138       <tr><td class="lineno" valign="top"></td><td class="left">   that case from others where the Referer field is not sent or has been</td><td> </td><td class="right">   that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr>
    1139       <tr><td><a name="diff0065" /></td></tr>
    1140       <tr><td class="lineno" valign="top"></td><td class="lblock">   removed<span class="delete">.  (Section 5.5.2)</span></td><td> </td><td class="rblock">   removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr>
    1141       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1142       <tr><td class="lineno" valign="top"></td><td class="left">   The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right">   The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr>
    1143       <tr><td class="lineno" valign="top"></td><td class="left">   stored and reused by a cache without explicit freshness information</td><td> </td><td class="right">   stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr>
    1144       <tr><td><a name="diff0066" /></td></tr>
    1145       <tr><td class="lineno" valign="top"></td><td class="lblock">   present): 204, 404, 405, 414, 501<span class="delete">.  (Section 6)</span></td><td> </td><td class="rblock">   present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr>
    1146       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1147       <tr><td class="lineno" valign="top"></td><td class="left">   The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right">   The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr>
    1148       <tr><td><a name="diff0067" /></td></tr>
    1149       <tr><td class="lineno" valign="top"></td><td class="lblock">   the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock">   the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr>
    1150       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr>
    1151       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1152       <tr><td class="lineno" valign="top"></td><td class="left">   The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right">   The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr>
    1153       <tr><td><a name="diff0068" /></td></tr>
    1154       <tr><td class="lineno" valign="top"></td><td class="lblock">   broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock">   broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr>
    1155       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr>
    1156       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1157       <tr><td class="lineno" valign="top"></td><td class="left">   The set of request methods that are safe to automatically redirect is</td><td> </td><td class="right">   The set of request methods that are safe to automatically redirect is</td><td class="lineno" valign="top"></td></tr>
    1158       <tr><td class="lineno" valign="top"></td><td class="left">   no longer closed; user agents are able to make that determination</td><td> </td><td class="right">   no longer closed; user agents are able to make that determination</td><td class="lineno" valign="top"></td></tr>
    1159       <tr><td class="lineno" valign="top"></td><td class="left">   based upon the request method semantics.  The redirect status codes</td><td> </td><td class="right">   based upon the request method semantics.  The redirect status codes</td><td class="lineno" valign="top"></td></tr>
    1160       <tr><td class="lineno" valign="top"></td><td class="left">   301, 302, and 307 no longer have normative requirements on response</td><td> </td><td class="right">   301, 302, and 307 no longer have normative requirements on response</td><td class="lineno" valign="top"></td></tr>
    1161       <tr><td><a name="diff0069" /></td></tr>
    1162       <tr><td class="lineno" valign="top"></td><td class="lblock">   payloads and user interaction<span class="delete">.  (Section 6.4)</span></td><td> </td><td class="rblock">   payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>
    1163       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1164       <tr><td class="lineno" valign="top"></td><td class="left">   The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right">   The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>
    1165       <tr><td><a name="diff0070" /></td></tr>
    1166       <tr><td class="lineno" valign="top"></td><td class="lblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>
    1167       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1168       <tr><td class="lineno" valign="top"></td><td class="left">   The description of the 303 (See Other) status code has been changed</td><td> </td><td class="right">   The description of the 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr>
    1169       <tr><td class="lineno" valign="top"></td><td class="left">   to allow it to be cached if explicit freshness information is given,</td><td> </td><td class="right">   to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr>
    1170       <tr><td><a name="diff0071" /></td></tr>
    1171       <tr><td class="lineno" valign="top"></td><td class="lblock">   and a specific definition has been added for a 303 response to <span class="delete">GET.</span></td><td> </td><td class="rblock">   and a specific definition has been added for a 303 response to <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
    1172       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.4.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.4.4).</span></td><td class="lineno" valign="top"></td></tr>
    1173       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1174       <tr><td class="lineno" valign="top"></td><td class="left">   The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right">   The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr>
    1175       <tr><td><a name="diff0072" /></td></tr>
    1176       <tr><td class="lineno" valign="top"></td><td class="lblock">   concerns regarding in-band configuration of a proxy<span class="delete">.  (Section 6.4.5)</span></td><td> </td><td class="rblock">   concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>
    1177       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1178       <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>
    1179       <tr><td><a name="diff0073" /></td></tr>
    1180       <tr><td class="lineno" valign="top"></td><td class="lblock">   limited to syntax errors<span class="delete">.  (Section 6.5.1)</span></td><td> </td><td class="rblock">   limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>
    1181       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1182       <tr><td class="lineno" valign="top"></td><td class="left">   The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right">   The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>
    1183       <tr><td><a name="diff0074" /></td></tr>
    1184       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2817]<span class="delete">.  (Section 6.5.15)</span></td><td> </td><td class="rblock">   [RFC2817]<span class="insert"> (Section 6.5.15).</span></td><td class="lineno" valign="top"></td></tr>
    1185       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1186       <tr><td class="lineno" valign="top"></td><td class="left">   The target of requirements on HTTP-date and the Date header field</td><td> </td><td class="right">   The target of requirements on HTTP-date and the Date header field</td><td class="lineno" valign="top"></td></tr>
    1187       <tr><td class="lineno" valign="top"></td><td class="left">   have been reduced to those systems generating the date, rather than</td><td> </td><td class="right">   have been reduced to those systems generating the date, rather than</td><td class="lineno" valign="top"></td></tr>
    1188       <tr><td><a name="diff0075" /></td></tr>
    1189       <tr><td class="lineno" valign="top"></td><td class="lblock">   all systems sending a date<span class="delete">.  (Section 7.1.1)</span></td><td> </td><td class="rblock">   all systems sending a date<span class="insert"> (Section 7.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    1190       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1191       <tr><td class="lineno" valign="top"></td><td class="left">   The syntax of the Location header field has been changed to allow all</td><td> </td><td class="right">   The syntax of the Location header field has been changed to allow all</td><td class="lineno" valign="top"></td></tr>
    1192       <tr><td class="lineno" valign="top"></td><td class="left">   URI references, including relative references and fragments, along</td><td> </td><td class="right">   URI references, including relative references and fragments, along</td><td class="lineno" valign="top"></td></tr>
    1193       <tr><td class="lineno" valign="top"></td><td class="left">   with some clarifications as to when use of fragments would not be</td><td> </td><td class="right">   with some clarifications as to when use of fragments would not be</td><td class="lineno" valign="top"></td></tr>
    1194       <tr><td><a name="diff0076" /></td></tr>
    1195       <tr><td class="lineno" valign="top"></td><td class="lblock">   appropriate<span class="delete">.  (Section 7.1.2)</span></td><td> </td><td class="rblock">   appropriate<span class="insert"> (Section 7.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    1196       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1197       <tr><td class="lineno" valign="top"></td><td class="left">   Allow has been reclassified as a response header field, removing the</td><td> </td><td class="right">   Allow has been reclassified as a response header field, removing the</td><td class="lineno" valign="top"></td></tr>
    1198       <tr><td class="lineno" valign="top"></td><td class="left">   option to specify it in a PUT request.  Requirements relating to the</td><td> </td><td class="right">   option to specify it in a PUT request.  Requirements relating to the</td><td class="lineno" valign="top"></td></tr>
    1199       <tr><td class="lineno" valign="top"></td><td class="left">   content of Allow have been relaxed; correspondingly, clients are not</td><td> </td><td class="right">   content of Allow have been relaxed; correspondingly, clients are not</td><td class="lineno" valign="top"></td></tr>
    1200       <tr><td><a name="diff0077" /></td></tr>
    1201       <tr><td class="lineno" valign="top"></td><td class="lblock">   required to always trust its value<span class="delete">.  (Section 7.4.1)</span></td><td> </td><td class="rblock">   required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    1202       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1203       <tr><td><a name="diff0078" /></td></tr>
    1204       <tr><td class="lineno" valign="top"></td><td class="lblock">   A Method Registry has been defined<span class="delete">.  (Section 8.1)</span></td><td> </td><td class="rblock">   A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>
    1205       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1206       <tr><td class="lineno" valign="top"></td><td class="left">   The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right">   The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr>
    1207       <tr><td><a name="diff0079" /></td></tr>
    1208       <tr><td class="lineno" valign="top"></td><td class="lblock">   previously, it was defined in Section 7.1 of <span class="delete">[RFC2817].</span></td><td> </td><td class="rblock">   previously, it was defined in Section 7.1 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.2).</span></td><td class="lineno" valign="top"></td></tr>
    1209       <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1210       <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">8.2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1211       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1212       <tr><td class="lineno" valign="top"></td><td class="left">   Registration of content codings has been changed to require IETF</td><td> </td><td class="right">   Registration of content codings has been changed to require IETF</td><td class="lineno" valign="top"></td></tr>
    1213       <tr><td><a name="diff0080" /></td></tr>
    1214       <tr><td class="lineno" valign="top"></td><td class="lblock">   Review<span class="delete">.  (Section 8.4)</span></td><td> </td><td class="rblock">   Review<span class="insert"> (Section 8.4).</span></td><td class="lineno" valign="top"></td></tr>
    1215       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1216       <tr><td class="lineno" valign="top"></td><td class="left">   The Content-Disposition header field has been removed since it is now</td><td> </td><td class="right">   The Content-Disposition header field has been removed since it is now</td><td class="lineno" valign="top"></td></tr>
    1217       <tr><td class="lineno" valign="top"></td><td class="left">   defined by [RFC6266].</td><td> </td><td class="right">   defined by [RFC6266].</td><td class="lineno" valign="top"></td></tr>
    1218       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1219       <tr><td class="lineno" valign="top"></td><td class="left">   The Content-MD5 header field has been removed because it was</td><td> </td><td class="right">   The Content-MD5 header field has been removed because it was</td><td class="lineno" valign="top"></td></tr>
    1220       <tr><td class="lineno" valign="top"></td><td class="left">   inconsistently implemented with respect to partial responses.</td><td> </td><td class="right">   inconsistently implemented with respect to partial responses.</td><td class="lineno" valign="top"></td></tr>
    1221       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1222       <tr><td class="lineno" valign="top"></td><td class="left">Appendix C.  Imported ABNF</td><td> </td><td class="right">Appendix C.  Imported ABNF</td><td class="lineno" valign="top"></td></tr>
    1223       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1224       <tr><td class="lineno" valign="top"></td><td class="left">   The following core rules are included by reference, as defined in</td><td> </td><td class="right">   The following core rules are included by reference, as defined in</td><td class="lineno" valign="top"></td></tr>
    1225       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1226       <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 99, line 45</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr>
     209      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 99, line 45</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr>
    1227210      <tr><td class="lineno" valign="top"></td><td class="left">      HEAD method  25</td><td> </td><td class="right">      HEAD method  25</td><td class="lineno" valign="top"></td></tr>
    1228211      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    1235218      <tr><td class="lineno" valign="top"></td><td class="left">   M</td><td> </td><td class="right">   M</td><td class="lineno" valign="top"></td></tr>
    1236219      <tr><td class="lineno" valign="top"></td><td class="left">      Max-Forwards header field  36</td><td> </td><td class="right">      Max-Forwards header field  36</td><td class="lineno" valign="top"></td></tr>
    1237       <tr><td><a name="diff0081" /></td></tr>
     220      <tr><td><a name="diff0014" /></td></tr>
    1238221      <tr><td class="lineno" valign="top"></td><td class="lblock">      MIME-Version header field  8<span class="delete">9</span></td><td> </td><td class="rblock">      MIME-Version header field  8<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    1239222      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    1249232
    1250233     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    1251      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 81 change blocks.&nbsp;</a></th></tr>
    1252      <tr class="stats"><td></td><th><i>192 lines changed or deleted</i></th><th><i> </i></th><th><i>164 lines changed or added</i></th><td></td></tr>
     234     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 14 change blocks.&nbsp;</a></th></tr>
     235     <tr class="stats"><td></td><th><i>50 lines changed or deleted</i></th><th><i> </i></th><th><i>24 lines changed or added</i></th><td></td></tr>
    1253236     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
    1254237   </table>
Note: See TracChangeset for help on using the changeset viewer.