Ignore:
Timestamp:
06/05/14 12:37:38 (6 years ago)
Author:
julian.reschke@…
Message:

punctuation (#553)

Location:
draft-ietf-httpbis/latest
Files:
10 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p1-messaging.unpg.txt

    r2634 r2636  
    534534   Section 5.7.2.
    535535
    536    A "gateway" (a.k.a., "reverse proxy") is an intermediary that acts as
    537    an origin server for the outbound connection, but translates received
     536   A "gateway" (a.k.a. "reverse proxy") is an intermediary that acts as
     537   an origin server for the outbound connection but translates received
    538538   requests and forwards them inbound to another server or servers.
    539539   Gateways are often used to encapsulate legacy or untrusted
     
    693693   commonly understood to be a reasonable length for some protocol
    694694   elements has changed over the course of the past two decades of HTTP
    695    use, and is expected to continue changing in the future.
     695   use and is expected to continue changing in the future.
    696696
    697697   At a minimum, a recipient MUST be able to parse and process protocol
     
    11261126   In theory, a client could receive requests and a server could receive
    11271127   responses, distinguishing them by their different start-line formats,
    1128    but in practice servers are implemented to only expect a request (a
     1128   but, in practice, servers are implemented to only expect a request (a
    11291129   response is interpreted as an unknown or invalid request method) and
    11301130   clients are implemented to only expect a response.
     
    18941894   value given by Content-Length.  A response that has neither chunked
    18951895   transfer coding nor Content-Length is terminated by closure of the
    1896    connection, and thus is considered complete regardless of the number
     1896   connection and, thus, is considered complete regardless of the number
    18971897   of message body octets received, provided that the header section was
    18981898   received intact.
     
    26822682
    26832683   Server header fields.  However, all comments in the Via field are
    2684    optional and a recipient MAY remove them prior to forwarding the
     2684   optional, and a recipient MAY remove them prior to forwarding the
    26852685   message.
    26862686
     
    30483048   ceiling, but this was found to be impractical for many applications.
    30493049   As a result, this specification does not mandate a particular maximum
    3050    number of connections, but instead encourages clients to be
     3050   number of connections but, instead, encourages clients to be
    30513051   conservative when opening multiple connections.
    30523052
  • draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt

    r2635 r2636  
    295295   request with one or more response messages.  A client constructs
    296296   request messages to communicate specific intentions, and examines
    297    received responses to see if the intentions were carried out and
     297   received responses to see if the intentions were carried out, and
    298298   determine how to interpret the results.  This document defines
    299299   HTTP/1.1 request and response semantics in terms of the architecture
     
    705705   each separated by a hyphen character ("-", %x2D).  In most cases, a
    706706   language tag consists of a primary language subtag that identifies a
    707    broad family of related languages (e.g., "en" = English) which is
     707   broad family of related languages (e.g., "en" = English), which is
    708708   optionally followed by a series of subtags that refine or narrow that
    709709   language's range (e.g., "en-CA" = the variety of English as
     
    13321332   specific requirements see [RFC7234].  In general, safe methods that
    13331333   do not depend on a current or authoritative response are defined as
    1334    cacheable; this specification defines GET, HEAD and POST as
     1334   cacheable; this specification defines GET, HEAD, and POST as
    13351335   cacheable, although the overwhelming majority of cache
    13361336   implementations only support GET and HEAD.
     
    13471347
    13481348   It is tempting to think of resource identifiers as remote file system
    1349    pathnames, and of representations as being a copy of the contents of
     1349   pathnames and of representations as being a copy of the contents of
    13501350   such files.  In fact, that is how many resources are implemented (see
    13511351   Section 9.1 for related security considerations).  However, there are
     
    13561356   a file system, an origin server might be configured to execute the
    13571357   files with the request as input and send the output as the
    1358    representation, rather than transfer the files directly.  Regardless,
     1358   representation rather than transfer the files directly.  Regardless,
    13591359   only the origin server needs to know how each of its resource
    1360    identifiers corresponds to an implementation, and how each
     1360   identifiers corresponds to an implementation and how each
    13611361   implementation manages to select and send a current representation of
    13621362   the target resource in a response to GET.
     
    16191619   functionality.  In effect, this method is similar to the rm command
    16201620   in UNIX: it expresses a deletion operation on the URI mapping of the
    1621    origin server, rather than an expectation that the previously
     1621   origin server rather than an expectation that the previously
    16221622   associated information be deleted.
    16231623
     
    20332033   value is greater than zero, the intermediary MUST generate an updated
    20342034   Max-Forwards field in the forwarded message with a field-value that
    2035    is the lesser of: a) the received value decremented by one (1), or b)
     2035   is the lesser of a) the received value decremented by one (1) or b)
    20362036   the recipient's maximum supported value for Max-Forwards.
    20372037
     
    23962396
    23972397
    2398    is not subject to content negotiation, or honor the header field by
     2398   is not subject to content negotiation or honor the header field by
    23992399   sending a 406 (Not Acceptable) response.  However, the latter is not
    24002400   encouraged, as doing so can prevent users from accessing content that
     
    24222422   Since intelligibility is highly dependent on the individual user,
    24232423   user agents need to allow user control over the linguistic preference
    2424    (either through configuration of the user agent itself, or by
     2424   (either through configuration of the user agent itself or by
    24252425   defaulting to a user controllable system setting).  A user agent that
    24262426   does not provide such control to the user MUST NOT send an Accept-
     
    28042804   prior to completing the requested action and sending a final
    28052805   response.  All 1xx responses consist of only the status-line and
    2806    optional header fields, and thus are terminated by the empty line at
     2806   optional header fields and, thus, are terminated by the empty line at
    28072807   the end of the header section.  Since HTTP/1.0 did not define any 1xx
    28082808   status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
     
    32153215   to a selected resource, since doing so provides the information
    32163216   corresponding to the POST response in a form that can be separately
    3217    identified, bookmarked, and cached independent of the original
     3217   identified, bookmarked, and cached, independent of the original
    32183218   request.
    32193219
     
    34573457   information, when the client has descended into a "black hole" of
    34583458   redirection (e.g., a redirected URI prefix that points to a suffix of
    3459    itself), or when the server is under attack by a client attempting to
     3459   itself) or when the server is under attack by a client attempting to
    34603460   exploit potential security holes.
    34613461
     
    42224222   when the condition is false.  Likewise, if the new method might have
    42234223   some use for partial response semantics ([RFC7233]), it ought to
    4224    document this too.
     4224   document this, too.
    42254225
    42264226      Note: Avoid defining a method name that starts with "M-", since
     
    44584458   consider documenting:
    44594459
    4460    o  Whether the field is a single value, or whether it can be a list
     4460   o  Whether the field is a single value or whether it can be a list
    44614461      (delimited by commas; see Section 3.2 of [RFC7230]).
    44624462
     
    46254625   representations.  Implementers need to be aware that most file
    46264626   systems are not designed to protect against malicious file or path
    4627    names, and thus depend on the origin server to avoid mapping to file
     4627   names and, thus, depend on the origin server to avoid mapping to file
    46284628   names, folders, or directories that have special significance to the
    46294629   system.
  • draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt

    r2634 r2636  
    494494
    495495
    496 Section 2.3., paragraph 6:
    497 OLD:
    498 
    499     A "gateway" (a.k.a., "reverse proxy") is an intermediary that acts as
    500     an origin server for the outbound connection, but translates received
    501     requests and forwards them inbound to another server or servers.
    502     Gateways are often used to encapsulate legacy or untrusted
    503     information services, to improve server performance through
    504     "accelerator" caching, and to enable partitioning or load balancing
    505     of HTTP services across multiple machines.
    506 
    507 NEW:
    508 
    509     A "gateway" (a.k.a. "reverse proxy") is an intermediary that acts as
    510     an origin server for the outbound connection but translates received
    511     requests and forwards them inbound to another server or servers.
    512     Gateways are often used to encapsulate legacy or untrusted
    513     information services, to improve server performance through
    514     "accelerator" caching, and to enable partitioning or load balancing
    515     of HTTP services across multiple machines.
    516 
    517 
    518496Section 2.3., paragraph 7:
    519497OLD:
     
    606584    name and field-value components, but then forward the header field
    607585    without further parsing inside the field-value.
    608 
    609 
    610 Section 2.5., paragraph 6:
    611 OLD:
    612 
    613     HTTP does not have specific length limitations for many of its
    614     protocol elements because the lengths that might be appropriate will
    615     vary widely, depending on the deployment context and purpose of the
    616     implementation.  Hence, interoperability between senders and
    617     recipients depends on shared expectations regarding what is a
    618     reasonable length for each protocol element.  Furthermore, what is
    619     commonly understood to be a reasonable length for some protocol
    620     elements has changed over the course of the past two decades of HTTP
    621     use, and is expected to continue changing in the future.
    622 
    623 NEW:
    624 
    625     HTTP does not have specific length limitations for many of its
    626     protocol elements because the lengths that might be appropriate will
    627     vary widely, depending on the deployment context and purpose of the
    628     implementation.  Hence, interoperability between senders and
    629     recipients depends on shared expectations regarding what is a
    630     reasonable length for each protocol element.  Furthermore, what is
    631     commonly understood to be a reasonable length for some protocol
    632     elements has changed over the course of the past two decades of HTTP
    633     use and is expected to continue changing in the future.
    634586
    635587
     
    795747    In theory, a client could receive requests and a server could receive
    796748    responses, distinguishing them by their different start-line formats,
    797     but in practice servers are implemented to only expect a request (a
     749    but, in practice, servers are implemented to only expect a request (a
    798750    response is interpreted as an unknown or invalid request method) and
    799751    clients are implemented to only expect a response.
     
    1042994
    1043995
    1044 Section 3.4., paragraph 4:
    1045 OLD:
    1046 
    1047     A message body that uses the chunked transfer coding is incomplete if
    1048     the zero-sized chunk that terminates the encoding has not been
    1049     received.  A message that uses a valid Content-Length is incomplete
    1050     if the size of the message body received (in octets) is less than the
    1051     value given by Content-Length.  A response that has neither chunked
    1052     transfer coding nor Content-Length is terminated by closure of the
    1053     connection, and thus is considered complete regardless of the number
    1054     of message body octets received, provided that the header section was
    1055     received intact.
    1056 
    1057 NEW:
    1058 
    1059     A message body that uses the chunked transfer coding is incomplete if
    1060     the zero-sized chunk that terminates the encoding has not been
    1061     received.  A message that uses a valid Content-Length is incomplete
    1062     if the size of the message body received (in octets) is less than the
    1063     value given by Content-Length.  A response that has neither chunked
    1064     transfer coding nor Content-Length is terminated by closure of the
    1065     connection and, thus, is considered complete regardless of the number
    1066     of message body octets received, provided that the header section was
    1067     received intact.
    1068 
    1069 
    1070996Section 4., paragraph 5:
    1071997OLD:
     
    10971023    program [RFC1952].  A recipient SHOULD consider "x-gzip" to be
    10981024    equivalent to "gzip".
    1099 
    1100 
    1101 Section 5.7.1., paragraph 8:
    1102 OLD:
    1103 
    1104     A sender MAY generate comments in the Via header field to identify
    1105     the software of each recipient, analogous to the User-Agent and
    1106     Server header fields.  However, all comments in the Via field are
    1107     optional and a recipient MAY remove them prior to forwarding the
    1108     message.
    1109 
    1110 NEW:
    1111 
    1112     A sender MAY generate comments in the Via header field to identify
    1113     the software of each recipient, analogous to the User-Agent and
    1114     Server header fields.  However, all comments in the Via field are
    1115     optional, and a recipient MAY remove them prior to forwarding the
    1116     message.
    11171025
    11181026
     
    12991207    but it MUST send the corresponding responses in the same order that
    13001208    the requests were received.
    1301 
    1302 
    1303 Section 6.4., paragraph 2:
    1304 OLD:
    1305 
    1306     Previous revisions of HTTP gave a specific number of connections as a
    1307     ceiling, but this was found to be impractical for many applications.
    1308     As a result, this specification does not mandate a particular maximum
    1309     number of connections, but instead encourages clients to be
    1310     conservative when opening multiple connections.
    1311 
    1312 NEW:
    1313 
    1314     Previous revisions of HTTP gave a specific number of connections as a
    1315     ceiling, but this was found to be impractical for many applications.
    1316     As a result, this specification does not mandate a particular maximum
    1317     number of connections but, instead, encourages clients to be
    1318     conservative when opening multiple connections.
    13191209
    13201210
  • draft-ietf-httpbis/latest/auth48/rfc7230.diff.html

    r2634 r2636  
    289289      <tr><td class="lineno" valign="top"></td><td class="left">   Some proxies are designed to apply transformations to selected</td><td> </td><td class="right">   Some proxies are designed to apply transformations to selected</td><td class="lineno" valign="top"></td></tr>
    290290      <tr><td class="lineno" valign="top"></td><td class="left">   messages or payloads while they are being forwarded, as described in</td><td> </td><td class="right">   messages or payloads while they are being forwarded, as described in</td><td class="lineno" valign="top"></td></tr>
    291       <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.7.2.</td><td> </td><td class="right">   Section 5.7.2.</td><td class="lineno" valign="top"></td></tr>
    292       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    293       <tr><td><a name="diff0018" /></td></tr>
    294       <tr><td class="lineno" valign="top"></td><td class="lblock">   A "gateway" <span class="delete">(a.k.a.,</span> "reverse proxy") is an intermediary that acts as</td><td> </td><td class="rblock">   A "gateway" <span class="insert">(a.k.a.</span> "reverse proxy") is an intermediary that acts as</td><td class="lineno" valign="top"></td></tr>
    295       <tr><td class="lineno" valign="top"></td><td class="lblock">   an origin server for the outbound <span class="delete">connection,</span> but translates received</td><td> </td><td class="rblock">   an origin server for the outbound <span class="insert">connection</span> but translates received</td><td class="lineno" valign="top"></td></tr>
    296       <tr><td class="lineno" valign="top"></td><td class="left">   requests and forwards them inbound to another server or servers.</td><td> </td><td class="right">   requests and forwards them inbound to another server or servers.</td><td class="lineno" valign="top"></td></tr>
     291      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     292      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 10, line 36</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 10, line 39</em></th><td></td></tr>
    297293      <tr><td class="lineno" valign="top"></td><td class="left">   Gateways are often used to encapsulate legacy or untrusted</td><td> </td><td class="right">   Gateways are often used to encapsulate legacy or untrusted</td><td class="lineno" valign="top"></td></tr>
    298294      <tr><td class="lineno" valign="top"></td><td class="left">   information services, to improve server performance through</td><td> </td><td class="right">   information services, to improve server performance through</td><td class="lineno" valign="top"></td></tr>
     
    305301      <tr><td class="lineno" valign="top"></td><td class="left">   extensions to HTTP that are outside the scope of this specification.</td><td> </td><td class="right">   extensions to HTTP that are outside the scope of this specification.</td><td class="lineno" valign="top"></td></tr>
    306302      <tr><td class="lineno" valign="top"></td><td class="left">   However, an HTTP-to-HTTP gateway that wishes to interoperate with</td><td> </td><td class="right">   However, an HTTP-to-HTTP gateway that wishes to interoperate with</td><td class="lineno" valign="top"></td></tr>
    307       <tr><td><a name="diff0019" /></td></tr>
     303      <tr><td><a name="diff0018" /></td></tr>
    308304      <tr><td class="lineno" valign="top"></td><td class="lblock">   third-party HTTP servers ought to conform to user<span class="delete"> </span>agent requirements</td><td> </td><td class="rblock">   third-party HTTP servers ought to conform to user<span class="insert">-</span>agent requirements</td><td class="lineno" valign="top"></td></tr>
    309305      <tr><td class="lineno" valign="top"></td><td class="left">   on the gateway's inbound connection.</td><td> </td><td class="right">   on the gateway's inbound connection.</td><td class="lineno" valign="top"></td></tr>
     
    318314      <tr><td class="lineno" valign="top"></td><td class="left">   confidential communication through a shared firewall proxy.</td><td> </td><td class="right">   confidential communication through a shared firewall proxy.</td><td class="lineno" valign="top"></td></tr>
    319315      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    320       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 11, line 22</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 11, line 25</em></th><td></td></tr>
     316      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 11, line 22</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 11, line 25</em></th><td></td></tr>
    321317      <tr><td class="lineno" valign="top"></td><td class="left">   interception proxy filters or redirects outgoing TCP port 80 packets</td><td> </td><td class="right">   interception proxy filters or redirects outgoing TCP port 80 packets</td><td class="lineno" valign="top"></td></tr>
    322318      <tr><td class="lineno" valign="top"></td><td class="left">   (and occasionally other common port traffic).  Interception proxies</td><td> </td><td class="right">   (and occasionally other common port traffic).  Interception proxies</td><td class="lineno" valign="top"></td></tr>
     
    329325      <tr><td class="lineno" valign="top"></td><td class="left">   message can be understood in isolation.  Many implementations depend</td><td> </td><td class="right">   message can be understood in isolation.  Many implementations depend</td><td class="lineno" valign="top"></td></tr>
    330326      <tr><td class="lineno" valign="top"></td><td class="left">   on HTTP's stateless design in order to reuse proxied connections or</td><td> </td><td class="right">   on HTTP's stateless design in order to reuse proxied connections or</td><td class="lineno" valign="top"></td></tr>
    331       <tr><td><a name="diff0020" /></td></tr>
     327      <tr><td><a name="diff0019" /></td></tr>
    332328      <tr><td class="lineno" valign="top"></td><td class="lblock">   dynamically load<span class="delete">-</span>balance requests across multiple servers.  Hence, a</td><td> </td><td class="rblock">   dynamically load<span class="insert"> </span>balance requests across multiple servers.  Hence, a</td><td class="lineno" valign="top"></td></tr>
    333329      <tr><td class="lineno" valign="top"></td><td class="left">   server MUST NOT assume that two requests on the same connection are</td><td> </td><td class="right">   server MUST NOT assume that two requests on the same connection are</td><td class="lineno" valign="top"></td></tr>
     
    342338      <tr><td class="lineno" valign="top"></td><td class="left">   subsystem that controls its message storage, retrieval, and deletion.</td><td> </td><td class="right">   subsystem that controls its message storage, retrieval, and deletion.</td><td class="lineno" valign="top"></td></tr>
    343339      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    344       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 12, line 8</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 12, line 11</em></th><td></td></tr>
     340      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 12, line 8</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 12, line 11</em></th><td></td></tr>
    345341      <tr><td class="lineno" valign="top"></td><td class="left">                     &lt;             &lt;</td><td> </td><td class="right">                     &lt;             &lt;</td><td class="lineno" valign="top"></td></tr>
    346342      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    353349      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7234].</td><td> </td><td class="right">   [RFC7234].</td><td class="lineno" valign="top"></td></tr>
    354350      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    355       <tr><td><a name="diff0021" /></td></tr>
     351      <tr><td><a name="diff0020" /></td></tr>
    356352      <tr><td class="lineno" valign="top"></td><td class="lblock">   There <span class="delete">are</span> a wide variety of architectures and configurations of</td><td> </td><td class="rblock">   There <span class="insert">is</span> a wide variety of architectures and configurations of caches</td><td class="lineno" valign="top"></td></tr>
    357353      <tr><td class="lineno" valign="top"></td><td class="lblock">   caches deployed across the World Wide Web and inside large</td><td> </td><td class="rblock">   deployed across the World Wide Web and inside large organizations.</td><td class="lineno" valign="top"></td></tr>
     
    369365      <tr><td class="lineno" valign="top"></td><td class="left">   depending on what behavior is being constrained by the requirement.</td><td> </td><td class="right">   depending on what behavior is being constrained by the requirement.</td><td class="lineno" valign="top"></td></tr>
    370366      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    371       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 12, line 44</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 12, line 47</em></th><td></td></tr>
     367      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 12, line 44</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 12, line 47</em></th><td></td></tr>
    372368      <tr><td class="lineno" valign="top"></td><td class="left">   elements.  A sender MUST NOT generate protocol elements that convey a</td><td> </td><td class="right">   elements.  A sender MUST NOT generate protocol elements that convey a</td><td class="lineno" valign="top"></td></tr>
    373369      <tr><td class="lineno" valign="top"></td><td class="left">   meaning that is known by that sender to be false.  A sender MUST NOT</td><td> </td><td class="right">   meaning that is known by that sender to be false.  A sender MUST NOT</td><td class="lineno" valign="top"></td></tr>
     
    380376      <tr><td class="lineno" valign="top"></td><td class="left">   When a received protocol element is parsed, the recipient MUST be</td><td> </td><td class="right">   When a received protocol element is parsed, the recipient MUST be</td><td class="lineno" valign="top"></td></tr>
    381377      <tr><td class="lineno" valign="top"></td><td class="left">   able to parse any value of reasonable length that is applicable to</td><td> </td><td class="right">   able to parse any value of reasonable length that is applicable to</td><td class="lineno" valign="top"></td></tr>
    382       <tr><td><a name="diff0022" /></td></tr>
     378      <tr><td><a name="diff0021" /></td></tr>
    383379      <tr><td class="lineno" valign="top"></td><td class="lblock">   the recipient's role and matches the grammar defined by the</td><td> </td><td class="rblock">   the recipient's role and <span class="insert">that </span>matches the grammar defined by the</td><td class="lineno" valign="top"></td></tr>
    384380      <tr><td class="lineno" valign="top"></td><td class="left">   corresponding ABNF rules.  Note, however, that some received protocol</td><td> </td><td class="right">   corresponding ABNF rules.  Note, however, that some received protocol</td><td class="lineno" valign="top"></td></tr>
     
    392388      <tr><td class="lineno" valign="top"></td><td class="left">   vary widely, depending on the deployment context and purpose of the</td><td> </td><td class="right">   vary widely, depending on the deployment context and purpose of the</td><td class="lineno" valign="top"></td></tr>
    393389      <tr><td class="lineno" valign="top"></td><td class="left">   implementation.  Hence, interoperability between senders and</td><td> </td><td class="right">   implementation.  Hence, interoperability between senders and</td><td class="lineno" valign="top"></td></tr>
    394       <tr><td class="lineno" valign="top"></td><td class="left">   recipients depends on shared expectations regarding what is a</td><td> </td><td class="right">   recipients depends on shared expectations regarding what is a</td><td class="lineno" valign="top"></td></tr>
    395       <tr><td class="lineno" valign="top"></td><td class="left">   reasonable length for each protocol element.  Furthermore, what is</td><td> </td><td class="right">   reasonable length for each protocol element.  Furthermore, what is</td><td class="lineno" valign="top"></td></tr>
    396       <tr><td class="lineno" valign="top"></td><td class="left">   commonly understood to be a reasonable length for some protocol</td><td> </td><td class="right">   commonly understood to be a reasonable length for some protocol</td><td class="lineno" valign="top"></td></tr>
    397       <tr><td class="lineno" valign="top"></td><td class="left">   elements has changed over the course of the past two decades of HTTP</td><td> </td><td class="right">   elements has changed over the course of the past two decades of HTTP</td><td class="lineno" valign="top"></td></tr>
    398       <tr><td><a name="diff0023" /></td></tr>
    399       <tr><td class="lineno" valign="top"></td><td class="lblock">   use<span class="delete">,</span> and is expected to continue changing in the future.</td><td> </td><td class="rblock">   use and is expected to continue changing in the future.</td><td class="lineno" valign="top"></td></tr>
    400       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    401       <tr><td class="lineno" valign="top"></td><td class="left">   At a minimum, a recipient MUST be able to parse and process protocol</td><td> </td><td class="right">   At a minimum, a recipient MUST be able to parse and process protocol</td><td class="lineno" valign="top"></td></tr>
    402       <tr><td class="lineno" valign="top"></td><td class="left">   element lengths that are at least as long as the values that it</td><td> </td><td class="right">   element lengths that are at least as long as the values that it</td><td class="lineno" valign="top"></td></tr>
    403       <tr><td class="lineno" valign="top"></td><td class="left">   generates for those same protocol elements in other messages.  For</td><td> </td><td class="right">   generates for those same protocol elements in other messages.  For</td><td class="lineno" valign="top"></td></tr>
    404       <tr><td class="lineno" valign="top"></td><td class="left">   example, an origin server that publishes very long URI references to</td><td> </td><td class="right">   example, an origin server that publishes very long URI references to</td><td class="lineno" valign="top"></td></tr>
    405       <tr><td class="lineno" valign="top"></td><td class="left">   its own resources needs to be able to parse and process those same</td><td> </td><td class="right">   its own resources needs to be able to parse and process those same</td><td class="lineno" valign="top"></td></tr>
    406       <tr><td class="lineno" valign="top"></td><td class="left">   references when received as a request target.</td><td> </td><td class="right">   references when received as a request target.</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">   A recipient MUST interpret a received protocol element according to</td><td> </td><td class="right">   A recipient MUST interpret a received protocol element according to</td><td class="lineno" valign="top"></td></tr>
    409       <tr><td class="lineno" valign="top"></td><td class="left">   the semantics defined for it by this specification, including</td><td> </td><td class="right">   the semantics defined for it by this specification, including</td><td class="lineno" valign="top"></td></tr>
    410       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    411       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr>
     390      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     391      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr>
    412392      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    413393      <tr><td class="lineno" valign="top"></td><td class="left">2.6.  Protocol Versioning</td><td> </td><td class="right">2.6.  Protocol Versioning</td><td class="lineno" valign="top"></td></tr>
     
    420400      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    421401      <tr><td class="lineno" valign="top"></td><td class="left">   The version of an HTTP message is indicated by an HTTP-version field</td><td> </td><td class="right">   The version of an HTTP message is indicated by an HTTP-version field</td><td class="lineno" valign="top"></td></tr>
    422       <tr><td><a name="diff0024" /></td></tr>
     402      <tr><td><a name="diff0022" /></td></tr>
    423403      <tr><td class="lineno" valign="top"></td><td class="lblock">   in the first line of the message.  HTTP-version is case<span class="delete">-</span>sensitive.</td><td> </td><td class="rblock">   in the first line of the message.  HTTP-version is case<span class="insert"> </span>sensitive.</td><td class="lineno" valign="top"></td></tr>
    424404      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    425405      <tr><td class="lineno" valign="top"></td><td class="left">     HTTP-version  = HTTP-name "/" DIGIT "." DIGIT</td><td> </td><td class="right">     HTTP-version  = HTTP-name "/" DIGIT "." DIGIT</td><td class="lineno" valign="top"></td></tr>
    426       <tr><td><a name="diff0025" /></td></tr>
     406      <tr><td><a name="diff0023" /></td></tr>
    427407      <tr><td class="lineno" valign="top"></td><td class="lblock">     HTTP-name     = %x48.54.54.50 ; "HTTP", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock">     HTTP-name     = %x48.54.54.50 ; "HTTP", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr>
    428408      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    437417      <tr><td class="lineno" valign="top"></td><td class="left">   recipient know that more advanced features can be used in response</td><td> </td><td class="right">   recipient know that more advanced features can be used in response</td><td class="lineno" valign="top"></td></tr>
    438418      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    439       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr>
     419      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr>
    440420      <tr><td class="lineno" valign="top"></td><td class="left">   The interpretation of a header field does not change between minor</td><td> </td><td class="right">   The interpretation of a header field does not change between minor</td><td class="lineno" valign="top"></td></tr>
    441421      <tr><td class="lineno" valign="top"></td><td class="left">   versions of the same major HTTP version, though the default behavior</td><td> </td><td class="right">   versions of the same major HTTP version, though the default behavior</td><td class="lineno" valign="top"></td></tr>
     
    448428      <tr><td class="lineno" valign="top"></td><td class="left">   New header fields can be introduced without changing the protocol</td><td> </td><td class="right">   New header fields can be introduced without changing the protocol</td><td class="lineno" valign="top"></td></tr>
    449429      <tr><td class="lineno" valign="top"></td><td class="left">   version if their defined semantics allow them to be safely ignored by</td><td> </td><td class="right">   version if their defined semantics allow them to be safely ignored by</td><td class="lineno" valign="top"></td></tr>
    450       <tr><td><a name="diff0026" /></td></tr>
     430      <tr><td><a name="diff0024" /></td></tr>
    451431      <tr><td class="lineno" valign="top"></td><td class="lblock">   recipients that do not recognize them.  Header<span class="delete"> </span>field extensibility is</td><td> </td><td class="rblock">   recipients that do not recognize them.  Header<span class="insert">-</span>field extensibility is</td><td class="lineno" valign="top"></td></tr>
    452432      <tr><td class="lineno" valign="top"></td><td class="left">   discussed in Section 3.2.1.</td><td> </td><td class="right">   discussed in Section 3.2.1.</td><td class="lineno" valign="top"></td></tr>
     
    461441      <tr><td class="lineno" valign="top"></td><td class="left">   version might result in communication errors when downstream</td><td> </td><td class="right">   version might result in communication errors when downstream</td><td class="lineno" valign="top"></td></tr>
    462442      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    463       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr>
     443      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr>
    464444      <tr><td class="lineno" valign="top"></td><td class="left">   introduced between [RFC2068] and [RFC2616], and this revision has</td><td> </td><td class="right">   introduced between [RFC2068] and [RFC2616], and this revision has</td><td class="lineno" valign="top"></td></tr>
    465445      <tr><td class="lineno" valign="top"></td><td class="left">   specifically avoided any such changes to the protocol.</td><td> </td><td class="right">   specifically avoided any such changes to the protocol.</td><td class="lineno" valign="top"></td></tr>
     
    472452      <tr><td class="lineno" valign="top"></td><td class="left">   message with a higher minor version, when sent to a recipient that</td><td> </td><td class="right">   message with a higher minor version, when sent to a recipient that</td><td class="lineno" valign="top"></td></tr>
    473453      <tr><td class="lineno" valign="top"></td><td class="left">   has not yet indicated support for that higher version, is</td><td> </td><td class="right">   has not yet indicated support for that higher version, is</td><td class="lineno" valign="top"></td></tr>
    474       <tr><td><a name="diff0027" /></td></tr>
     454      <tr><td><a name="diff0025" /></td></tr>
    475455      <tr><td class="lineno" valign="top"></td><td class="lblock">   sufficiently backwards<span class="delete">-</span>compatible to be safely processed by any</td><td> </td><td class="rblock">   sufficiently backwards<span class="insert"> </span>compatible to be safely processed by any</td><td class="lineno" valign="top"></td></tr>
    476456      <tr><td class="lineno" valign="top"></td><td class="left">   implementation of the same major version.</td><td> </td><td class="right">   implementation of the same major version.</td><td class="lineno" valign="top"></td></tr>
     
    488468      <tr><td class="lineno" valign="top"></td><td class="left">   "absolute-path" rule is defined for protocol elements that can</td><td> </td><td class="right">   "absolute-path" rule is defined for protocol elements that can</td><td class="lineno" valign="top"></td></tr>
    489469      <tr><td class="lineno" valign="top"></td><td class="left">   contain a non-empty path component.  (This rule differs slightly from</td><td> </td><td class="right">   contain a non-empty path component.  (This rule differs slightly from</td><td class="lineno" valign="top"></td></tr>
    490       <tr><td><a name="diff0028" /></td></tr>
     470      <tr><td><a name="diff0026" /></td></tr>
    491471      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">RFC 3986's</span> path-abempty <span class="delete">rule,</span> which allows for an empty path to be</td><td> </td><td class="rblock">   <span class="insert">the</span> path-abempty <span class="insert">rule of RFC 3986,</span> which allows for an empty path to</td><td class="lineno" valign="top"></td></tr>
    492472      <tr><td class="lineno" valign="top"></td><td class="lblock">   used in references, and path-absolute rule, which does not allow</td><td> </td><td class="rblock">   be used in references, and path-absolute rule, which does not allow</td><td class="lineno" valign="top"></td></tr>
     
    502482      <tr><td class="lineno" valign="top"></td><td class="left">     uri-host      = &lt;host, defined in [RFC3986], Section 3.2.2&gt;</td><td> </td><td class="right">     uri-host      = &lt;host, defined in [RFC3986], Section 3.2.2&gt;</td><td class="lineno" valign="top"></td></tr>
    503483      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    504       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>
     484      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>
    505485      <tr><td class="lineno" valign="top"></td><td class="left">   of reference (URI-reference), only a URI in absolute form (absolute-</td><td> </td><td class="right">   of reference (URI-reference), only a URI in absolute form (absolute-</td><td class="lineno" valign="top"></td></tr>
    506486      <tr><td class="lineno" valign="top"></td><td class="left">   URI), only the path and optional query components, or some</td><td> </td><td class="right">   URI), only the path and optional query components, or some</td><td class="lineno" valign="top"></td></tr>
     
    513493      <tr><td class="lineno" valign="top"></td><td class="left">   identifiers according to their association with the hierarchical</td><td> </td><td class="right">   identifiers according to their association with the hierarchical</td><td class="lineno" valign="top"></td></tr>
    514494      <tr><td class="lineno" valign="top"></td><td class="left">   namespace governed by a potential HTTP origin server listening for</td><td> </td><td class="right">   namespace governed by a potential HTTP origin server listening for</td><td class="lineno" valign="top"></td></tr>
    515       <tr><td><a name="diff0029" /></td></tr>
     495      <tr><td><a name="diff0027" /></td></tr>
    516496      <tr><td class="lineno" valign="top"></td><td class="lblock">   TCP ([RFC<span class="delete">0</span>793]) connections on a given port.</td><td> </td><td class="rblock">   TCP ([RFC793]) connections on a given port.</td><td class="lineno" valign="top"></td></tr>
    517497      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    526506      <tr><td class="lineno" valign="top"></td><td class="left">   target resource within that origin server's name space.  The optional</td><td> </td><td class="right">   target resource within that origin server's name space.  The optional</td><td class="lineno" valign="top"></td></tr>
    527507      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    528       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 18, line 44</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 18, line 44</em></th><td></td></tr>
     508      <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 18, line 44</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 18, line 44</em></th><td></td></tr>
    529509      <tr><td class="lineno" valign="top"></td><td class="left">   through the use of strong encryption, end-to-end, prior to sending</td><td> </td><td class="right">   through the use of strong encryption, end-to-end, prior to sending</td><td class="lineno" valign="top"></td></tr>
    530510      <tr><td class="lineno" valign="top"></td><td class="left">   the first HTTP request.</td><td> </td><td class="right">   the first HTTP request.</td><td class="lineno" valign="top"></td></tr>
     
    537517      <tr><td class="lineno" valign="top"></td><td class="left">   scheme have no shared identity with the "http" scheme even if their</td><td> </td><td class="right">   scheme have no shared identity with the "http" scheme even if their</td><td class="lineno" valign="top"></td></tr>
    538518      <tr><td class="lineno" valign="top"></td><td class="left">   resource identifiers indicate the same authority (the same host</td><td> </td><td class="right">   resource identifiers indicate the same authority (the same host</td><td class="lineno" valign="top"></td></tr>
    539       <tr><td><a name="diff0030" /></td></tr>
     519      <tr><td><a name="diff0028" /></td></tr>
    540520      <tr><td class="lineno" valign="top"></td><td class="lblock">   listening to the same TCP port).  They are distinct name<span class="delete"> </span>spaces and</td><td> </td><td class="rblock">   listening to the same TCP port).  They are distinct namespaces and</td><td class="lineno" valign="top"></td></tr>
    541521      <tr><td class="lineno" valign="top"></td><td class="left">   are considered to be distinct origin servers.  However, an extension</td><td> </td><td class="right">   are considered to be distinct origin servers.  However, an extension</td><td class="lineno" valign="top"></td></tr>
     
    550530      <tr><td class="lineno" valign="top"></td><td class="left">2.7.3.  http and https URI Normalization and Comparison</td><td> </td><td class="right">2.7.3.  http and https URI Normalization and Comparison</td><td class="lineno" valign="top"></td></tr>
    551531      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    552       <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr>
     532      <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr>
    553533      <tr><td class="lineno" valign="top"></td><td class="left">   Since the "http" and "https" schemes conform to the URI generic</td><td> </td><td class="right">   Since the "http" and "https" schemes conform to the URI generic</td><td class="lineno" valign="top"></td></tr>
    554534      <tr><td class="lineno" valign="top"></td><td class="left">   syntax, such URIs are normalized and compared according to the</td><td> </td><td class="right">   syntax, such URIs are normalized and compared according to the</td><td class="lineno" valign="top"></td></tr>
     
    561541      <tr><td class="lineno" valign="top"></td><td class="left">   path component is equivalent to an absolute path of "/", so the</td><td> </td><td class="right">   path component is equivalent to an absolute path of "/", so the</td><td class="lineno" valign="top"></td></tr>
    562542      <tr><td class="lineno" valign="top"></td><td class="left">   normal form is to provide a path of "/" instead.  The scheme and host</td><td> </td><td class="right">   normal form is to provide a path of "/" instead.  The scheme and host</td><td class="lineno" valign="top"></td></tr>
    563       <tr><td><a name="diff0031" /></td></tr>
     543      <tr><td><a name="diff0029" /></td></tr>
    564544      <tr><td class="lineno" valign="top"></td><td class="lblock">   are case<span class="delete">-</span>insensitive and normally provided in lowercase; all other</td><td> </td><td class="rblock">   are case<span class="insert"> </span>insensitive and normally provided in lowercase; all other</td><td class="lineno" valign="top"></td></tr>
    565545      <tr><td class="lineno" valign="top"></td><td class="left">   components are compared in a case-sensitive manner.  Characters other</td><td> </td><td class="right">   components are compared in a case-sensitive manner.  Characters other</td><td class="lineno" valign="top"></td></tr>
     
    574554      <tr><td class="lineno" valign="top"></td><td class="left">      http://EXAMPLE.com:/%7esmith/home.html</td><td> </td><td class="right">      http://EXAMPLE.com:/%7esmith/home.html</td><td class="lineno" valign="top"></td></tr>
    575555      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    576       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr>
     556      <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr>
    577557      <tr><td class="lineno" valign="top"></td><td class="left">   The presence of such whitespace in a request might be an attempt to</td><td> </td><td class="right">   The presence of such whitespace in a request might be an attempt to</td><td class="lineno" valign="top"></td></tr>
    578558      <tr><td class="lineno" valign="top"></td><td class="left">   trick a server into ignoring that field or processing the line after</td><td> </td><td class="right">   trick a server into ignoring that field or processing the line after</td><td class="lineno" valign="top"></td></tr>
     
    585565      <tr><td class="lineno" valign="top"></td><td class="left">3.1.  Start Line</td><td> </td><td class="right">3.1.  Start Line</td><td class="lineno" valign="top"></td></tr>
    586566      <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><a name="diff0032" /></td></tr>
     567      <tr><td><a name="diff0030" /></td></tr>
    588568      <tr><td class="lineno" valign="top"></td><td class="lblock">   An HTTP message can <span class="delete">either be</span> a request from client to server or a</td><td> </td><td class="rblock">   An HTTP message can <span class="insert">be either</span> a request from client to server or a</td><td class="lineno" valign="top"></td></tr>
    589569      <tr><td class="lineno" valign="top"></td><td class="left">   response from server to client.  Syntactically, the two types of</td><td> </td><td class="right">   response from server to client.  Syntactically, the two types of</td><td class="lineno" valign="top"></td></tr>
     
    594574      <tr><td class="lineno" valign="top"></td><td class="left">   In theory, a client could receive requests and a server could receive</td><td> </td><td class="right">   In theory, a client could receive requests and a server could receive</td><td class="lineno" valign="top"></td></tr>
    595575      <tr><td class="lineno" valign="top"></td><td class="left">   responses, distinguishing them by their different start-line formats,</td><td> </td><td class="right">   responses, distinguishing them by their different start-line formats,</td><td class="lineno" valign="top"></td></tr>
    596       <tr><td><a name="diff0033" /></td></tr>
    597       <tr><td class="lineno" valign="top"></td><td class="lblock">   but<span class="delete"> in practice servers are implemented to only</span> expect a request (a</td><td> </td><td class="rblock">   but<span class="insert">, in practice, servers are implemented only to</span> expect a request (a</td><td class="lineno" valign="top"></td></tr>
     576      <tr><td><a name="diff0031" /></td></tr>
     577      <tr><td class="lineno" valign="top"></td><td class="lblock">   but, in practice, servers are implemented <span class="delete">to only</span> expect a request (a</td><td> </td><td class="rblock">   but, in practice, servers are implemented <span class="insert">only to</span> expect a request (a</td><td class="lineno" valign="top"></td></tr>
    598578      <tr><td class="lineno" valign="top"></td><td class="left">   response is interpreted as an unknown or invalid request method) and</td><td> </td><td class="right">   response is interpreted as an unknown or invalid request method) and</td><td class="lineno" valign="top"></td></tr>
    599579      <tr><td class="lineno" valign="top"></td><td class="left">   clients are implemented to only expect a response.</td><td> </td><td class="right">   clients are implemented to only expect a response.</td><td class="lineno" valign="top"></td></tr>
     
    603583      <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.  Request Line</td><td> </td><td class="right">3.1.1.  Request Line</td><td class="lineno" valign="top"></td></tr>
    604584      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    605       <tr><td><a name="diff0034" /></td></tr>
     585      <tr><td><a name="diff0032" /></td></tr>
    606586      <tr><td class="lineno" valign="top"></td><td class="lblock">   A request-line begins with a method <span class="delete">token,</span> followed by a single space</td><td> </td><td class="rblock">   A request-line begins with a method <span class="insert">token and is</span> followed by a single</td><td class="lineno" valign="top"></td></tr>
    607587      <tr><td class="lineno" valign="top"></td><td class="lblock">   (SP), the request-target, another single space (SP), the protocol</td><td> </td><td class="rblock">   space (SP), the request-target, another single space (SP), the</td><td class="lineno" valign="top"></td></tr>
     
    611591      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    612592      <tr><td class="lineno" valign="top"></td><td class="left">   The method token indicates the request method to be performed on the</td><td> </td><td class="right">   The method token indicates the request method to be performed on the</td><td class="lineno" valign="top"></td></tr>
    613       <tr><td><a name="diff0035" /></td></tr>
     593      <tr><td><a name="diff0033" /></td></tr>
    614594      <tr><td class="lineno" valign="top"></td><td class="lblock">   target resource.  The request method is case<span class="delete">-</span>sensitive.</td><td> </td><td class="rblock">   target resource.  The request method is case<span class="insert"> </span>sensitive.</td><td class="lineno" valign="top"></td></tr>
    615595      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    624604      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    625605      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    626       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 21, line 39</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 21, line 39</em></th><td></td></tr>
     606      <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 21, line 39</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 21, line 39</em></th><td></td></tr>
    627607      <tr><td class="lineno" valign="top"></td><td class="left">   references, resulting in those disallowed characters being sent in a</td><td> </td><td class="right">   references, resulting in those disallowed characters being sent in a</td><td class="lineno" valign="top"></td></tr>
    628608      <tr><td class="lineno" valign="top"></td><td class="left">   request-target.</td><td> </td><td class="right">   request-target.</td><td class="lineno" valign="top"></td></tr>
     
    635615      <tr><td class="lineno" valign="top"></td><td class="left">   security filters along the request chain.</td><td> </td><td class="right">   security filters along the request chain.</td><td class="lineno" valign="top"></td></tr>
    636616      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    637       <tr><td><a name="diff0036" /></td></tr>
     617      <tr><td><a name="diff0034" /></td></tr>
    638618      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP does not place a pre<span class="delete">-</span>defined limit on the length of a request-</td><td> </td><td class="rblock">   HTTP does not place a predefined limit on the length of a request-</td><td class="lineno" valign="top"></td></tr>
    639619      <tr><td class="lineno" valign="top"></td><td class="left">   line, as described in Section 2.5.  A server that receives a method</td><td> </td><td class="right">   line, as described in Section 2.5.  A server that receives a method</td><td class="lineno" valign="top"></td></tr>
     
    643623      <tr><td class="lineno" valign="top"></td><td class="left">   Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td> </td><td class="right">   Too Long) status code (see Section 6.5.12 of [RFC7231]).</td><td class="lineno" valign="top"></td></tr>
    644624      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    645       <tr><td><a name="diff0037" /></td></tr>
     625      <tr><td><a name="diff0035" /></td></tr>
    646626      <tr><td class="lineno" valign="top"></td><td class="lblock">   Various ad<span class="delete">-</span>hoc limitations on request-line length are found in</td><td> </td><td class="rblock">   Various ad<span class="insert"> </span>hoc limitations on request-line length are found in</td><td class="lineno" valign="top"></td></tr>
    647627      <tr><td class="lineno" valign="top"></td><td class="left">   practice.  It is RECOMMENDED that all HTTP senders and recipients</td><td> </td><td class="right">   practice.  It is RECOMMENDED that all HTTP senders and recipients</td><td class="lineno" valign="top"></td></tr>
     
    651631      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    652632      <tr><td class="lineno" valign="top"></td><td class="left">   The first line of a response message is the status-line, consisting</td><td> </td><td class="right">   The first line of a response message is the status-line, consisting</td><td class="lineno" valign="top"></td></tr>
    653       <tr><td><a name="diff0038" /></td></tr>
     633      <tr><td><a name="diff0036" /></td></tr>
    654634      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the protocol version, a space (SP), the status code, another</td><td> </td><td class="rblock">   of the protocol version, a space (SP), the status code, another <span class="insert">space</span></td><td class="lineno" valign="top"></td></tr>
    655635      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">space,</span> a <span class="delete">possibly-empty</span> textual phrase describing the status code,</td><td> </td><td class="rblock"><span class="insert">   (SP),</span> a <span class="insert">possibly empty</span> textual phrase describing the status code,</td><td class="lineno" valign="top"></td></tr>
     
    666646      <tr><td class="lineno" valign="top"></td><td class="left">   first digit), the status codes defined by this specification,</td><td> </td><td class="right">   first digit), the status codes defined by this specification,</td><td class="lineno" valign="top"></td></tr>
    667647      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    668       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>
     648      <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>
    669649      <tr><td class="lineno" valign="top"></td><td class="left">   evaluation, or refine the meaning of responses.</td><td> </td><td class="right">   evaluation, or refine the meaning of responses.</td><td class="lineno" valign="top"></td></tr>
    670650      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    677657      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    678658      <tr><td class="lineno" valign="top"></td><td class="left">   All defined header fields ought to be registered with IANA in the</td><td> </td><td class="right">   All defined header fields ought to be registered with IANA in the</td><td class="lineno" valign="top"></td></tr>
    679       <tr><td><a name="diff0039" /></td></tr>
     659      <tr><td><a name="diff0037" /></td></tr>
    680660      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Message Header Field R</span>egistry, as described in Section 8.3 of</td><td> </td><td class="rblock">   <span class="insert">"Message Headers" field r</span>egistry, as described in Section 8.3 of</td><td class="lineno" valign="top"></td></tr>
    681661      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231].</td><td> </td><td class="right">   [RFC7231].</td><td class="lineno" valign="top"></td></tr>
     
    690670      <tr><td class="lineno" valign="top"></td><td class="left">   apply a request to the target resource until the entire request</td><td> </td><td class="right">   apply a request to the target resource until the entire request</td><td class="lineno" valign="top"></td></tr>
    691671      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    692       <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>
     672      <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>
    693673      <tr><td class="lineno" valign="top"></td><td class="left">   the combined field value in order, separated by a comma.  The order</td><td> </td><td class="right">   the combined field value in order, separated by a comma.  The order</td><td class="lineno" valign="top"></td></tr>
    694674      <tr><td class="lineno" valign="top"></td><td class="left">   in which header fields with the same field name are received is</td><td> </td><td class="right">   in which header fields with the same field name are received is</td><td class="lineno" valign="top"></td></tr>
     
    701681      <tr><td class="lineno" valign="top"></td><td class="left">      list syntax, violating the above requirements on multiple header</td><td> </td><td class="right">      list syntax, violating the above requirements on multiple header</td><td class="lineno" valign="top"></td></tr>
    702682      <tr><td class="lineno" valign="top"></td><td class="left">      fields with the same name.  Since it cannot be combined into a</td><td> </td><td class="right">      fields with the same name.  Since it cannot be combined into a</td><td class="lineno" valign="top"></td></tr>
    703       <tr><td><a name="diff0040" /></td></tr>
     683      <tr><td><a name="diff0038" /></td></tr>
    704684      <tr><td class="lineno" valign="top"></td><td class="lblock">      single field-value, recipients ought to handle <span class="delete">"Set-Cookie"</span> as a</td><td> </td><td class="rblock">      single field-value, recipients ought to handle <span class="insert">Set-Cookie</span> as a</td><td class="lineno" valign="top"></td></tr>
    705685      <tr><td class="lineno" valign="top"></td><td class="left">      special case while processing header fields.  (See Appendix A.2.3</td><td> </td><td class="right">      special case while processing header fields.  (See Appendix A.2.3</td><td class="lineno" valign="top"></td></tr>
     
    716696      <tr><td class="lineno" valign="top"></td><td class="left">   preferred to improve readability, a sender SHOULD generate the</td><td> </td><td class="right">   preferred to improve readability, a sender SHOULD generate the</td><td class="lineno" valign="top"></td></tr>
    717697      <tr><td class="lineno" valign="top"></td><td class="left">   optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td> </td><td class="right">   optional whitespace as a single SP; otherwise, a sender SHOULD NOT</td><td class="lineno" valign="top"></td></tr>
    718       <tr><td><a name="diff0041" /></td></tr>
     698      <tr><td><a name="diff0039" /></td></tr>
    719699      <tr><td class="lineno" valign="top"></td><td class="lblock">   generate optional whitespace except as needed to white<span class="delete">-</span>out invalid or</td><td> </td><td class="rblock">   generate optional whitespace except as needed to white<span class="insert"> </span>out invalid or</td><td class="lineno" valign="top"></td></tr>
    720700      <tr><td class="lineno" valign="top"></td><td class="left">   unwanted protocol elements during in-place message filtering.</td><td> </td><td class="right">   unwanted protocol elements during in-place message filtering.</td><td class="lineno" valign="top"></td></tr>
     
    729709      <tr><td class="lineno" valign="top"></td><td class="left">   it before interpreting the protocol element.</td><td> </td><td class="right">   it before interpreting the protocol element.</td><td class="lineno" valign="top"></td></tr>
    730710      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    731       <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>
     711      <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>
    732712      <tr><td class="lineno" valign="top"></td><td class="left">     BWS            = OWS</td><td> </td><td class="right">     BWS            = OWS</td><td class="lineno" valign="top"></td></tr>
    733713      <tr><td class="lineno" valign="top"></td><td class="left">                    ; "bad" whitespace</td><td> </td><td class="right">                    ; "bad" whitespace</td><td class="lineno" valign="top"></td></tr>
     
    740720      <tr><td class="lineno" valign="top"></td><td class="left">   (usually after the message's entire header section has been</td><td> </td><td class="right">   (usually after the message's entire header section has been</td><td class="lineno" valign="top"></td></tr>
    741721      <tr><td class="lineno" valign="top"></td><td class="left">   processed).  Consequently, this specification does not use ABNF rules</td><td> </td><td class="right">   processed).  Consequently, this specification does not use ABNF rules</td><td class="lineno" valign="top"></td></tr>
    742       <tr><td><a name="diff0042" /></td></tr>
     722      <tr><td><a name="diff0040" /></td></tr>
    743723      <tr><td class="lineno" valign="top"></td><td class="lblock">   to define each <span class="delete">"Field-Name: Field Value"</span> pair, as was done in</td><td> </td><td class="rblock">   to define each <span class="insert">"field-name: field-value"</span> pair, as was done in</td><td class="lineno" valign="top"></td></tr>
    744724      <tr><td class="lineno" valign="top"></td><td class="lblock">   previous editions.  Instead, this specification uses ABNF rules <span class="delete">which</span></td><td> </td><td class="rblock">   previous editions.  Instead, this specification uses ABNF rules <span class="insert">that</span></td><td class="lineno" valign="top"></td></tr>
     
    759739      <tr><td class="lineno" valign="top"></td><td class="left">   whitespace (OWS); a single SP preceding the field-value is preferred</td><td> </td><td class="right">   whitespace (OWS); a single SP preceding the field-value is preferred</td><td class="lineno" valign="top"></td></tr>
    760740      <tr><td class="lineno" valign="top"></td><td class="left">   for consistent readability by humans.  The field value does not</td><td> </td><td class="right">   for consistent readability by humans.  The field value does not</td><td class="lineno" valign="top"></td></tr>
    761       <tr><td><a name="diff0043" /></td></tr>
     741      <tr><td><a name="diff0041" /></td></tr>
    762742      <tr><td class="lineno" valign="top"></td><td class="lblock">   include any leading or trailing white<span class="delete"> </span>space: OWS occurring before the</td><td> </td><td class="rblock">   include any leading or trailing whitespace: OWS occurring before the</td><td class="lineno" valign="top"></td></tr>
    763743      <tr><td class="lineno" valign="top"></td><td class="left">   first non-whitespace octet of the field value or after the last non-</td><td> </td><td class="right">   first non-whitespace octet of the field value or after the last non-</td><td class="lineno" valign="top"></td></tr>
     
    772752      <tr><td class="lineno" valign="top"></td><td class="left">   line folding (i.e., that has any field-value that contains a match to</td><td> </td><td class="right">   line folding (i.e., that has any field-value that contains a match to</td><td class="lineno" valign="top"></td></tr>
    773753      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    774       <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 26, line 15</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 26, line 15</em></th><td></td></tr>
     754      <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 26, line 15</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 26, line 15</em></th><td></td></tr>
    775755      <tr><td class="lineno" valign="top"></td><td class="left">   with a representation explaining that unacceptable line folding was</td><td> </td><td class="right">   with a representation explaining that unacceptable line folding was</td><td class="lineno" valign="top"></td></tr>
    776756      <tr><td class="lineno" valign="top"></td><td class="left">   received, or replace each received obs-fold with one or more SP</td><td> </td><td class="right">   received, or replace each received obs-fold with one or more SP</td><td class="lineno" valign="top"></td></tr>
     
    783763      <tr><td class="lineno" valign="top"></td><td class="left">   value.</td><td> </td><td class="right">   value.</td><td class="lineno" valign="top"></td></tr>
    784764      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    785       <tr><td><a name="diff0044" /></td></tr>
     765      <tr><td><a name="diff0042" /></td></tr>
    786766      <tr><td class="lineno" valign="top"></td><td class="lblock">   Historically, HTTP has allowed field content with text in the <span class="delete">ISO-</span></td><td> </td><td class="rblock">   Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr>
    787767      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   8859-1</span> [ISO-8859-1] charset, supporting other charsets only through</td><td> </td><td class="rblock">   <span class="insert">ISO-8859-1</span> [ISO-8859-1] charset, supporting other charsets only</td><td class="lineno" valign="top"></td></tr>
     
    794774      <tr><td class="lineno" valign="top"></td><td class="left">3.2.5.  Field Limits</td><td> </td><td class="right">3.2.5.  Field Limits</td><td class="lineno" valign="top"></td></tr>
    795775      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    796       <tr><td><a name="diff0045" /></td></tr>
     776      <tr><td><a name="diff0043" /></td></tr>
    797777      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP does not place a pre<span class="delete">-</span>defined limit on the length of each header</td><td> </td><td class="rblock">   HTTP does not place a predefined limit on the length of each header</td><td class="lineno" valign="top"></td></tr>
    798778      <tr><td class="lineno" valign="top"></td><td class="left">   field or on the length of the header section as a whole, as described</td><td> </td><td class="right">   field or on the length of the header section as a whole, as described</td><td class="lineno" valign="top"></td></tr>
    799       <tr><td><a name="diff0046" /></td></tr>
     779      <tr><td><a name="diff0044" /></td></tr>
    800780      <tr><td class="lineno" valign="top"></td><td class="lblock">   in Section 2.5.  Various ad<span class="delete">-</span>hoc limitations on individual header</td><td> </td><td class="rblock">   in Section 2.5.  Various ad<span class="insert"> </span>hoc limitations on individual header</td><td class="lineno" valign="top"></td></tr>
    801781      <tr><td class="lineno" valign="top"></td><td class="left">   field length are found in practice, often depending on the specific</td><td> </td><td class="right">   field length are found in practice, often depending on the specific</td><td class="lineno" valign="top"></td></tr>
     
    810790      <tr><td class="lineno" valign="top"></td><td class="left">   A client MAY discard or truncate received header fields that are</td><td> </td><td class="right">   A client MAY discard or truncate received header fields that are</td><td class="lineno" valign="top"></td></tr>
    811791      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    812       <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr>
     792      <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 33, line 6</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 33, line 6</em></th><td></td></tr>
    813793      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    814794      <tr><td class="lineno" valign="top"></td><td class="left">   6.  If this is a request message and none of the above are true, then</td><td> </td><td class="right">   6.  If this is a request message and none of the above are true, then</td><td class="lineno" valign="top"></td></tr>
     
    821801      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    822802      <tr><td class="lineno" valign="top"></td><td class="left">   Since there is no way to distinguish a successfully completed, close-</td><td> </td><td class="right">   Since there is no way to distinguish a successfully completed, close-</td><td class="lineno" valign="top"></td></tr>
    823       <tr><td><a name="diff0047" /></td></tr>
     803      <tr><td><a name="diff0045" /></td></tr>
    824804      <tr><td class="lineno" valign="top"></td><td class="lblock">   delimited message from a partially<span class="delete">-</span>received message interrupted by</td><td> </td><td class="rblock">   delimited message from a partially<span class="insert"> </span>received message interrupted by</td><td class="lineno" valign="top"></td></tr>
    825805      <tr><td class="lineno" valign="top"></td><td class="left">   network failure, a server SHOULD generate encoding or length-</td><td> </td><td class="right">   network failure, a server SHOULD generate encoding or length-</td><td class="lineno" valign="top"></td></tr>
     
    834814      <tr><td class="lineno" valign="top"></td><td class="left">   valid Content-Length header field if the message body length is known</td><td> </td><td class="right">   valid Content-Length header field if the message body length is known</td><td class="lineno" valign="top"></td></tr>
    835815      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    836       <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 33, line 43</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 33, line 43</em></th><td></td></tr>
     816      <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 33, line 43</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 33, line 43</em></th><td></td></tr>
    837817      <tr><td class="lineno" valign="top"></td><td class="left">   agent MAY discard the remaining data or attempt to determine if that</td><td> </td><td class="right">   agent MAY discard the remaining data or attempt to determine if that</td><td class="lineno" valign="top"></td></tr>
    838818      <tr><td class="lineno" valign="top"></td><td class="left">   data belongs as part of the prior response body, which might be the</td><td> </td><td class="right">   data belongs as part of the prior response body, which might be the</td><td class="lineno" valign="top"></td></tr>
     
    845825      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    846826      <tr><td class="lineno" valign="top"></td><td class="left">   A server that receives an incomplete request message, usually due to</td><td> </td><td class="right">   A server that receives an incomplete request message, usually due to</td><td class="lineno" valign="top"></td></tr>
    847       <tr><td><a name="diff0048" /></td></tr>
     827      <tr><td><a name="diff0046" /></td></tr>
    848828      <tr><td class="lineno" valign="top"></td><td class="lblock">   a canceled request or a triggered time<span class="delete">-</span>out exception, MAY send an</td><td> </td><td class="rblock">   a canceled request or a triggered timeout exception, MAY send an</td><td class="lineno" valign="top"></td></tr>
    849829      <tr><td class="lineno" valign="top"></td><td class="left">   error response prior to closing the connection.</td><td> </td><td class="right">   error response prior to closing the connection.</td><td class="lineno" valign="top"></td></tr>
     
    857837      <tr><td class="lineno" valign="top"></td><td class="left">   If a response terminates in the middle of the header section (before</td><td> </td><td class="right">   If a response terminates in the middle of the header section (before</td><td class="lineno" valign="top"></td></tr>
    858838      <tr><td class="lineno" valign="top"></td><td class="left">   the empty line is received) and the status code might rely on header</td><td> </td><td class="right">   the empty line is received) and the status code might rely on header</td><td class="lineno" valign="top"></td></tr>
    859       <tr><td class="lineno" valign="top"></td><td class="left">   fields to convey the full meaning of the response, then the client</td><td> </td><td class="right">   fields to convey the full meaning of the response, then the client</td><td class="lineno" valign="top"></td></tr>
    860       <tr><td class="lineno" valign="top"></td><td class="left">   cannot assume that meaning has been conveyed; the client might need</td><td> </td><td class="right">   cannot assume that meaning has been conveyed; the client might need</td><td class="lineno" valign="top"></td></tr>
    861       <tr><td class="lineno" valign="top"></td><td class="left">   to repeat the request in order to determine what action to take next.</td><td> </td><td class="right">   to repeat the request in order to determine what action to take next.</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">   A message body that uses the chunked transfer coding is incomplete if</td><td> </td><td class="right">   A message body that uses the chunked transfer coding is incomplete if</td><td class="lineno" valign="top"></td></tr>
    864       <tr><td class="lineno" valign="top"></td><td class="left">   the zero-sized chunk that terminates the encoding has not been</td><td> </td><td class="right">   the zero-sized chunk that terminates the encoding has not been</td><td class="lineno" valign="top"></td></tr>
    865       <tr><td class="lineno" valign="top"></td><td class="left">   received.  A message that uses a valid Content-Length is incomplete</td><td> </td><td class="right">   received.  A message that uses a valid Content-Length is incomplete</td><td class="lineno" valign="top"></td></tr>
    866       <tr><td class="lineno" valign="top"></td><td class="left">   if the size of the message body received (in octets) is less than the</td><td> </td><td class="right">   if the size of the message body received (in octets) is less than the</td><td class="lineno" valign="top"></td></tr>
    867       <tr><td class="lineno" valign="top"></td><td class="left">   value given by Content-Length.  A response that has neither chunked</td><td> </td><td class="right">   value given by Content-Length.  A response that has neither chunked</td><td class="lineno" valign="top"></td></tr>
    868       <tr><td class="lineno" valign="top"></td><td class="left">   transfer coding nor Content-Length is terminated by closure of the</td><td> </td><td class="right">   transfer coding nor Content-Length is terminated by closure of the</td><td class="lineno" valign="top"></td></tr>
    869       <tr><td><a name="diff0049" /></td></tr>
    870       <tr><td class="lineno" valign="top"></td><td class="lblock">   connection<span class="delete">, and thus</span> is considered complete regardless of the number</td><td> </td><td class="rblock">   connection<span class="insert"> and, thus,</span> is considered complete regardless of the number</td><td class="lineno" valign="top"></td></tr>
    871       <tr><td class="lineno" valign="top"></td><td class="left">   of message body octets received, provided that the header section was</td><td> </td><td class="right">   of message body octets received, provided that the header section was</td><td class="lineno" valign="top"></td></tr>
    872       <tr><td class="lineno" valign="top"></td><td class="left">   received intact.</td><td> </td><td class="right">   received intact.</td><td class="lineno" valign="top"></td></tr>
    873       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    874       <tr><td class="lineno" valign="top"></td><td class="left">3.5.  Message Parsing Robustness</td><td> </td><td class="right">3.5.  Message Parsing Robustness</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">   Older HTTP/1.0 user agent implementations might send an extra CRLF</td><td> </td><td class="right">   Older HTTP/1.0 user agent implementations might send an extra CRLF</td><td class="lineno" valign="top"></td></tr>
    877       <tr><td class="lineno" valign="top"></td><td class="left">   after a POST request as a workaround for some early server</td><td> </td><td class="right">   after a POST request as a workaround for some early server</td><td class="lineno" valign="top"></td></tr>
    878       <tr><td class="lineno" valign="top"></td><td class="left">   applications that failed to read message body content that was not</td><td> </td><td class="right">   applications that failed to read message body content that was not</td><td class="lineno" valign="top"></td></tr>
    879       <tr><td class="lineno" valign="top"></td><td class="left">   terminated by a line-ending.  An HTTP/1.1 user agent MUST NOT preface</td><td> </td><td class="right">   terminated by a line-ending.  An HTTP/1.1 user agent MUST NOT preface</td><td class="lineno" valign="top"></td></tr>
    880       <tr><td class="lineno" valign="top"></td><td class="left">   or follow a request with an extra CRLF.  If terminating the request</td><td> </td><td class="right">   or follow a request with an extra CRLF.  If terminating the request</td><td class="lineno" valign="top"></td></tr>
    881       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    882       <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>
     839      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     840      <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>
    883841      <tr><td class="lineno" valign="top"></td><td class="left">                        / "compress" ; Section 4.2.1</td><td> </td><td class="right">                        / "compress" ; Section 4.2.1</td><td class="lineno" valign="top"></td></tr>
    884842      <tr><td class="lineno" valign="top"></td><td class="left">                        / "deflate" ; Section 4.2.2</td><td> </td><td class="right">                        / "deflate" ; Section 4.2.2</td><td class="lineno" valign="top"></td></tr>
     
    891849      <tr><td class="lineno" valign="top"></td><td class="left">     transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td> </td><td class="right">     transfer-parameter = token BWS "=" BWS ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr>
    892850      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    893       <tr><td><a name="diff0050" /></td></tr>
     851      <tr><td><a name="diff0047" /></td></tr>
    894852      <tr><td class="lineno" valign="top"></td><td class="lblock">   All transfer-coding names are <span class="delete">case-insensitive</span> and ought to be</td><td> </td><td class="rblock">   All transfer-coding names are <span class="insert">case insensitive</span> and ought to be</td><td class="lineno" valign="top"></td></tr>
    895853      <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the <span class="delete">HTTP</span> Transfer <span class="delete">Coding</span> registry, as defined in</td><td> </td><td class="rblock">   registered within the <span class="insert">"HTTP</span> Transfer <span class="insert">Coding"</span> registry, as defined in</td><td class="lineno" valign="top"></td></tr>
     
    905863      <tr><td class="lineno" valign="top"></td><td class="left">   sequence of length-delimited buffers, which enables the sender to</td><td> </td><td class="right">   sequence of length-delimited buffers, which enables the sender to</td><td class="lineno" valign="top"></td></tr>
    906864      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    907       <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr>
     865      <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 38, line 28</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 38, line 28</em></th><td></td></tr>
    908866      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    909867      <tr><td class="lineno" valign="top"></td><td class="left">   The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td> </td><td class="right">   The "deflate" coding is a "zlib" data format [RFC1950] containing a</td><td class="lineno" valign="top"></td></tr>
     
    916874      <tr><td class="lineno" valign="top"></td><td class="left">4.2.3.  Gzip Coding</td><td> </td><td class="right">4.2.3.  Gzip Coding</td><td class="lineno" valign="top"></td></tr>
    917875      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    918       <tr><td><a name="diff0051" /></td></tr>
     876      <tr><td><a name="diff0048" /></td></tr>
    919877      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "gzip" coding is an LZ77 coding with a <span class="delete">32 bit CRC</span> that is</td><td> </td><td class="rblock">   The "gzip" coding is an LZ77 coding with a <span class="insert">32-bit Cyclic Redundancy</span></td><td class="lineno" valign="top"></td></tr>
    920878      <tr><td class="lineno" valign="top"></td><td class="lblock">   commonly produced by the gzip file compression program [RFC1952].  A</td><td> </td><td class="rblock"><span class="insert">   Check (CRC)</span> that is commonly produced by the gzip file compression</td><td class="lineno" valign="top"></td></tr>
     
    932890      <tr><td class="lineno" valign="top"></td><td class="left">   coding names, each allowing for optional parameters (as described in</td><td> </td><td class="right">   coding names, each allowing for optional parameters (as described in</td><td class="lineno" valign="top"></td></tr>
    933891      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    934       <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 48, line 5</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 48, line 5</em></th><td></td></tr>
    935       <tr><td class="lineno" valign="top"></td><td class="left">   optional port number of a recipient server or client that</td><td> </td><td class="right">   optional port number of a recipient server or client that</td><td class="lineno" valign="top"></td></tr>
    936       <tr><td class="lineno" valign="top"></td><td class="left">   subsequently forwarded the message.  However, if the real host is</td><td> </td><td class="right">   subsequently forwarded the message.  However, if the real host is</td><td class="lineno" valign="top"></td></tr>
    937       <tr><td class="lineno" valign="top"></td><td class="left">   considered to be sensitive information, a sender MAY replace it with</td><td> </td><td class="right">   considered to be sensitive information, a sender MAY replace it with</td><td class="lineno" valign="top"></td></tr>
    938       <tr><td class="lineno" valign="top"></td><td class="left">   a pseudonym.  If a port is not provided, a recipient MAY interpret</td><td> </td><td class="right">   a pseudonym.  If a port is not provided, a recipient MAY interpret</td><td class="lineno" valign="top"></td></tr>
    939       <tr><td class="lineno" valign="top"></td><td class="left">   that as meaning it was received on the default TCP port, if any, for</td><td> </td><td class="right">   that as meaning it was received on the default TCP port, if any, for</td><td class="lineno" valign="top"></td></tr>
    940       <tr><td class="lineno" valign="top"></td><td class="left">   the received-protocol.</td><td> </td><td class="right">   the received-protocol.</td><td class="lineno" valign="top"></td></tr>
    941       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    942       <tr><td class="lineno" valign="top"></td><td class="left">   A sender MAY generate comments in the Via header field to identify</td><td> </td><td class="right">   A sender MAY generate comments in the Via header field to identify</td><td class="lineno" valign="top"></td></tr>
    943       <tr><td class="lineno" valign="top"></td><td class="left">   the software of each recipient, analogous to the User-Agent and</td><td> </td><td class="right">   the software of each recipient, analogous to the User-Agent and</td><td class="lineno" valign="top"></td></tr>
    944       <tr><td class="lineno" valign="top"></td><td class="left">   Server header fields.  However, all comments in the Via field are</td><td> </td><td class="right">   Server header fields.  However, all comments in the Via field are</td><td class="lineno" valign="top"></td></tr>
    945       <tr><td><a name="diff0052" /></td></tr>
    946       <tr><td class="lineno" valign="top"></td><td class="lblock">   optional and a recipient MAY remove them prior to forwarding the</td><td> </td><td class="rblock">   optional<span class="insert">,</span> and a recipient MAY remove them prior to forwarding the</td><td class="lineno" valign="top"></td></tr>
    947       <tr><td class="lineno" valign="top"></td><td class="left">   message.</td><td> </td><td class="right">   message.</td><td class="lineno" valign="top"></td></tr>
    948       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    949       <tr><td class="lineno" valign="top"></td><td class="left">   For example, a request message could be sent from an HTTP/1.0 user</td><td> </td><td class="right">   For example, a request message could be sent from an HTTP/1.0 user</td><td class="lineno" valign="top"></td></tr>
    950       <tr><td class="lineno" valign="top"></td><td class="left">   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to</td><td> </td><td class="right">   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to</td><td class="lineno" valign="top"></td></tr>
    951       <tr><td class="lineno" valign="top"></td><td class="left">   forward the request to a public proxy at p.example.net, which</td><td> </td><td class="right">   forward the request to a public proxy at p.example.net, which</td><td class="lineno" valign="top"></td></tr>
    952       <tr><td class="lineno" valign="top"></td><td class="left">   completes the request by forwarding it to the origin server at</td><td> </td><td class="right">   completes the request by forwarding it to the origin server at</td><td class="lineno" valign="top"></td></tr>
    953       <tr><td class="lineno" valign="top"></td><td class="left">   www.example.com.  The request received by www.example.com would then</td><td> </td><td class="right">   www.example.com.  The request received by www.example.com would then</td><td class="lineno" valign="top"></td></tr>
    954       <tr><td class="lineno" valign="top"></td><td class="left">   have the following Via header field:</td><td> </td><td class="right">   have the following Via header field:</td><td class="lineno" valign="top"></td></tr>
    955       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    956       <tr><td class="lineno" valign="top"></td><td class="left">     Via: 1.0 fred, 1.1 p.example.net</td><td> </td><td class="right">     Via: 1.0 fred, 1.1 p.example.net</td><td class="lineno" valign="top"></td></tr>
    957       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    958892      <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>
    959893      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    967901      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    968902      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td> </td><td class="right">   A proxy MUST NOT transform the payload (Section 3.3 of [RFC7231]) of</td><td class="lineno" valign="top"></td></tr>
    969       <tr><td><a name="diff0053" /></td></tr>
     903      <tr><td><a name="diff0049" /></td></tr>
    970904      <tr><td class="lineno" valign="top"></td><td class="lblock">   a message that contains a no-transform <span class="delete">cache-c</span>ontrol directive</td><td> </td><td class="rblock">   a message that contains a no-transform <span class="insert">Cache-C</span>ontrol directive</td><td class="lineno" valign="top"></td></tr>
    971905      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 5.2 of [RFC7234]).</td><td> </td><td class="right">   (Section 5.2 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
    972906      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    973907      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MAY transform the payload of a message that does not contain</td><td> </td><td class="right">   A proxy MAY transform the payload of a message that does not contain</td><td class="lineno" valign="top"></td></tr>
    974       <tr><td><a name="diff0054" /></td></tr>
     908      <tr><td><a name="diff0050" /></td></tr>
    975909      <tr><td class="lineno" valign="top"></td><td class="lblock">   a no-transform <span class="delete">cache-c</span>ontrol directive.  A proxy that transforms a</td><td> </td><td class="rblock">   a no-transform <span class="insert">Cache-C</span>ontrol directive.  A proxy that transforms a</td><td class="lineno" valign="top"></td></tr>
    976910      <tr><td class="lineno" valign="top"></td><td class="left">   payload MUST add a Warning header field with the warn-code of 214</td><td> </td><td class="right">   payload MUST add a Warning header field with the warn-code of 214</td><td class="lineno" valign="top"></td></tr>
     
    982916      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    983917      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy SHOULD NOT modify header fields that provide information</td><td> </td><td class="right">   A proxy SHOULD NOT modify header fields that provide information</td><td class="lineno" valign="top"></td></tr>
    984       <tr><td><a name="diff0055" /></td></tr>
     918      <tr><td><a name="diff0051" /></td></tr>
    985919      <tr><td class="lineno" valign="top"></td><td class="lblock">   about the end<span class="delete"> </span>points of the communication chain, the resource state,</td><td> </td><td class="rblock">   about the endpoints of the communication chain, the resource state,</td><td class="lineno" valign="top"></td></tr>
    986920      <tr><td class="lineno" valign="top"></td><td class="left">   or the selected representation (other than the payload) unless the</td><td> </td><td class="right">   or the selected representation (other than the payload) unless the</td><td class="lineno" valign="top"></td></tr>
     
    990924      <tr><td class="lineno" valign="top"></td><td class="left">6.  Connection Management</td><td> </td><td class="right">6.  Connection Management</td><td class="lineno" valign="top"></td></tr>
    991925      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    992       <tr><td><a name="diff0056" /></td></tr>
     926      <tr><td><a name="diff0052" /></td></tr>
    993927      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP messaging is independent of the underlying <span class="delete">transport</span> or <span class="delete">session-</span></td><td> </td><td class="rblock">   HTTP messaging is independent of the underlying <span class="insert">transport-</span> or</td><td class="lineno" valign="top"></td></tr>
    994928      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   layer</span> connection protocol(s).  HTTP only presumes a reliable</td><td> </td><td class="rblock">   <span class="insert">session-layer</span> connection protocol(s).  HTTP only presumes a reliable</td><td class="lineno" valign="top"></td></tr>
     
    1013947      <tr><td class="lineno" valign="top"></td><td class="left">   per server endpoint.  Most servers are designed to maintain thousands</td><td> </td><td class="right">   per server endpoint.  Most servers are designed to maintain thousands</td><td class="lineno" valign="top"></td></tr>
    1014948      <tr><td class="lineno" valign="top"></td><td class="left">   of concurrent connections, while controlling request queues to enable</td><td> </td><td class="right">   of concurrent connections, while controlling request queues to enable</td><td class="lineno" valign="top"></td></tr>
    1015       <tr><td><a name="diff0057" /></td></tr>
     949      <tr><td><a name="diff0053" /></td></tr>
    1016950      <tr><td class="lineno" valign="top"></td><td class="lblock">   fair use and detect denial<span class="delete"> of </span>service attacks.</td><td> </td><td class="rblock">   fair use and detect denial<span class="insert">-of-</span>service attacks.</td><td class="lineno" valign="top"></td></tr>
    1017951      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    1037971      <tr><td class="lineno" valign="top"></td><td class="left">     connection-option = token</td><td> </td><td class="right">     connection-option = token</td><td class="lineno" valign="top"></td></tr>
    1038972      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1039       <tr><td><a name="diff0058" /></td></tr>
     973      <tr><td><a name="diff0054" /></td></tr>
    1040974      <tr><td class="lineno" valign="top"></td><td class="lblock">   Connection options are case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock">   Connection options are case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr>
    1041975      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    1061995      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1062996      <tr><td class="lineno" valign="top"></td><td class="left">   It is beyond the scope of this specification to describe how</td><td> </td><td class="right">   It is beyond the scope of this specification to describe how</td><td class="lineno" valign="top"></td></tr>
    1063       <tr><td><a name="diff0059" /></td></tr>
     997      <tr><td><a name="diff0055" /></td></tr>
    1064998      <tr><td class="lineno" valign="top"></td><td class="lblock">   connections are established via various transport or session-layer</td><td> </td><td class="rblock">   connections are established via various transport<span class="insert">-</span> or session-layer</td><td class="lineno" valign="top"></td></tr>
    1065999      <tr><td class="lineno" valign="top"></td><td class="left">   protocols.  Each connection applies to only one transport link.</td><td> </td><td class="right">   protocols.  Each connection applies to only one transport link.</td><td class="lineno" valign="top"></td></tr>
     
    10691003      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td> </td><td class="right">   HTTP/1.1 defaults to the use of "persistent connections", allowing</td><td class="lineno" valign="top"></td></tr>
    10701004      <tr><td class="lineno" valign="top"></td><td class="left">   multiple requests and responses to be carried over a single</td><td> </td><td class="right">   multiple requests and responses to be carried over a single</td><td class="lineno" valign="top"></td></tr>
    1071       <tr><td><a name="diff0060" /></td></tr>
     1005      <tr><td><a name="diff0056" /></td></tr>
    10721006      <tr><td class="lineno" valign="top"></td><td class="lblock">   connection.  The "close" connection<span class="delete">-</span>option is used to signal that a</td><td> </td><td class="rblock">   connection.  The "close" connection<span class="insert"> </span>option is used to signal that a</td><td class="lineno" valign="top"></td></tr>
    10731007      <tr><td class="lineno" valign="top"></td><td class="left">   connection will not persist after the current request/response.  HTTP</td><td> </td><td class="right">   connection will not persist after the current request/response.  HTTP</td><td class="lineno" valign="top"></td></tr>
     
    10781012      <tr><td class="lineno" valign="top"></td><td class="left">   Connection header field (if any):</td><td> </td><td class="right">   Connection header field (if any):</td><td class="lineno" valign="top"></td></tr>
    10791013      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1080       <tr><td><a name="diff0061" /></td></tr>
     1014      <tr><td><a name="diff0057" /></td></tr>
    10811015      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  If the <span class="delete">close</span> connection option is present, the connection will not</td><td> </td><td class="rblock">   o  If the <span class="insert">"close"</span> connection option is present, the connection will</td><td class="lineno" valign="top"></td></tr>
    10821016      <tr><td class="lineno" valign="top"></td><td class="lblock">      persist after the current response; else,</td><td> </td><td class="rblock">      not persist after the current response; else,</td><td class="lineno" valign="top"></td></tr>
     
    10931027      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10941028      <tr><td class="lineno" valign="top"></td><td class="left">   A client MAY send additional requests on a persistent connection</td><td> </td><td class="right">   A client MAY send additional requests on a persistent connection</td><td class="lineno" valign="top"></td></tr>
    1095       <tr><td><a name="diff0062" /></td></tr>
     1029      <tr><td><a name="diff0058" /></td></tr>
    10961030      <tr><td class="lineno" valign="top"></td><td class="lblock">   until it sends or receives a <span class="delete">close</span> connection option or receives an</td><td> </td><td class="rblock">   until it sends or receives a <span class="insert">"close"</span> connection option or receives an</td><td class="lineno" valign="top"></td></tr>
    10971031      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.0 response without a "keep-alive" connection option.</td><td> </td><td class="right">   HTTP/1.0 response without a "keep-alive" connection option.</td><td class="lineno" valign="top"></td></tr>
     
    11111045      <tr><td class="lineno" valign="top"></td><td class="left">   implemented by many HTTP/1.0 clients).</td><td> </td><td class="right">   implemented by many HTTP/1.0 clients).</td><td class="lineno" valign="top"></td></tr>
    11121046      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1113       <tr><td><a name="diff0063" /></td></tr>
     1047      <tr><td><a name="diff0059" /></td></tr>
    11141048      <tr><td class="lineno" valign="top"></td><td class="lblock">   See Appendix A.1.2 for more information on backward compatibility</td><td> </td><td class="rblock">   See Appendix A.1.2 for more information on backward<span class="insert">s</span> compatibility</td><td class="lineno" valign="top"></td></tr>
    11151049      <tr><td class="lineno" valign="top"></td><td class="left">   with HTTP/1.0 clients.</td><td> </td><td class="right">   with HTTP/1.0 clients.</td><td class="lineno" valign="top"></td></tr>
     
    11351069      <tr><td class="lineno" valign="top"></td><td class="left">   response).  A server MAY process a sequence of pipelined requests in</td><td> </td><td class="right">   response).  A server MAY process a sequence of pipelined requests in</td><td class="lineno" valign="top"></td></tr>
    11361070      <tr><td class="lineno" valign="top"></td><td class="left">   parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td> </td><td class="right">   parallel if they all have safe methods (Section 4.2.1 of [RFC7231]),</td><td class="lineno" valign="top"></td></tr>
    1137       <tr><td><a name="diff0064" /></td></tr>
     1071      <tr><td><a name="diff0060" /></td></tr>
    11381072      <tr><td class="lineno" valign="top"></td><td class="lblock">   but MUST send the corresponding responses in the same order that the</td><td> </td><td class="rblock">   but <span class="insert">it</span> MUST send the corresponding responses in the same order that</td><td class="lineno" valign="top"></td></tr>
    11391073      <tr><td class="lineno" valign="top"></td><td class="lblock">   requests were received.</td><td> </td><td class="rblock">   the requests were received.</td><td class="lineno" valign="top"></td></tr>
     
    11491083      <tr><td class="lineno" valign="top"></td><td class="left">   connection (see the TCP reset problem described in Section 6.6).</td><td> </td><td class="right">   connection (see the TCP reset problem described in Section 6.6).</td><td class="lineno" valign="top"></td></tr>
    11501084      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1151       <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 54, line 29</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 54, line 29</em></th><td></td></tr>
    1152       <tr><td class="lineno" valign="top"></td><td class="left">   agent(s) can recover accordingly.</td><td> </td><td class="right">   agent(s) can recover accordingly.</td><td class="lineno" valign="top"></td></tr>
    1153       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1154       <tr><td class="lineno" valign="top"></td><td class="left">6.4.  Concurrency</td><td> </td><td class="right">6.4.  Concurrency</td><td class="lineno" valign="top"></td></tr>
    1155       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1156       <tr><td class="lineno" valign="top"></td><td class="left">   A client ought to limit the number of simultaneous open connections</td><td> </td><td class="right">   A client ought to limit the number of simultaneous open connections</td><td class="lineno" valign="top"></td></tr>
    1157       <tr><td class="lineno" valign="top"></td><td class="left">   that it maintains to a given server.</td><td> </td><td class="right">   that it maintains to a given server.</td><td class="lineno" valign="top"></td></tr>
    1158       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1159       <tr><td class="lineno" valign="top"></td><td class="left">   Previous revisions of HTTP gave a specific number of connections as a</td><td> </td><td class="right">   Previous revisions of HTTP gave a specific number of connections as a</td><td class="lineno" valign="top"></td></tr>
    1160       <tr><td class="lineno" valign="top"></td><td class="left">   ceiling, but this was found to be impractical for many applications.</td><td> </td><td class="right">   ceiling, but this was found to be impractical for many applications.</td><td class="lineno" valign="top"></td></tr>
    1161       <tr><td class="lineno" valign="top"></td><td class="left">   As a result, this specification does not mandate a particular maximum</td><td> </td><td class="right">   As a result, this specification does not mandate a particular maximum</td><td class="lineno" valign="top"></td></tr>
    1162       <tr><td><a name="diff0065" /></td></tr>
    1163       <tr><td class="lineno" valign="top"></td><td class="lblock">   number of connections<span class="delete">, but instead</span> encourages clients to be</td><td> </td><td class="rblock">   number of connections<span class="insert"> but, instead,</span> encourages clients to be</td><td class="lineno" valign="top"></td></tr>
     1085      <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 54, line 40</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 54, line 40</em></th><td></td></tr>
    11641086      <tr><td class="lineno" valign="top"></td><td class="left">   conservative when opening multiple connections.</td><td> </td><td class="right">   conservative when opening multiple connections.</td><td class="lineno" valign="top"></td></tr>
    11651087      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11721094      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11731095      <tr><td class="lineno" valign="top"></td><td class="left">   Note that a server might reject traffic that it deems abusive or</td><td> </td><td class="right">   Note that a server might reject traffic that it deems abusive or</td><td class="lineno" valign="top"></td></tr>
    1174       <tr><td><a name="diff0066" /></td></tr>
     1096      <tr><td><a name="diff0061" /></td></tr>
    11751097      <tr><td class="lineno" valign="top"></td><td class="lblock">   characteristic of a denial<span class="delete"> of </span>service attack, such as an excessive</td><td> </td><td class="rblock">   characteristic of a denial<span class="insert">-of-</span>service attack, such as an excessive</td><td class="lineno" valign="top"></td></tr>
    11761098      <tr><td class="lineno" valign="top"></td><td class="left">   number of open connections from a single client.</td><td> </td><td class="right">   number of open connections from a single client.</td><td class="lineno" valign="top"></td></tr>
    11771099      <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><a name="diff0067" /></td></tr>
     1100      <tr><td><a name="diff0062" /></td></tr>
    11791101      <tr><td class="lineno" valign="top"></td><td class="lblock">6.5.  Failures and Time<span class="delete">-</span>outs</td><td> </td><td class="rblock">6.5.  Failures and Timeouts</td><td class="lineno" valign="top"></td></tr>
    11801102      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1181       <tr><td><a name="diff0068" /></td></tr>
     1103      <tr><td><a name="diff0063" /></td></tr>
    11821104      <tr><td class="lineno" valign="top"></td><td class="lblock">   Servers will usually have some time<span class="delete">-</span>out value beyond which they will</td><td> </td><td class="rblock">   Servers will usually have some timeout value beyond which they will</td><td class="lineno" valign="top"></td></tr>
    11831105      <tr><td class="lineno" valign="top"></td><td class="left">   no longer maintain an inactive connection.  Proxy servers might make</td><td> </td><td class="right">   no longer maintain an inactive connection.  Proxy servers might make</td><td class="lineno" valign="top"></td></tr>
     
    11851107      <tr><td class="lineno" valign="top"></td><td class="left">   more connections through the same proxy server.  The use of</td><td> </td><td class="right">   more connections through the same proxy server.  The use of</td><td class="lineno" valign="top"></td></tr>
    11861108      <tr><td class="lineno" valign="top"></td><td class="left">   persistent connections places no requirements on the length (or</td><td> </td><td class="right">   persistent connections places no requirements on the length (or</td><td class="lineno" valign="top"></td></tr>
    1187       <tr><td><a name="diff0069" /></td></tr>
     1109      <tr><td><a name="diff0064" /></td></tr>
    11881110      <tr><td class="lineno" valign="top"></td><td class="lblock">   existence) of this time<span class="delete">-</span>out for either the client or the server.</td><td> </td><td class="rblock">   existence) of this timeout for either the client or the server.</td><td class="lineno" valign="top"></td></tr>
    11891111      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1190       <tr><td><a name="diff0070" /></td></tr>
     1112      <tr><td><a name="diff0065" /></td></tr>
    11911113      <tr><td class="lineno" valign="top"></td><td class="lblock">   A client or server that wishes to time<span class="delete">-</span>out SHOULD issue a graceful</td><td> </td><td class="rblock">   A client or server that wishes to time<span class="insert"> </span>out SHOULD issue a graceful</td><td class="lineno" valign="top"></td></tr>
    11921114      <tr><td class="lineno" valign="top"></td><td class="left">   close on the connection.  Implementations SHOULD constantly monitor</td><td> </td><td class="right">   close on the connection.  Implementations SHOULD constantly monitor</td><td class="lineno" valign="top"></td></tr>
     
    12031125      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12041126      <tr><td class="lineno" valign="top"></td><td class="left">   A server SHOULD sustain persistent connections, when possible, and</td><td> </td><td class="right">   A server SHOULD sustain persistent connections, when possible, and</td><td class="lineno" valign="top"></td></tr>
    1205       <tr><td><a name="diff0071" /></td></tr>
     1127      <tr><td><a name="diff0066" /></td></tr>
    12061128      <tr><td class="lineno" valign="top"></td><td class="lblock">   allow the underlying transport's flow<span class="delete"> </span>control mechanisms to resolve</td><td> </td><td class="rblock">   allow the underlying transport's flow<span class="insert">-</span>control mechanisms to resolve</td><td class="lineno" valign="top"></td></tr>
    12071129      <tr><td class="lineno" valign="top"></td><td class="left">   temporary overloads, rather than terminate connections with the</td><td> </td><td class="right">   temporary overloads, rather than terminate connections with the</td><td class="lineno" valign="top"></td></tr>
     
    12161138      <tr><td class="lineno" valign="top"></td><td class="left">   the connection.</td><td> </td><td class="right">   the connection.</td><td class="lineno" valign="top"></td></tr>
    12171139      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1218       <tr><td><a name="diff0072" /></td></tr>
     1140      <tr><td><a name="diff0067" /></td></tr>
    12191141      <tr><td class="lineno" valign="top"></td><td class="lblock">6.6.  Tear<span class="delete">-</span>down</td><td> </td><td class="rblock">6.6.  Teardown</td><td class="lineno" valign="top"></td></tr>
    12201142      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12231145      <tr><td class="lineno" valign="top"></td><td class="left">   the connection after the current request/response pair.</td><td> </td><td class="right">   the connection after the current request/response pair.</td><td class="lineno" valign="top"></td></tr>
    12241146      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1225       <tr><td><a name="diff0073" /></td></tr>
     1147      <tr><td><a name="diff0068" /></td></tr>
    12261148      <tr><td class="lineno" valign="top"></td><td class="lblock">   A client that sends a <span class="delete">close</span> connection option MUST NOT send further</td><td> </td><td class="rblock">   A client that sends a <span class="insert">"close"</span> connection option MUST NOT send further</td><td class="lineno" valign="top"></td></tr>
    12271149      <tr><td class="lineno" valign="top"></td><td class="left">   requests on that connection (after the one containing close) and MUST</td><td> </td><td class="right">   requests on that connection (after the one containing close) and MUST</td><td class="lineno" valign="top"></td></tr>
     
    12291151      <tr><td class="lineno" valign="top"></td><td class="left">   corresponding to this request.</td><td> </td><td class="right">   corresponding to this request.</td><td class="lineno" valign="top"></td></tr>
    12301152      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1231       <tr><td><a name="diff0074" /></td></tr>
     1153      <tr><td><a name="diff0069" /></td></tr>
    12321154      <tr><td class="lineno" valign="top"></td><td class="lblock">   A server that receives a <span class="delete">close</span> connection option MUST initiate a</td><td> </td><td class="rblock">   A server that receives a <span class="insert">"close"</span> connection option MUST initiate a</td><td class="lineno" valign="top"></td></tr>
    12331155      <tr><td class="lineno" valign="top"></td><td class="left">   close of the connection (see below) after it sends the final response</td><td> </td><td class="right">   close of the connection (see below) after it sends the final response</td><td class="lineno" valign="top"></td></tr>
     
    12371159      <tr><td class="lineno" valign="top"></td><td class="left">   connection.</td><td> </td><td class="right">   connection.</td><td class="lineno" valign="top"></td></tr>
    12381160      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1239       <tr><td><a name="diff0075" /></td></tr>
     1161      <tr><td><a name="diff0070" /></td></tr>
    12401162      <tr><td class="lineno" valign="top"></td><td class="lblock">   A server that sends a <span class="delete">close</span> connection option MUST initiate a close</td><td> </td><td class="rblock">   A server that sends a <span class="insert">"close"</span> connection option MUST initiate a close</td><td class="lineno" valign="top"></td></tr>
    12411163      <tr><td class="lineno" valign="top"></td><td class="left">   of the connection (see below) after it sends the response containing</td><td> </td><td class="right">   of the connection (see below) after it sends the response containing</td><td class="lineno" valign="top"></td></tr>
     
    12431165      <tr><td class="lineno" valign="top"></td><td class="left">   that connection.</td><td> </td><td class="right">   that connection.</td><td class="lineno" valign="top"></td></tr>
    12441166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1245       <tr><td><a name="diff0076" /></td></tr>
     1167      <tr><td><a name="diff0071" /></td></tr>
    12461168      <tr><td class="lineno" valign="top"></td><td class="lblock">   A client that receives a <span class="delete">close</span> connection option MUST cease sending</td><td> </td><td class="rblock">   A client that receives a <span class="insert">"close"</span> connection option MUST cease sending</td><td class="lineno" valign="top"></td></tr>
    12471169      <tr><td class="lineno" valign="top"></td><td class="left">   requests on that connection and close the connection after reading</td><td> </td><td class="right">   requests on that connection and close the connection after reading</td><td class="lineno" valign="top"></td></tr>
     
    12531175      <tr><td class="lineno" valign="top"></td><td class="left">   a significant risk that the client will not be able to read the last</td><td> </td><td class="right">   a significant risk that the client will not be able to read the last</td><td class="lineno" valign="top"></td></tr>
    12541176      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP response.  If the server receives additional data from the</td><td> </td><td class="right">   HTTP response.  If the server receives additional data from the</td><td class="lineno" valign="top"></td></tr>
    1255       <tr><td><a name="diff0077" /></td></tr>
     1177      <tr><td><a name="diff0072" /></td></tr>
    12561178      <tr><td class="lineno" valign="top"></td><td class="lblock">   client on a fully<span class="delete">-</span>closed connection, such as another request that was</td><td> </td><td class="rblock">   client on a fully<span class="insert"> </span>closed connection, such as another request that was</td><td class="lineno" valign="top"></td></tr>
    12571179      <tr><td class="lineno" valign="top"></td><td class="left">   sent by the client before receiving the server's response, the</td><td> </td><td class="right">   sent by the client before receiving the server's response, the</td><td class="lineno" valign="top"></td></tr>
     
    12771199      <tr><td class="lineno" valign="top"></td><td class="left">   after the protocol change is entirely dependent upon the new</td><td> </td><td class="right">   after the protocol change is entirely dependent upon the new</td><td class="lineno" valign="top"></td></tr>
    12781200      <tr><td class="lineno" valign="top"></td><td class="left">   protocol(s) chosen.  However, immediately after sending the 101</td><td> </td><td class="right">   protocol(s) chosen.  However, immediately after sending the 101</td><td class="lineno" valign="top"></td></tr>
    1279       <tr><td><a name="diff0078" /></td></tr>
     1201      <tr><td><a name="diff0073" /></td></tr>
    12801202      <tr><td class="lineno" valign="top"></td><td class="lblock">   response, the server is expected to continue responding to the</td><td> </td><td class="rblock">   <span class="insert">(Switching Protocols)</span> response, the server is expected to continue</td><td class="lineno" valign="top"></td></tr>
    12811203      <tr><td class="lineno" valign="top"></td><td class="lblock">   original request as if it had received its equivalent within the new</td><td> </td><td class="rblock">   responding to the original request as if it had received its</td><td class="lineno" valign="top"></td></tr>
     
    12911213      <tr><td class="lineno" valign="top"></td><td class="left">   GET on the target resource.  This allows a connection to be upgraded</td><td> </td><td class="right">   GET on the target resource.  This allows a connection to be upgraded</td><td class="lineno" valign="top"></td></tr>
    12921214      <tr><td class="lineno" valign="top"></td><td class="left">   to protocols with the same semantics as HTTP without the latency cost</td><td> </td><td class="right">   to protocols with the same semantics as HTTP without the latency cost</td><td class="lineno" valign="top"></td></tr>
    1293       <tr><td><a name="diff0079" /></td></tr>
     1215      <tr><td><a name="diff0074" /></td></tr>
    12941216      <tr><td class="lineno" valign="top"></td><td class="lblock">   of an additional round<span class="delete">-</span>trip.  A server MUST NOT switch protocols</td><td> </td><td class="rblock">   of an additional round<span class="insert"> </span>trip.  A server MUST NOT switch protocols</td><td class="lineno" valign="top"></td></tr>
    12951217      <tr><td class="lineno" valign="top"></td><td class="left">   unless the received message semantics can be honored by the new</td><td> </td><td class="right">   unless the received message semantics can be honored by the new</td><td class="lineno" valign="top"></td></tr>
     
    13151237      <tr><td class="lineno" valign="top"></td><td class="left">   until it has completely sent the request message (i.e., the client</td><td> </td><td class="right">   until it has completely sent the request message (i.e., the client</td><td class="lineno" valign="top"></td></tr>
    13161238      <tr><td class="lineno" valign="top"></td><td class="left">   can't change the protocol it is sending in the middle of a message).</td><td> </td><td class="right">   can't change the protocol it is sending in the middle of a message).</td><td class="lineno" valign="top"></td></tr>
    1317       <tr><td><a name="diff0080" /></td></tr>
     1239      <tr><td><a name="diff0075" /></td></tr>
    13181240      <tr><td class="lineno" valign="top"></td><td class="lblock">   If a server receives both Upgrade and an Expect header field with the</td><td> </td><td class="rblock">   If a server receives both <span class="insert">an</span> Upgrade and an Expect header field with</td><td class="lineno" valign="top"></td></tr>
    13191241      <tr><td class="lineno" valign="top"></td><td class="lblock">   "100-continue" expectation (Section 5.1.1 of [RFC7231]), the server</td><td> </td><td class="rblock">   the "100-continue" expectation (Section 5.1.1 of [RFC7231]), the</td><td class="lineno" valign="top"></td></tr>
     
    13421264      <tr><td class="lineno" valign="top"></td><td class="left">   ignore a reasonable number of empty list elements: enough to handle</td><td> </td><td class="right">   ignore a reasonable number of empty list elements: enough to handle</td><td class="lineno" valign="top"></td></tr>
    13431265      <tr><td class="lineno" valign="top"></td><td class="left">   common mistakes by senders that merge values, but not so much that</td><td> </td><td class="right">   common mistakes by senders that merge values, but not so much that</td><td class="lineno" valign="top"></td></tr>
    1344       <tr><td><a name="diff0081" /></td></tr>
     1266      <tr><td><a name="diff0076" /></td></tr>
    13451267      <tr><td class="lineno" valign="top"></td><td class="lblock">   they could be used as a denial<span class="delete"> of </span>service mechanism.  In other words,</td><td> </td><td class="rblock">   they could be used as a denial<span class="insert">-of-</span>service mechanism.  In other words,</td><td class="lineno" valign="top"></td></tr>
    13461268      <tr><td class="lineno" valign="top"></td><td class="left">   a recipient MUST accept lists that satisfy the following syntax:</td><td> </td><td class="right">   a recipient MUST accept lists that satisfy the following syntax:</td><td class="lineno" valign="top"></td></tr>
     
    13561278      <tr><td class="lineno" valign="top"></td><td class="left">     example-list-elmt = token ; see Section 3.2.6</td><td> </td><td class="right">     example-list-elmt = token ; see Section 3.2.6</td><td class="lineno" valign="top"></td></tr>
    13571279      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1358       <tr><td><a name="diff0082" /></td></tr>
     1280      <tr><td><a name="diff0077" /></td></tr>
    13591281      <tr><td class="lineno" valign="top"></td><td class="lblock">   Then the following are valid values for example-list (not including</td><td> </td><td class="rblock">   Then<span class="insert">,</span> the following are valid values for example-list (not including</td><td class="lineno" valign="top"></td></tr>
    13601282      <tr><td class="lineno" valign="top"></td><td class="left">   the double quotes, which are present for delimitation only):</td><td> </td><td class="right">   the double quotes, which are present for delimitation only):</td><td class="lineno" valign="top"></td></tr>
     
    13781300      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Header Field Registration</td><td> </td><td class="right">8.1.  Header Field Registration</td><td class="lineno" valign="top"></td></tr>
    13791301      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1380       <tr><td><a name="diff0083" /></td></tr>
     1302      <tr><td><a name="diff0078" /></td></tr>
    13811303      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock">   HTTP header fields are registered within the <span class="insert">"Message Header" field</span></td><td class="lineno" valign="top"></td></tr>
    13821304      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry</span> maintained at</td><td> </td><td class="rblock"><span class="insert">   registry</span> maintained at</td><td class="lineno" valign="top"></td></tr>
    13831305      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/message-headers/&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/message-headers/&gt;.</td><td class="lineno" valign="top"></td></tr>
    13841306      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1385       <tr><td><a name="diff0084" /></td></tr>
     1307      <tr><td><a name="diff0079" /></td></tr>
    13861308      <tr><td class="lineno" valign="top"></td><td class="lblock">   This document defines the following HTTP header fields, so <span class="delete">their</span></td><td> </td><td class="rblock">   This document defines the following HTTP header fields, so <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
    13871309      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   associated</span> registry <span class="delete">entries shall be</span> updated <span class="delete">according to the</span></td><td> </td><td class="rblock"><span class="insert">   "Permanent Message Header Field Names"</span> registry <span class="insert">has been</span> updated</td><td class="lineno" valign="top"></td></tr>
     
    14011323      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+---------------+</td><td> </td><td class="right">   +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr>
    14021324      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1403       <tr><td><a name="diff0085" /></td></tr>
     1325      <tr><td><a name="diff0080" /></td></tr>
    14041326      <tr><td class="lineno" valign="top"></td><td class="lblock">   Furthermore, the header field-name "Close" <span class="delete">shall be</span> registered as</td><td> </td><td class="rblock">   Furthermore, the header field-name "Close" <span class="insert">has been</span> registered as</td><td class="lineno" valign="top"></td></tr>
    14051327      <tr><td class="lineno" valign="top"></td><td class="left">   "reserved", since using that name as an HTTP header field might</td><td> </td><td class="right">   "reserved", since using that name as an HTTP header field might</td><td class="lineno" valign="top"></td></tr>
     
    14211343      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/uri-schemes/&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/uri-schemes/&gt;.</td><td class="lineno" valign="top"></td></tr>
    14221344      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1423       <tr><td><a name="diff0086" /></td></tr>
     1345      <tr><td><a name="diff0081" /></td></tr>
    14241346      <tr><td class="lineno" valign="top"></td><td class="lblock">   This document defines the following URI schemes, so <span class="delete">their associated</span></td><td> </td><td class="rblock">   This document defines the following URI schemes, so <span class="insert">the "Permanent</span></td><td class="lineno" valign="top"></td></tr>
    14251347      <tr><td class="lineno" valign="top"></td><td class="lblock">   registry <span class="delete">entries shall be</span> updated <span class="delete">according to the permanent</span></td><td> </td><td class="rblock"><span class="insert">   URI Schemes"</span> registry <span class="insert">has been</span> updated <span class="insert">accordingly.</span></td><td class="lineno" valign="top"></td></tr>
     
    14391361      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    14401362      <tr><td class="lineno" valign="top"></td><td class="left">   This document serves as the specification for the Internet media</td><td> </td><td class="right">   This document serves as the specification for the Internet media</td><td class="lineno" valign="top"></td></tr>
    1441       <tr><td><a name="diff0087" /></td></tr>
     1363      <tr><td><a name="diff0082" /></td></tr>
    14421364      <tr><td class="lineno" valign="top"></td><td class="lblock">   types "message/http" and "application/http".  The following <span class="delete">is to be</span></td><td> </td><td class="rblock">   types "message/http" and "application/http".  The following <span class="insert">has been</span></td><td class="lineno" valign="top"></td></tr>
    14431365      <tr><td class="lineno" valign="top"></td><td class="left">   registered with IANA.</td><td> </td><td class="right">   registered with IANA.</td><td class="lineno" valign="top"></td></tr>
     
    14631385      <tr><td class="lineno" valign="top"></td><td class="left">      Macintosh file type code(s):  N/A</td><td> </td><td class="right">      Macintosh file type code(s):  N/A</td><td class="lineno" valign="top"></td></tr>
    14641386      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1465       <tr><td><a name="diff0088" /></td></tr>
     1387      <tr><td><a name="diff0083" /></td></tr>
    14661388      <tr><td class="lineno" valign="top"></td><td class="lblock">   Person and email address to contact for further information:  See</td><td> </td><td class="rblock">   Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr>
    14671389      <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">Authors</span> Section.</td><td> </td><td class="rblock">      See <span class="insert">Authors' Addresses</span>  Section.</td><td class="lineno" valign="top"></td></tr>
     
    14711393      <tr><td class="lineno" valign="top"></td><td class="left">   Restrictions on usage:  N/A</td><td> </td><td class="right">   Restrictions on usage:  N/A</td><td class="lineno" valign="top"></td></tr>
    14721394      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1473       <tr><td><a name="diff0089" /></td></tr>
     1395      <tr><td><a name="diff0084" /></td></tr>
    14741396      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author:  See Authors Section.</td><td> </td><td class="rblock">   Author:  See Authors<span class="insert">' Addresses</span> Section.</td><td class="lineno" valign="top"></td></tr>
    14751397      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    14951417      <tr><td class="lineno" valign="top"></td><td class="left">   Encoding considerations:  HTTP messages enclosed by this type are in</td><td> </td><td class="right">   Encoding considerations:  HTTP messages enclosed by this type are in</td><td class="lineno" valign="top"></td></tr>
    14961418      <tr><td class="lineno" valign="top"></td><td class="left">      "binary" format; use of an appropriate Content-Transfer-Encoding</td><td> </td><td class="right">      "binary" format; use of an appropriate Content-Transfer-Encoding</td><td class="lineno" valign="top"></td></tr>
    1497       <tr><td><a name="diff0090" /></td></tr>
     1419      <tr><td><a name="diff0085" /></td></tr>
    14981420      <tr><td class="lineno" valign="top"></td><td class="lblock">      is required when transmitted via <span class="delete">E-</span>mail.</td><td> </td><td class="rblock">      is required when transmitted via <span class="insert">e</span>mail.</td><td class="lineno" valign="top"></td></tr>
    14991421      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    15191441      <tr><td class="lineno" valign="top"></td><td class="left">      Macintosh file type code(s):  N/A</td><td> </td><td class="right">      Macintosh file type code(s):  N/A</td><td class="lineno" valign="top"></td></tr>
    15201442      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1521       <tr><td><a name="diff0091" /></td></tr>
     1443      <tr><td><a name="diff0086" /></td></tr>
    15221444      <tr><td class="lineno" valign="top"></td><td class="lblock">   Person and email address to contact for further information:  See</td><td> </td><td class="rblock">   Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr>
    15231445      <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">Authors</span> Section.</td><td> </td><td class="rblock">      See <span class="insert">Authors' Addresses</span> Section.</td><td class="lineno" valign="top"></td></tr>
     
    15271449      <tr><td class="lineno" valign="top"></td><td class="left">   Restrictions on usage:  N/A</td><td> </td><td class="right">   Restrictions on usage:  N/A</td><td class="lineno" valign="top"></td></tr>
    15281450      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1529       <tr><td><a name="diff0092" /></td></tr>
     1451      <tr><td><a name="diff0087" /></td></tr>
    15301452      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author:  See Authors Section.</td><td> </td><td class="rblock">   Author:  See Authors<span class="insert">' Addresses</span> Section.</td><td class="lineno" valign="top"></td></tr>
    15311453      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    15341456      <tr><td class="lineno" valign="top"></td><td class="left">8.4.  Transfer Coding Registry</td><td> </td><td class="right">8.4.  Transfer Coding Registry</td><td class="lineno" valign="top"></td></tr>
    15351457      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1536       <tr><td><a name="diff0093" /></td></tr>
     1458      <tr><td><a name="diff0088" /></td></tr>
    15371459      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Transfer <span class="delete">Coding Registry</span> defines the <span class="delete">name space</span> for transfer</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Transfer <span class="insert">Coding" registry</span> defines the <span class="insert">namespace</span> for</td><td class="lineno" valign="top"></td></tr>
    15381460      <tr><td class="lineno" valign="top"></td><td class="lblock">   coding names.  It is maintained at</td><td> </td><td class="rblock">   transfer coding names.  It is maintained at</td><td class="lineno" valign="top"></td></tr>
     
    15531475      <tr><td class="lineno" valign="top"></td><td class="left">   codings defined in Section 4.2.</td><td> </td><td class="right">   codings defined in Section 4.2.</td><td class="lineno" valign="top"></td></tr>
    15541476      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1555       <tr><td><a name="diff0094" /></td></tr>
     1477      <tr><td><a name="diff0089" /></td></tr>
    15561478      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
    15571479      <tr><td class="lineno" valign="top"></td><td class="lblock">   Section 4.1 of [RFC5226]), and MUST conform to the purpose of</td><td> </td><td class="rblock">   4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding</td><td class="lineno" valign="top"></td></tr>
     
    15631485      <tr><td class="lineno" valign="top"></td><td class="left">8.4.2.  Registration</td><td> </td><td class="right">8.4.2.  Registration</td><td class="lineno" valign="top"></td></tr>
    15641486      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1565       <tr><td><a name="diff0095" /></td></tr>
     1487      <tr><td><a name="diff0090" /></td></tr>
    15661488      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP Transfer Coding Registry shall be</span> updated with the</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Transfer Coding Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    15671489      <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>
     
    15821504      <tr><td class="lineno" valign="top"></td><td class="left">8.5.  Content Coding Registration</td><td> </td><td class="right">8.5.  Content Coding Registration</td><td class="lineno" valign="top"></td></tr>
    15831505      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1584       <tr><td><a name="diff0096" /></td></tr>
     1506      <tr><td><a name="diff0091" /></td></tr>
    15851507      <tr><td class="lineno" valign="top"></td><td class="lblock">   IANA maintains the <span class="delete">registry of HTTP Content Codings</span> at</td><td> </td><td class="rblock">   IANA maintains the <span class="insert">"HTTP Content Coding Registry"</span> at</td><td class="lineno" valign="top"></td></tr>
    15861508      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td class="lineno" valign="top"></td></tr>
    15871509      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1588       <tr><td><a name="diff0097" /></td></tr>
     1510      <tr><td><a name="diff0092" /></td></tr>
    15891511      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP Content Codings Registry shall be</span> updated with the</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Content Codings Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    15901512      <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>
     
    16041526      <tr><td class="lineno" valign="top"></td><td class="left">8.6.  Upgrade Token Registry</td><td> </td><td class="right">8.6.  Upgrade Token Registry</td><td class="lineno" valign="top"></td></tr>
    16051527      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1606       <tr><td><a name="diff0098" /></td></tr>
     1528      <tr><td><a name="diff0093" /></td></tr>
    16071529      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Upgrade Token <span class="delete">Registry</span> defines the <span class="delete">name space</span> for <span class="delete">protocol-</span></td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Upgrade Token <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr>
    16081530      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   name</span> tokens used to identify protocols in the Upgrade header field.</td><td> </td><td class="rblock">   defines the <span class="insert">namespace</span> for <span class="insert">protocol-name</span> tokens used to identify</td><td class="lineno" valign="top"></td></tr>
     
    16301552      <tr><td class="lineno" valign="top"></td><td class="left">8.6.2.  Upgrade Token Registration</td><td> </td><td class="right">8.6.2.  Upgrade Token Registration</td><td class="lineno" valign="top"></td></tr>
    16311553      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1632       <tr><td><a name="diff0099" /></td></tr>
     1554      <tr><td><a name="diff0094" /></td></tr>
    16331555      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP" entry in the <span class="delete">HTTP</span> Upgrade <span class="delete">Token Registry</span> shall be updated</td><td> </td><td class="rblock">   The "HTTP" entry in the <span class="insert">"HTTP</span> Upgrade <span class="insert">Token" registry</span> shall be</td><td class="lineno" valign="top"></td></tr>
    16341556      <tr><td class="lineno" valign="top"></td><td class="lblock">   with the registration below:</td><td> </td><td class="rblock">   updated with the registration below:</td><td class="lineno" valign="top"></td></tr>
     
    16551577      <tr><td class="lineno" valign="top"></td><td class="left">   Domain Name Service (DNS), and the hierarchy of servers from which it</td><td> </td><td class="right">   Domain Name Service (DNS), and the hierarchy of servers from which it</td><td class="lineno" valign="top"></td></tr>
    16561578      <tr><td class="lineno" valign="top"></td><td class="left">   obtains resolution results, could impact the authenticity of address</td><td> </td><td class="right">   obtains resolution results, could impact the authenticity of address</td><td class="lineno" valign="top"></td></tr>
    1657       <tr><td><a name="diff0100" /></td></tr>
     1579      <tr><td><a name="diff0095" /></td></tr>
    16581580      <tr><td class="lineno" valign="top"></td><td class="lblock">   mappings; <span class="delete">DNSSEC</span> ([RFC4033]) is one way to improve authenticity.</td><td> </td><td class="rblock">   mappings; <span class="insert">DNS Security Extensions (DNSSEC)</span> ([RFC4033]) is one way to</td><td class="lineno" valign="top"></td></tr>
    16591581      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   improve authenticity.</td><td class="lineno" valign="top"></td></tr>
     
    16731595      <tr><td class="lineno" valign="top"></td><td class="left">9.2.  Risks of Intermediaries</td><td> </td><td class="right">9.2.  Risks of Intermediaries</td><td class="lineno" valign="top"></td></tr>
    16741596      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1675       <tr><td><a name="diff0101" /></td></tr>
     1597      <tr><td><a name="diff0096" /></td></tr>
    16761598      <tr><td class="lineno" valign="top"></td><td class="lblock">   By their very nature, HTTP intermediaries are <span class="delete">men-in-the-middle, and</span></td><td> </td><td class="rblock">   By their very nature, HTTP intermediaries are <span class="insert">men in the middle and,</span></td><td class="lineno" valign="top"></td></tr>
    16771599      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   thus</span> represent an opportunity for man-in-the-middle attacks.</td><td> </td><td class="rblock"><span class="insert">   thus,</span> represent an opportunity for man-in-the-middle attacks.</td><td class="lineno" valign="top"></td></tr>
     
    16981620      <tr><td class="lineno" valign="top"></td><td class="left">   and body chunks.  Failure to limit such processing can result in</td><td> </td><td class="right">   and body chunks.  Failure to limit such processing can result in</td><td class="lineno" valign="top"></td></tr>
    16991621      <tr><td class="lineno" valign="top"></td><td class="left">   buffer overflows, arithmetic overflows, or increased vulnerability to</td><td> </td><td class="right">   buffer overflows, arithmetic overflows, or increased vulnerability to</td><td class="lineno" valign="top"></td></tr>
    1700       <tr><td><a name="diff0102" /></td></tr>
     1622      <tr><td><a name="diff0097" /></td></tr>
    17011623      <tr><td class="lineno" valign="top"></td><td class="lblock">   denial<span class="delete"> of </span>service attacks.</td><td> </td><td class="rblock">   denial<span class="insert">-of-</span>service attacks.</td><td class="lineno" valign="top"></td></tr>
    17021624      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    17221644      <tr><td class="lineno" valign="top"></td><td class="left">   such information is detected by the protocol to be incomplete,</td><td> </td><td class="right">   such information is detected by the protocol to be incomplete,</td><td class="lineno" valign="top"></td></tr>
    17231645      <tr><td class="lineno" valign="top"></td><td class="left">   expired, or corrupted during transfer.  Such mechanisms might be</td><td> </td><td class="right">   expired, or corrupted during transfer.  Such mechanisms might be</td><td class="lineno" valign="top"></td></tr>
    1724       <tr><td><a name="diff0103" /></td></tr>
     1646      <tr><td><a name="diff0098" /></td></tr>
    17251647      <tr><td class="lineno" valign="top"></td><td class="lblock">   selectively enabled via user<span class="delete"> </span>agent extensions or the presence of</td><td> </td><td class="rblock">   selectively enabled via user<span class="insert">-</span>agent extensions or the presence of</td><td class="lineno" valign="top"></td></tr>
    17261648      <tr><td class="lineno" valign="top"></td><td class="left">   message integrity metadata in a response.  At a minimum, user agents</td><td> </td><td class="right">   message integrity metadata in a response.  At a minimum, user agents</td><td class="lineno" valign="top"></td></tr>
     
    17461668      <tr><td class="lineno" valign="top"></td><td class="left">   securely stored and appropriate guidelines followed for its analysis.</td><td> </td><td class="right">   securely stored and appropriate guidelines followed for its analysis.</td><td class="lineno" valign="top"></td></tr>
    17471669      <tr><td class="lineno" valign="top"></td><td class="left">   Anonymization of personal information within individual entries</td><td> </td><td class="right">   Anonymization of personal information within individual entries</td><td class="lineno" valign="top"></td></tr>
    1748       <tr><td><a name="diff0104" /></td></tr>
     1670      <tr><td><a name="diff0099" /></td></tr>
    17491671      <tr><td class="lineno" valign="top"></td><td class="lblock">   helps, but is generally not sufficient to prevent real log traces</td><td> </td><td class="rblock">   helps, but i<span class="insert">t i</span>s generally not sufficient to prevent real log traces</td><td class="lineno" valign="top"></td></tr>
    17501672      <tr><td class="lineno" valign="top"></td><td class="left">   from being re-identified based on correlation with other access</td><td> </td><td class="right">   from being re-identified based on correlation with other access</td><td class="lineno" valign="top"></td></tr>
     
    17641686      <tr><td class="lineno" valign="top"></td><td class="left">   into RFC 1945, RFC 2068, RFC 2145, and RFC 2616, including</td><td> </td><td class="right">   into RFC 1945, RFC 2068, RFC 2145, and RFC 2616, including</td><td class="lineno" valign="top"></td></tr>
    17651687      <tr><td class="lineno" valign="top"></td><td class="left">   substantial contributions made by the previous authors, editors, and</td><td> </td><td class="right">   substantial contributions made by the previous authors, editors, and</td><td class="lineno" valign="top"></td></tr>
    1766       <tr><td><a name="diff0105" /></td></tr>
     1688      <tr><td><a name="diff0100" /></td></tr>
    17671689      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">working group c</span>hairs: Tim Berners-Lee, Ari Luotonen, Roy T. Fielding,</td><td> </td><td class="rblock">   <span class="insert">Working Group C</span>hairs: Tim Berners-Lee, Ari Luotonen, Roy T. Fielding,</td><td class="lineno" valign="top"></td></tr>
    17681690      <tr><td class="lineno" valign="top"></td><td class="left">   Henrik Frystyk Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter,</td><td> </td><td class="right">   Henrik Frystyk Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter,</td><td class="lineno" valign="top"></td></tr>
    1769       <tr><td><a name="diff0106" /></td></tr>
     1691      <tr><td><a name="diff0101" /></td></tr>
    17701692      <tr><td class="lineno" valign="top"></td><td class="lblock">   and Paul J. Leach.  Mark Nottingham oversaw this effort as <span class="delete">working</span></td><td> </td><td class="rblock">   and Paul J. Leach.  Mark Nottingham oversaw this effort as <span class="insert">Working</span></td><td class="lineno" valign="top"></td></tr>
    17711693      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   group chair.</span></td><td> </td><td class="rblock"><span class="insert">   Group Chair.</span></td><td class="lineno" valign="top"></td></tr>
     
    17921714      <tr><td class="lineno" valign="top"></td><td class="left">11.1.  Normative References</td><td> </td><td class="right">11.1.  Normative References</td><td class="lineno" valign="top"></td></tr>
    17931715      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1794       <tr><td><a name="diff0107" /></td></tr>
     1716      <tr><td><a name="diff0102" /></td></tr>
    17951717      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">[RFC0793]     Postel, J., "Transmission Control Protocol", STD 7,</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    17961718      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 RFC 793, September 1981.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    18181740      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7231]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
    18191741      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Semantics and Content",</td><td class="lineno" valign="top"></td></tr>
    1820       <tr><td><a name="diff0108" /></td></tr>
     1742      <tr><td><a name="diff0103" /></td></tr>
    18211743      <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p2-semantics-latest (work in</span></td><td> </td><td class="rblock">                 <span class="insert">RFC 7231,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    18221744      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    18241746      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
    18251747      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td class="lineno" valign="top"></td></tr>
    1826       <tr><td><a name="diff0109" /></td></tr>
     1748      <tr><td><a name="diff0104" /></td></tr>
    18271749      <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">                 <span class="insert">RFC 7232,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    18281750      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    18301752      <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>
    18311753      <tr><td class="lineno" valign="top"></td><td class="left">                 "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td> </td><td class="right">                 "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td class="lineno" valign="top"></td></tr>
    1832       <tr><td><a name="diff0110" /></td></tr>
     1754      <tr><td><a name="diff0105" /></td></tr>
    18331755      <tr><td class="lineno" valign="top"></td><td class="lblock">                 Requests", <span class="delete">draft-ietf-httpbis-p5-range-latest (work in</span></td><td> </td><td class="rblock">                 Requests", <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    18341756      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    18361758      <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>
    18371759      <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>
    1838       <tr><td><a name="diff0111" /></td></tr>
     1760      <tr><td><a name="diff0106" /></td></tr>
    18391761      <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>
    18401762      <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>
     
    18421764      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="right">   [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td class="lineno" valign="top"></td></tr>
    18431765      <tr><td class="lineno" valign="top"></td><td class="left">                 Transfer Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="right">                 Transfer Protocol (HTTP/1.1): Authentication",</td><td class="lineno" valign="top"></td></tr>
    1844       <tr><td><a name="diff0112" /></td></tr>
     1766      <tr><td><a name="diff0107" /></td></tr>
    18451767      <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">                 <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    18461768      <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>
     
    18521774      <tr><td class="lineno" valign="top"></td><td class="left">                 Interchange", ANSI X3.4, 1986.</td><td> </td><td class="right">                 Interchange", ANSI X3.4, 1986.</td><td class="lineno" valign="top"></td></tr>
    18531775      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1854       <tr><td><a name="diff0113" /></td></tr>
     1776      <tr><td><a name="diff0108" /></td></tr>
    18551777      <tr><td class="lineno" valign="top"></td><td class="lblock">   [Welch]       Welch, T., "A Technique for High<span class="delete"> </span>Performance Data</td><td> </td><td class="rblock">   [Welch]       Welch, T., "A Technique for High<span class="insert">-</span>Performance Data</td><td class="lineno" valign="top"></td></tr>
    18561778      <tr><td class="lineno" valign="top"></td><td class="left">                 Compression", IEEE Computer 17(6), June 1984.</td><td> </td><td class="right">                 Compression", IEEE Computer 17(6), June 1984.</td><td class="lineno" valign="top"></td></tr>
     
    18761798      <tr><td class="lineno" valign="top"></td><td class="left">   effects of hierarchical proxies, caching, the need for persistent</td><td> </td><td class="right">   effects of hierarchical proxies, caching, the need for persistent</td><td class="lineno" valign="top"></td></tr>
    18771799      <tr><td class="lineno" valign="top"></td><td class="left">   connections, or name-based virtual hosts.  The proliferation of</td><td> </td><td class="right">   connections, or name-based virtual hosts.  The proliferation of</td><td class="lineno" valign="top"></td></tr>
    1878       <tr><td><a name="diff0114" /></td></tr>
     1800      <tr><td><a name="diff0109" /></td></tr>
    18791801      <tr><td class="lineno" valign="top"></td><td class="lblock">   incompletely<span class="delete">-</span>implemented applications calling themselves "HTTP/1.0"</td><td> </td><td class="rblock">   incompletely<span class="insert"> </span>implemented applications calling themselves "HTTP/1.0"</td><td class="lineno" valign="top"></td></tr>
    18801802      <tr><td class="lineno" valign="top"></td><td class="left">   further necessitated a protocol version change in order for two</td><td> </td><td class="right">   further necessitated a protocol version change in order for two</td><td class="lineno" valign="top"></td></tr>
     
    18851807      <tr><td class="lineno" valign="top"></td><td class="left">   requirements that enable reliable implementations, adding only those</td><td> </td><td class="right">   requirements that enable reliable implementations, adding only those</td><td class="lineno" valign="top"></td></tr>
    18861808      <tr><td class="lineno" valign="top"></td><td class="left">   features that can either be safely ignored by an HTTP/1.0 recipient</td><td> </td><td class="right">   features that can either be safely ignored by an HTTP/1.0 recipient</td><td class="lineno" valign="top"></td></tr>
    1887       <tr><td><a name="diff0115" /></td></tr>
     1809      <tr><td><a name="diff0110" /></td></tr>
    18881810      <tr><td class="lineno" valign="top"></td><td class="lblock">   or only sent when communicating with a party advertising conformance</td><td> </td><td class="rblock">   or only <span class="insert">be</span> sent when communicating with a party advertising</td><td class="lineno" valign="top"></td></tr>
    18891811      <tr><td class="lineno" valign="top"></td><td class="lblock">   with HTTP/1.1.</td><td> </td><td class="rblock">   conformance with HTTP/1.1.</td><td class="lineno" valign="top"></td></tr>
     
    19101832      <tr><td class="lineno" valign="top"></td><td class="left">   and HTTP/1.1.</td><td> </td><td class="right">   and HTTP/1.1.</td><td class="lineno" valign="top"></td></tr>
    19111833      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1912       <tr><td><a name="diff0116" /></td></tr>
     1834      <tr><td><a name="diff0111" /></td></tr>
    19131835      <tr><td class="lineno" valign="top"></td><td class="lblock">A.1.1.  Multi<span class="delete">-</span>homed Web Servers</td><td> </td><td class="rblock">A.1.1.  Multihomed Web Servers</td><td class="lineno" valign="top"></td></tr>
    19141836      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    19341856      <tr><td class="lineno" valign="top"></td><td class="left">A.2.  Changes from RFC 2616</td><td> </td><td class="right">A.2.  Changes from RFC 2616</td><td class="lineno" valign="top"></td></tr>
    19351857      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1936       <tr><td><a name="diff0117" /></td></tr>
     1858      <tr><td><a name="diff0112" /></td></tr>
    19371859      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP's approach to error handling has been explained<span class="delete">.  (Section 2.5)</span></td><td> </td><td class="rblock">   HTTP's approach to error handling has been explained<span class="insert"> (Section 2.5).</span></td><td class="lineno" valign="top"></td></tr>
    19381860      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1939       <tr><td><a name="diff0118" /></td></tr>
     1861      <tr><td><a name="diff0113" /></td></tr>
    19401862      <tr><td class="lineno" valign="top"></td><td class="lblock">   The HTTP-version ABNF production has been clarified to be <span class="delete">case-</span></td><td> </td><td class="rblock">   The HTTP-version ABNF production has been clarified to be <span class="insert">case</span></td><td class="lineno" valign="top"></td></tr>
    19411863      <tr><td class="lineno" valign="top"></td><td class="lblock">   sensitive.  Additionally, version numbers <span class="delete">has</span> been restricted to</td><td> </td><td class="rblock">   sensitive.  Additionally, version numbers <span class="insert">have</span> been restricted to</td><td class="lineno" valign="top"></td></tr>
    19421864      <tr><td class="lineno" valign="top"></td><td class="left">   single digits, due to the fact that implementations are known to</td><td> </td><td class="right">   single digits, due to the fact that implementations are known to</td><td class="lineno" valign="top"></td></tr>
    1943       <tr><td><a name="diff0119" /></td></tr>
     1865      <tr><td><a name="diff0114" /></td></tr>
    19441866      <tr><td class="lineno" valign="top"></td><td class="lblock">   handle multi-digit version numbers incorrectly<span class="delete">.  (Section 2.6)</span></td><td> </td><td class="rblock">   handle multi-digit version numbers incorrectly<span class="insert"> (Section 2.6).</span></td><td class="lineno" valign="top"></td></tr>
    19451867      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19461868      <tr><td class="lineno" valign="top"></td><td class="left">   Userinfo (i.e., username and password) are now disallowed in HTTP and</td><td> </td><td class="right">   Userinfo (i.e., username and password) are now disallowed in HTTP and</td><td class="lineno" valign="top"></td></tr>
    19471869      <tr><td class="lineno" valign="top"></td><td class="left">   HTTPS URIs, because of security issues related to their transmission</td><td> </td><td class="right">   HTTPS URIs, because of security issues related to their transmission</td><td class="lineno" valign="top"></td></tr>
    1948       <tr><td><a name="diff0120" /></td></tr>
     1870      <tr><td><a name="diff0115" /></td></tr>
    19491871      <tr><td class="lineno" valign="top"></td><td class="lblock">   on the wire<span class="delete">.  (Section 2.7.1)</span></td><td> </td><td class="rblock">   on the wire<span class="insert"> (Section 2.7.1).</span></td><td class="lineno" valign="top"></td></tr>
    19501872      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19511873      <tr><td class="lineno" valign="top"></td><td class="left">   The HTTPS URI scheme is now defined by this specification;</td><td> </td><td class="right">   The HTTPS URI scheme is now defined by this specification;</td><td class="lineno" valign="top"></td></tr>
    1952       <tr><td><a name="diff0121" /></td></tr>
     1874      <tr><td><a name="diff0116" /></td></tr>
    19531875      <tr><td class="lineno" valign="top"></td><td class="lblock">   previously, it was <span class="delete">done</span> in Section 2.4 of [RFC2818].  Furthermore, it</td><td> </td><td class="rblock">   previously, it was <span class="insert">defined</span> in Section 2.4 of [RFC2818].  Furthermore,</td><td class="lineno" valign="top"></td></tr>
    19541876      <tr><td class="lineno" valign="top"></td><td class="lblock">   implies end-to-end <span class="delete">security.</span>  (Section <span class="delete">2.7.2)</span></td><td> </td><td class="rblock">   it implies end-to-end <span class="insert">security</span> (Section <span class="insert">2.7.2).</span></td><td class="lineno" valign="top"></td></tr>
     
    19581880      <tr><td class="lineno" valign="top"></td><td class="left">   fundamentally a message-oriented protocol.  Minimum supported sizes</td><td> </td><td class="right">   fundamentally a message-oriented protocol.  Minimum supported sizes</td><td class="lineno" valign="top"></td></tr>
    19591881      <tr><td class="lineno" valign="top"></td><td class="left">   for various protocol elements have been suggested, to improve</td><td> </td><td class="right">   for various protocol elements have been suggested, to improve</td><td class="lineno" valign="top"></td></tr>
    1960       <tr><td><a name="diff0122" /></td></tr>
     1882      <tr><td><a name="diff0117" /></td></tr>
    19611883      <tr><td class="lineno" valign="top"></td><td class="lblock">   interoperability<span class="delete">.  (Section 3)</span></td><td> </td><td class="rblock">   interoperability<span class="insert"> (Section 3).</span></td><td class="lineno" valign="top"></td></tr>
    19621884      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19631885      <tr><td class="lineno" valign="top"></td><td class="left">   Invalid whitespace around field-names is now required to be rejected,</td><td> </td><td class="right">   Invalid whitespace around field-names is now required to be rejected,</td><td class="lineno" valign="top"></td></tr>
    19641886      <tr><td class="lineno" valign="top"></td><td class="left">   because accepting it represents a security vulnerability.  The ABNF</td><td> </td><td class="right">   because accepting it represents a security vulnerability.  The ABNF</td><td class="lineno" valign="top"></td></tr>
    1965       <tr><td><a name="diff0123" /></td></tr>
     1887      <tr><td><a name="diff0118" /></td></tr>
    19661888      <tr><td class="lineno" valign="top"></td><td class="lblock">   productions defining header fields now only list the field <span class="delete">value.</span></td><td> </td><td class="rblock">   productions defining header fields now only list the field <span class="insert">value</span></td><td class="lineno" valign="top"></td></tr>
    19671889      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.2).</span></td><td class="lineno" valign="top"></td></tr>
     
    19691891      <tr><td class="lineno" valign="top"></td><td class="left">   Rules about implicit linear whitespace between certain grammar</td><td> </td><td class="right">   Rules about implicit linear whitespace between certain grammar</td><td class="lineno" valign="top"></td></tr>
    19701892      <tr><td class="lineno" valign="top"></td><td class="left">   productions have been removed; now whitespace is only allowed where</td><td> </td><td class="right">   productions have been removed; now whitespace is only allowed where</td><td class="lineno" valign="top"></td></tr>
    1971       <tr><td><a name="diff0124" /></td></tr>
     1893      <tr><td><a name="diff0119" /></td></tr>
    19721894      <tr><td class="lineno" valign="top"></td><td class="lblock">   specifically defined in the ABNF<span class="delete">.  (Section 3.2.3)</span></td><td> </td><td class="rblock">   specifically defined in the ABNF<span class="insert"> (Section 3.2.3).</span></td><td class="lineno" valign="top"></td></tr>
    19731895      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19741896      <tr><td class="lineno" valign="top"></td><td class="left">   Header fields that span multiple lines ("line folding") are</td><td> </td><td class="right">   Header fields that span multiple lines ("line folding") are</td><td class="lineno" valign="top"></td></tr>
    1975       <tr><td><a name="diff0125" /></td></tr>
     1897      <tr><td><a name="diff0120" /></td></tr>
    19761898      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">deprecated.</span>  (Section <span class="delete">3.2.4)</span></td><td> </td><td class="rblock">   <span class="insert">deprecated</span> (Section <span class="insert">3.2.4).</span></td><td class="lineno" valign="top"></td></tr>
    19771899      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
     
    19791901      <tr><td class="lineno" valign="top"></td><td class="left">   and handling of backslash-escaping in them has been clarified.  The</td><td> </td><td class="right">   and handling of backslash-escaping in them has been clarified.  The</td><td class="lineno" valign="top"></td></tr>
    19801902      <tr><td class="lineno" valign="top"></td><td class="left">   quoted-pair rule no longer allows escaping control characters other</td><td> </td><td class="right">   quoted-pair rule no longer allows escaping control characters other</td><td class="lineno" valign="top"></td></tr>
    1981       <tr><td><a name="diff0126" /></td></tr>
     1903      <tr><td><a name="diff0121" /></td></tr>
    19821904      <tr><td class="lineno" valign="top"></td><td class="lblock">   than HTAB.  <span class="delete">Non-ASCII</span> content in header fields and the reason phrase</td><td> </td><td class="rblock">   than HTAB.  <span class="insert">Non-US-ASCII</span> content in header fields and the reason</td><td class="lineno" valign="top"></td></tr>
    19831905      <tr><td class="lineno" valign="top"></td><td class="lblock">   has been obsoleted and made opaque (the TEXT rule was <span class="delete">removed).</span></td><td> </td><td class="rblock">   phrase has been obsoleted and made opaque (the TEXT rule was <span class="insert">removed)</span></td><td class="lineno" valign="top"></td></tr>
     
    19851907      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    19861908      <tr><td class="lineno" valign="top"></td><td class="left">   Bogus "Content-Length" header fields are now required to be handled</td><td> </td><td class="right">   Bogus "Content-Length" header fields are now required to be handled</td><td class="lineno" valign="top"></td></tr>
    1987       <tr><td><a name="diff0127" /></td></tr>
     1909      <tr><td><a name="diff0122" /></td></tr>
    19881910      <tr><td class="lineno" valign="top"></td><td class="lblock">   as errors by recipients<span class="delete">.  (Section 3.3.2)</span></td><td> </td><td class="rblock">   as errors by recipients<span class="insert"> (Section 3.3.2).</span></td><td class="lineno" valign="top"></td></tr>
    19891911      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    19931915      <tr><td class="lineno" valign="top"></td><td class="left">   elements cannot define such special cases.  CONNECT is a new, special</td><td> </td><td class="right">   elements cannot define such special cases.  CONNECT is a new, special</td><td class="lineno" valign="top"></td></tr>
    19941916      <tr><td class="lineno" valign="top"></td><td class="left">   case in determining message body length. "multipart/byteranges" is no</td><td> </td><td class="right">   case in determining message body length. "multipart/byteranges" is no</td><td class="lineno" valign="top"></td></tr>
    1995       <tr><td><a name="diff0128" /></td></tr>
     1917      <tr><td><a name="diff0123" /></td></tr>
    19961918      <tr><td class="lineno" valign="top"></td><td class="lblock">   longer a way of determining message body length <span class="delete">detection.</span></td><td> </td><td class="rblock">   longer a way of determining message body length <span class="insert">detection</span></td><td class="lineno" valign="top"></td></tr>
    19971919      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.3.3)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.3.3).</span></td><td class="lineno" valign="top"></td></tr>
    19981920      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1999       <tr><td><a name="diff0129" /></td></tr>
     1921      <tr><td><a name="diff0124" /></td></tr>
    20001922      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "identity" transfer coding token has been <span class="delete">removed.</span>  (Sections 3.3</td><td> </td><td class="rblock">   The "identity" transfer coding token has been <span class="insert">removed</span> (Sections 3.3</td><td class="lineno" valign="top"></td></tr>
    20011923      <tr><td class="lineno" valign="top"></td><td class="lblock">   and <span class="delete">4)</span></td><td> </td><td class="rblock">   and <span class="insert">4).</span></td><td class="lineno" valign="top"></td></tr>
    20021924      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20031925      <tr><td class="lineno" valign="top"></td><td class="left">   Chunk length does not include the count of the octets in the chunk</td><td> </td><td class="right">   Chunk length does not include the count of the octets in the chunk</td><td class="lineno" valign="top"></td></tr>
    2004       <tr><td><a name="diff0130" /></td></tr>
     1926      <tr><td><a name="diff0125" /></td></tr>
    20051927      <tr><td class="lineno" valign="top"></td><td class="lblock">   header and trailer.  Line folding in chunk extensions is <span class="delete">disallowed.</span></td><td> </td><td class="rblock">   header and trailer.  Line folding in chunk extensions is <span class="insert">disallowed</span></td><td class="lineno" valign="top"></td></tr>
    20061928      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.1).</span></td><td class="lineno" valign="top"></td></tr>
    20071929      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2008       <tr><td><a name="diff0131" /></td></tr>
     1930      <tr><td><a name="diff0126" /></td></tr>
    20091931      <tr><td class="lineno" valign="top"></td><td class="lblock">   The meaning of the "deflate" content coding has been <span class="delete">clarified.</span></td><td> </td><td class="rblock">   The meaning of the "deflate" content coding has been <span class="insert">clarified</span></td><td class="lineno" valign="top"></td></tr>
    20101932      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.2.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.2.2).</span></td><td class="lineno" valign="top"></td></tr>
     
    20121934      <tr><td class="lineno" valign="top"></td><td class="left">   The segment + query components of RFC 3986 have been used to define</td><td> </td><td class="right">   The segment + query components of RFC 3986 have been used to define</td><td class="lineno" valign="top"></td></tr>
    20131935      <tr><td class="lineno" valign="top"></td><td class="left">   the request-target, instead of abs_path from RFC 1808.  The asterisk-</td><td> </td><td class="right">   the request-target, instead of abs_path from RFC 1808.  The asterisk-</td><td class="lineno" valign="top"></td></tr>
    2014       <tr><td><a name="diff0132" /></td></tr>
     1936      <tr><td><a name="diff0127" /></td></tr>
    20151937      <tr><td class="lineno" valign="top"></td><td class="lblock">   form of the request-target is only allowed with the OPTIONS <span class="delete">method.</span></td><td> </td><td class="rblock">   form of the request-target is only allowed with the OPTIONS <span class="insert">method</span></td><td class="lineno" valign="top"></td></tr>
    20161938      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">5.3)</span></td><td> </td><td class="rblock">   (Section <span class="insert">5.3).</span></td><td class="lineno" valign="top"></td></tr>
    20171939      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2018       <tr><td><a name="diff0133" /></td></tr>
     1940      <tr><td><a name="diff0128" /></td></tr>
    20191941      <tr><td class="lineno" valign="top"></td><td class="lblock">   The term "Effective Request URI" has been introduced<span class="delete">.  (Section 5.5)</span></td><td> </td><td class="rblock">   The term "Effective Request URI" has been introduced<span class="insert"> (Section 5.5).</span></td><td class="lineno" valign="top"></td></tr>
    20201942      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2021       <tr><td><a name="diff0134" /></td></tr>
     1943      <tr><td><a name="diff0129" /></td></tr>
    20221944      <tr><td class="lineno" valign="top"></td><td class="lblock">   Gateways do not need to generate Via header fields <span class="delete">anymore.</span></td><td> </td><td class="rblock">   Gateways do not need to generate Via header fields <span class="insert">anymore</span></td><td class="lineno" valign="top"></td></tr>
    20231945      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">5.7.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">5.7.1).</span></td><td class="lineno" valign="top"></td></tr>
     
    20261948      <tr><td class="lineno" valign="top"></td><td class="left">   clarified.  Also, "hop-by-hop" header fields are required to appear</td><td> </td><td class="right">   clarified.  Also, "hop-by-hop" header fields are required to appear</td><td class="lineno" valign="top"></td></tr>
    20271949      <tr><td class="lineno" valign="top"></td><td class="left">   in the Connection header field; just because they're defined as hop-</td><td> </td><td class="right">   in the Connection header field; just because they're defined as hop-</td><td class="lineno" valign="top"></td></tr>
    2028       <tr><td><a name="diff0135" /></td></tr>
     1950      <tr><td><a name="diff0130" /></td></tr>
    20291951      <tr><td class="lineno" valign="top"></td><td class="lblock">   by-hop in this specification doesn't exempt them<span class="delete">.  (Section 6.1)</span></td><td> </td><td class="rblock">   by-hop in this specification doesn't exempt them<span class="insert"> (Section 6.1).</span></td><td class="lineno" valign="top"></td></tr>
    20301952      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    20341956      <tr><td class="lineno" valign="top"></td><td class="left">   the server prematurely closes the connection has been removed.  Also,</td><td> </td><td class="right">   the server prematurely closes the connection has been removed.  Also,</td><td class="lineno" valign="top"></td></tr>
    20351957      <tr><td class="lineno" valign="top"></td><td class="left">   some extraneous requirements about when servers are allowed to close</td><td> </td><td class="right">   some extraneous requirements about when servers are allowed to close</td><td class="lineno" valign="top"></td></tr>
    2036       <tr><td><a name="diff0136" /></td></tr>
     1958      <tr><td><a name="diff0131" /></td></tr>
    20371959      <tr><td class="lineno" valign="top"></td><td class="lblock">   connections prematurely have been removed<span class="delete">.  (Section 6.3)</span></td><td> </td><td class="rblock">   connections prematurely have been removed<span class="insert"> (Section 6.3).</span></td><td class="lineno" valign="top"></td></tr>
    20381960      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20391961      <tr><td class="lineno" valign="top"></td><td class="left">   The semantics of the Upgrade header field is now defined in responses</td><td> </td><td class="right">   The semantics of the Upgrade header field is now defined in responses</td><td class="lineno" valign="top"></td></tr>
    20401962      <tr><td class="lineno" valign="top"></td><td class="left">   other than 101 (this was incorporated from [RFC2817]).  Furthermore,</td><td> </td><td class="right">   other than 101 (this was incorporated from [RFC2817]).  Furthermore,</td><td class="lineno" valign="top"></td></tr>
    2041       <tr><td><a name="diff0137" /></td></tr>
     1963      <tr><td><a name="diff0132" /></td></tr>
    20421964      <tr><td class="lineno" valign="top"></td><td class="lblock">   the ordering in the field value is now significant<span class="delete">.  (Section 6.7)</span></td><td> </td><td class="rblock">   the ordering in the field value is now significant<span class="insert"> (Section 6.7).</span></td><td class="lineno" valign="top"></td></tr>
    20431965      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20441966      <tr><td class="lineno" valign="top"></td><td class="left">   Empty list elements in list productions (e.g., a list header field</td><td> </td><td class="right">   Empty list elements in list productions (e.g., a list header field</td><td class="lineno" valign="top"></td></tr>
    2045       <tr><td><a name="diff0138" /></td></tr>
     1967      <tr><td><a name="diff0133" /></td></tr>
    20461968      <tr><td class="lineno" valign="top"></td><td class="lblock">   containing ", ,") have been deprecated<span class="delete">.  (Section 7)</span></td><td> </td><td class="rblock">   containing ", ,") have been deprecated<span class="insert"> (Section 7).</span></td><td class="lineno" valign="top"></td></tr>
    20471969      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20481970      <tr><td class="lineno" valign="top"></td><td class="left">   Registration of Transfer Codings now requires IETF Review</td><td> </td><td class="right">   Registration of Transfer Codings now requires IETF Review</td><td class="lineno" valign="top"></td></tr>
    2049       <tr><td><a name="diff0139" /></td></tr>
     1971      <tr><td><a name="diff0134" /></td></tr>
    20501972      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 8.4)</td><td> </td><td class="rblock">   (Section 8.4)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>
    20511973      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2052       <tr><td><a name="diff0140" /></td></tr>
     1974      <tr><td><a name="diff0135" /></td></tr>
    20531975      <tr><td class="lineno" valign="top"></td><td class="lblock">   This specification now defines the Upgrade <span class="delete">Token Registry,</span> previously</td><td> </td><td class="rblock">   This specification now defines the <span class="insert">"HTTP</span> Upgrade <span class="insert">Tokens" registry,</span></td><td class="lineno" valign="top"></td></tr>
    20541976      <tr><td class="lineno" valign="top"></td><td class="lblock">   defined in Section 7.2 of <span class="delete">[RFC2817].</span>  (Section <span class="delete">8.6)</span></td><td> </td><td class="rblock">   previously defined in Section 7.2 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.6).</span></td><td class="lineno" valign="top"></td></tr>
    20551977      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2056       <tr><td><a name="diff0141" /></td></tr>
     1978      <tr><td><a name="diff0136" /></td></tr>
    20571979      <tr><td class="lineno" valign="top"></td><td class="lblock">   The expectation to support HTTP/0.9 requests has been <span class="delete">removed.</span></td><td> </td><td class="rblock">   The expectation to support HTTP/0.9 requests has been <span class="insert">removed</span></td><td class="lineno" valign="top"></td></tr>
    20581980      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Appendix <span class="delete">A)</span></td><td> </td><td class="rblock">   (Appendix <span class="insert">A).</span></td><td class="lineno" valign="top"></td></tr>
     
    20601982      <tr><td class="lineno" valign="top"></td><td class="left">   Issues with the Keep-Alive and Proxy-Connection header fields in</td><td> </td><td class="right">   Issues with the Keep-Alive and Proxy-Connection header fields in</td><td class="lineno" valign="top"></td></tr>
    20611983      <tr><td class="lineno" valign="top"></td><td class="left">   requests are pointed out, with use of the latter being discouraged</td><td> </td><td class="right">   requests are pointed out, with use of the latter being discouraged</td><td class="lineno" valign="top"></td></tr>
    2062       <tr><td><a name="diff0142" /></td></tr>
     1984      <tr><td><a name="diff0137" /></td></tr>
    20631985      <tr><td class="lineno" valign="top"></td><td class="lblock">   altogether<span class="delete">.  (Appendix A.1.2)</span></td><td> </td><td class="rblock">   altogether<span class="insert"> (Appendix A.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    20641986      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    20842006      <tr><td class="lineno" valign="top"></td><td class="left">      deflate (Coding Format)  38</td><td> </td><td class="right">      deflate (Coding Format)  38</td><td class="lineno" valign="top"></td></tr>
    20852007      <tr><td class="lineno" valign="top"></td><td class="left">      Delimiters  26</td><td> </td><td class="right">      Delimiters  26</td><td class="lineno" valign="top"></td></tr>
    2086       <tr><td><a name="diff0143" /></td></tr>
     2008      <tr><td><a name="diff0138" /></td></tr>
    20872009      <tr><td class="lineno" valign="top"></td><td class="lblock">      downstream  <span class="delete">9</span></td><td> </td><td class="rblock">      downstream  <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
    20882010      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    21082030      <tr><td class="lineno" valign="top"></td><td class="left">         HTAB  6</td><td> </td><td class="right">         HTAB  6</td><td class="lineno" valign="top"></td></tr>
    21092031      <tr><td class="lineno" valign="top"></td><td class="left">         HTTP-message  19</td><td> </td><td class="right">         HTTP-message  19</td><td class="lineno" valign="top"></td></tr>
    2110       <tr><td><a name="diff0144" /></td></tr>
     2032      <tr><td><a name="diff0139" /></td></tr>
    21112033      <tr><td class="lineno" valign="top"></td><td class="lblock">         HTTP-name  1<span class="delete">3</span></td><td> </td><td class="rblock">         HTTP-name  1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    21122034      <tr><td class="lineno" valign="top"></td><td class="left">         http-URI  16</td><td> </td><td class="right">         http-URI  16</td><td class="lineno" valign="top"></td></tr>
    2113       <tr><td><a name="diff0145" /></td></tr>
     2035      <tr><td><a name="diff0140" /></td></tr>
    21142036      <tr><td class="lineno" valign="top"></td><td class="lblock">         HTTP-version  1<span class="delete">3</span></td><td> </td><td class="rblock">         HTTP-version  1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    21152037      <tr><td class="lineno" valign="top"></td><td class="left">         https-URI  18</td><td> </td><td class="right">         https-URI  18</td><td class="lineno" valign="top"></td></tr>
     
    21352057      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21362058      <tr><td class="lineno" valign="top"></td><td class="left">   I</td><td> </td><td class="right">   I</td><td class="lineno" valign="top"></td></tr>
    2137       <tr><td><a name="diff0146" /></td></tr>
     2059      <tr><td><a name="diff0141" /></td></tr>
    21382060      <tr><td class="lineno" valign="top"></td><td class="lblock">      inbound  <span class="delete">9</span></td><td> </td><td class="rblock">      inbound  <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
    21392061      <tr><td class="lineno" valign="top"></td><td class="left">      interception proxy  11</td><td> </td><td class="right">      interception proxy  11</td><td class="lineno" valign="top"></td></tr>
     
    21542076      <tr><td class="lineno" valign="top"></td><td class="left">      origin server  7</td><td> </td><td class="right">      origin server  7</td><td class="lineno" valign="top"></td></tr>
    21552077      <tr><td class="lineno" valign="top"></td><td class="left">      origin-form (of request-target)  41</td><td> </td><td class="right">      origin-form (of request-target)  41</td><td class="lineno" valign="top"></td></tr>
    2156       <tr><td><a name="diff0147" /></td></tr>
     2078      <tr><td><a name="diff0142" /></td></tr>
    21572079      <tr><td class="lineno" valign="top"></td><td class="lblock">      outbound  <span class="delete">9</span></td><td> </td><td class="rblock">      outbound  <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
    21582080      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    21782100      <tr><td class="lineno" valign="top"></td><td class="left">   U</td><td> </td><td class="right">   U</td><td class="lineno" valign="top"></td></tr>
    21792101      <tr><td class="lineno" valign="top"></td><td class="left">      Upgrade header field  56</td><td> </td><td class="right">      Upgrade header field  56</td><td class="lineno" valign="top"></td></tr>
    2180       <tr><td><a name="diff0148" /></td></tr>
     2102      <tr><td><a name="diff0143" /></td></tr>
    21812103      <tr><td class="lineno" valign="top"></td><td class="lblock">      upstream  <span class="delete">9</span></td><td> </td><td class="rblock">      upstream  <span class="insert">10</span></td><td class="lineno" valign="top"></td></tr>
    21822104      <tr><td class="lineno" valign="top"></td><td class="left">      URI scheme</td><td> </td><td class="right">      URI scheme</td><td class="lineno" valign="top"></td></tr>
     
    21922114
    21932115     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    2194      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 148 change blocks.&nbsp;</a></th></tr>
    2195      <tr class="stats"><td></td><th><i>246 lines changed or deleted</i></th><th><i> </i></th><th><i>225 lines changed or added</i></th><td></td></tr>
     2116     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 143 change blocks.&nbsp;</a></th></tr>
     2117     <tr class="stats"><td></td><th><i>240 lines changed or deleted</i></th><th><i> </i></th><th><i>219 lines changed or added</i></th><td></td></tr>
    21962118     <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>
    21972119   </table>
  • draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt

    r2635 r2636  
    396396    request with one or more response messages.  A client constructs
    397397    request messages to communicate specific intentions, and examines
    398     received responses to see if the intentions were carried out and
     398    received responses to see if the intentions were carried out, and
    399399    determine how to interpret the results.  This document defines
    400400    HTTP/1.1 request and response semantics in terms of the architecture
     
    577577
    578578
    579 Section 3.1.3.1., paragraph 4:
    580 OLD:
    581 
    582     A language tag is a sequence of one or more case-insensitive subtags,
    583     each separated by a hyphen character ("-", %x2D).  In most cases, a
    584     language tag consists of a primary language subtag that identifies a
    585     broad family of related languages (e.g., "en" = English) which is
    586     optionally followed by a series of subtags that refine or narrow that
    587     language's range (e.g., "en-CA" = the variety of English as
    588     communicated in Canada).  Whitespace is not allowed within a language
    589     tag.  Example tags include:
    590 
    591 NEW:
    592 
    593     A language tag is a sequence of one or more case-insensitive subtags,
    594     each separated by a hyphen character ("-", %x2D).  In most cases, a
    595     language tag consists of a primary language subtag that identifies a
    596     broad family of related languages (e.g., "en" = English), which is
    597     optionally followed by a series of subtags that refine or narrow that
    598     language's range (e.g., "en-CA" = the variety of English as
    599     communicated in Canada).  Whitespace is not allowed within a language
    600     tag.  Example tags include:
    601 
    602 
    603579Section 3.1.3.2., paragraph 5:
    604580OLD:
     
    771747
    772748
    773 Section 4.2.3., paragraph 1:
    774 OLD:
    775 
    776     Request methods can be defined as "cacheable" to indicate that
    777     responses to them are allowed to be stored for future reuse; for
    778     specific requirements see [RFC7234].  In general, safe methods that
    779     do not depend on a current or authoritative response are defined as
    780     cacheable; this specification defines GET, HEAD and POST as
    781     cacheable, although the overwhelming majority of cache
    782     implementations only support GET and HEAD.
    783 
    784 NEW:
    785 
    786     Request methods can be defined as "cacheable" to indicate that
    787     responses to them are allowed to be stored for future reuse; for
    788     specific requirements see [RFC7234].  In general, safe methods that
    789     do not depend on a current or authoritative response are defined as
    790     cacheable; this specification defines GET, HEAD, and POST as
    791     cacheable, although the overwhelming majority of cache
    792     implementations only support GET and HEAD.
    793 
    794 
    795 Section 4.3.1., paragraph 2:
    796 OLD:
    797 
    798     It is tempting to think of resource identifiers as remote file system
    799     pathnames, and of representations as being a copy of the contents of
    800     such files.  In fact, that is how many resources are implemented (see
    801     Section 9.1 for related security considerations).  However, there are
    802     no such limitations in practice.  The HTTP interface for a resource
    803     is just as likely to be implemented as a tree of content objects, a
    804     programmatic view on various database records, or a gateway to other
    805     information systems.  Even when the URI mapping mechanism is tied to
    806     a file system, an origin server might be configured to execute the
    807     files with the request as input and send the output as the
    808     representation, rather than transfer the files directly.  Regardless,
    809     only the origin server needs to know how each of its resource
    810     identifiers corresponds to an implementation, and how each
    811     implementation manages to select and send a current representation of
    812     the target resource in a response to GET.
    813 
    814 NEW:
    815 
    816     It is tempting to think of resource identifiers as remote file system
    817     pathnames and of representations as being a copy of the contents of
    818     such files.  In fact, that is how many resources are implemented (see
    819     Section 9.1 for related security considerations).  However, there are
    820     no such limitations in practice.  The HTTP interface for a resource
    821     is just as likely to be implemented as a tree of content objects, a
    822     programmatic view on various database records, or a gateway to other
    823     information systems.  Even when the URI mapping mechanism is tied to
    824     a file system, an origin server might be configured to execute the
    825     files with the request as input and send the output as the
    826     representation rather than transfer the files directly.  Regardless,
    827     only the origin server needs to know how each of its resource
    828     identifiers corresponds to an implementation and how each
    829     implementation manages to select and send a current representation of
    830     the target resource in a response to GET.
    831 
    832 
    833749Section 4.3.3., paragraph 6:
    834750OLD:
     
    908824
    909825
    910 Section 4.3.5., paragraph 1:
    911 OLD:
    912 
    913     The DELETE method requests that the origin server remove the
    914     association between the target resource and its current
    915     functionality.  In effect, this method is similar to the rm command
    916     in UNIX: it expresses a deletion operation on the URI mapping of the
    917     origin server, rather than an expectation that the previously
    918     associated information be deleted.
    919 
    920 NEW:
    921 
    922     The DELETE method requests that the origin server remove the
    923     association between the target resource and its current
    924     functionality.  In effect, this method is similar to the rm command
    925     in UNIX: it expresses a deletion operation on the URI mapping of the
    926     origin server rather than an expectation that the previously
    927     associated information be deleted.
    928 
    929 
    930826Section 4.3.6., paragraph 2:
    931827OLD:
     
    1023919
    1024920
    1025 Section 5.1.2., paragraph 4:
    1026 OLD:
    1027 
    1028     Each intermediary that receives a TRACE or OPTIONS request containing
    1029     a Max-Forwards header field MUST check and update its value prior to
    1030     forwarding the request.  If the received value is zero (0), the
    1031     intermediary MUST NOT forward the request; instead, the intermediary
    1032     MUST respond as the final recipient.  If the received Max-Forwards
    1033     value is greater than zero, the intermediary MUST generate an updated
    1034     Max-Forwards field in the forwarded message with a field-value that
    1035     is the lesser of: a) the received value decremented by one (1), or b)
    1036     the recipient's maximum supported value for Max-Forwards.
    1037 
    1038 NEW:
    1039 
    1040     Each intermediary that receives a TRACE or OPTIONS request containing
    1041     a Max-Forwards header field MUST check and update its value prior to
    1042     forwarding the request.  If the received value is zero (0), the
    1043     intermediary MUST NOT forward the request; instead, the intermediary
    1044     MUST respond as the final recipient.  If the received Max-Forwards
    1045     value is greater than zero, the intermediary MUST generate an updated
    1046     Max-Forwards field in the forwarded message with a field-value that
    1047     is the lesser of a) the received value decremented by one (1) or b)
    1048     the recipient's maximum supported value for Max-Forwards.
    1049 
    1050 
    1051921Section 5.3.2., paragraph 9:
    1052922OLD:
     
    1059929    is interpreted as "I prefer audio/basic, but send me any audio type
    1060930    if it is the best available after an 80% markdown in quality".
    1061 
    1062 
    1063 Section 5.3.5., paragraph 6:
    1064 OLD:
    1065 
    1066     A request without any Accept-Language header field implies that the
    1067     user agent will accept any language in response.  If the header field
    1068     is present in a request and none of the available representations for
    1069     the response have a matching language tag, the origin server can
    1070     either disregard the header field by treating the response as if it
    1071     is not subject to content negotiation, or honor the header field by
    1072     sending a 406 (Not Acceptable) response.  However, the latter is not
    1073     encouraged, as doing so can prevent users from accessing content that
    1074     they might be able to use (with translation software, for example).
    1075 
    1076 NEW:
    1077 
    1078     A request without any Accept-Language header field implies that the
    1079     user agent will accept any language in response.  If the header field
    1080     is present in a request and none of the available representations for
    1081     the response have a matching language tag, the origin server can
    1082     either disregard the header field by treating the response as if it
    1083     is not subject to content negotiation or honor the header field by
    1084     sending a 406 (Not Acceptable) response.  However, the latter is not
    1085     encouraged, as doing so can prevent users from accessing content that
    1086     they might be able to use (with translation software, for example).
    1087 
    1088 
    1089 Section 5.3.5., paragraph 10:
    1090 OLD:
    1091 
    1092     Since intelligibility is highly dependent on the individual user,
    1093     user agents need to allow user control over the linguistic preference
    1094     (either through configuration of the user agent itself, or by
    1095     defaulting to a user controllable system setting).  A user agent that
    1096     does not provide such control to the user MUST NOT send an Accept-
    1097     Language header field.
    1098 
    1099 NEW:
    1100 
    1101     Since intelligibility is highly dependent on the individual user,
    1102     user agents need to allow user control over the linguistic preference
    1103     (either through configuration of the user agent itself or by
    1104     defaulting to a user controllable system setting).  A user agent that
    1105     does not provide such control to the user MUST NOT send an Accept-
    1106     Language header field.
    1107931
    1108932
     
    14191243
    14201244
    1421 Section 6.2., paragraph 1:
    1422 OLD:
    1423 
    1424     The 1xx (Informational) class of status code indicates an interim
    1425     response for communicating connection status or request progress
    1426     prior to completing the requested action and sending a final
    1427     response.  All 1xx responses consist of only the status-line and
    1428     optional header fields, and thus are terminated by the empty line at
    1429     the end of the header section.  Since HTTP/1.0 did not define any 1xx
    1430     status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
    1431     client.
    1432 
    1433 NEW:
    1434 
    1435     The 1xx (Informational) class of status code indicates an interim
    1436     response for communicating connection status or request progress
    1437     prior to completing the requested action and sending a final
    1438     response.  All 1xx responses consist of only the status-line and
    1439     optional header fields and, thus, are terminated by the empty line at
    1440     the end of the header section.  Since HTTP/1.0 did not define any 1xx
    1441     status codes, a server MUST NOT send a 1xx response to an HTTP/1.0
    1442     client.
    1443 
    1444 
    14451245Section 6.3.3., paragraph 2:
    14461246OLD:
     
    15131313
    15141314
    1515 Section 6.4.4., paragraph 2:
    1516 OLD:
    1517 
    1518     This status code is applicable to any HTTP method.  It is primarily
    1519     used to allow the output of a POST action to redirect the user agent
    1520     to a selected resource, since doing so provides the information
    1521     corresponding to the POST response in a form that can be separately
    1522     identified, bookmarked, and cached independent of the original
    1523     request.
    1524 
    1525 NEW:
    1526 
    1527     This status code is applicable to any HTTP method.  It is primarily
    1528     used to allow the output of a POST action to redirect the user agent
    1529     to a selected resource, since doing so provides the information
    1530     corresponding to the POST response in a form that can be separately
    1531     identified, bookmarked, and cached, independent of the original
    1532     request.
    1533 
    1534 
    15351315Section 6.4.7., paragraph 3:
    15361316OLD:
     
    15651345    a client error (e.g., malformed request syntax, invalid request
    15661346    message framing, or deceptive request routing).
    1567 
    1568 
    1569 Section 5.3, paragraph 0:
    1570 OLD:
    1571 
    1572     The 414 (URI Too Long) status code indicates that the server is
    1573     refusing to service the request because the request-target (Section
    1574     5.3 of [RFC7230]) is longer than the server is willing to interpret.
    1575     This rare condition is only likely to occur when a client has
    1576     improperly converted a POST request to a GET request with long query
    1577     information, when the client has descended into a "black hole" of
    1578     redirection (e.g., a redirected URI prefix that points to a suffix of
    1579     itself), or when the server is under attack by a client attempting to
    1580     exploit potential security holes.
    1581 
    1582 NEW:
    1583 
    1584     The 414 (URI Too Long) status code indicates that the server is
    1585     refusing to service the request because the request-target (Section
    1586     5.3 of [RFC7230]) is longer than the server is willing to interpret.
    1587     This rare condition is only likely to occur when a client has
    1588     improperly converted a POST request to a GET request with long query
    1589     information, when the client has descended into a "black hole" of
    1590     redirection (e.g., a redirected URI prefix that points to a suffix of
    1591     itself) or when the server is under attack by a client attempting to
    1592     exploit potential security holes.
    15931347
    15941348
     
    17851539    when the condition is false.  Likewise, if the new method might have
    17861540    some use for partial response semantics ([RFC7233]), it ought to
    1787     document this too.
     1541    document this, too.
    17881542
    17891543NEW:
     
    19081662    range of ASCII characters.  Header fields needing a greater range of
    19091663    characters can use an encoding such as the one defined in [RFC5987].
    1910 
    1911 
    1912 Section 8.3.1., paragraph 13:
    1913 OLD:
    1914 
    1915     o  Whether the field is a single value, or whether it can be a list
    1916        (delimited by commas; see Section 3.2 of [RFC7230]).
    1917 
    1918 NEW:
    1919 
    1920     o  Whether the field is a single value or whether it can be a list
    1921        (delimited by commas; see Section 3.2 of [RFC7230]).
    19221664
    19231665
     
    20641806
    20651807
    2066 Section 9.1., paragraph 1:
    2067 OLD:
    2068 
    2069     Origin servers frequently make use of their local file system to
    2070     manage the mapping from effective request URI to resource
    2071     representations.  Implementers need to be aware that most file
    2072     systems are not designed to protect against malicious file or path
    2073     names, and thus depend on the origin server to avoid mapping to file
    2074     names, folders, or directories that have special significance to the
    2075     system.
    2076 
    2077 NEW:
    2078 
    2079     Origin servers frequently make use of their local file system to
    2080     manage the mapping from effective request URI to resource
    2081     representations.  Implementers need to be aware that most file
    2082     systems are not designed to protect against malicious file or path
    2083     names and, thus, depend on the origin server to avoid mapping to file
    2084     names, folders, or directories that have special significance to the
    2085     system.
    2086 
    2087 
    20881808Section 9.1., paragraph 2:
    20891809OLD:
  • draft-ietf-httpbis/latest/auth48/rfc7231.diff.html

    r2635 r2636  
    140140      <tr><td class="lineno" valign="top"></td><td class="left">   request with one or more response messages.  A client constructs</td><td> </td><td class="right">   request with one or more response messages.  A client constructs</td><td class="lineno" valign="top"></td></tr>
    141141      <tr><td><a name="diff0009" /></td></tr>
    142       <tr><td class="lineno" valign="top"></td><td class="lblock">   request messages to communicate specific intentions, <span class="delete">and</span> examines</td><td> </td><td class="rblock">   request messages to communicate specific intentions, examines</td><td class="lineno" valign="top"></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="lblock">   received responses to see if the intentions were carried <span class="delete">out</span> and</td><td> </td><td class="rblock">   received responses to see if the intentions were carried <span class="insert">out,</span> and</td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">determine</span> how to interpret the results.  This document defines</td><td> </td><td class="rblock">   <span class="insert">determines</span> how to interpret the results.  This document defines</td><td class="lineno" valign="top"></td></tr>
     142      <tr><td class="lineno" valign="top"></td><td class="lblock">   request messages to communicate specific intentions, <span class="delete">and </span>examines</td><td> </td><td class="rblock">   request messages to communicate specific intentions, examines</td><td class="lineno" valign="top"></td></tr>
     143      <tr><td class="lineno" valign="top"></td><td class="left">   received responses to see if the intentions were carried out, and</td><td> </td><td class="right">   received responses to see if the intentions were carried out, and</td><td class="lineno" valign="top"></td></tr>
     144      <tr><td><a name="diff0010" /></td></tr>
     145      <tr><td class="lineno" valign="top"></td><td class="lblock">   determine how to interpret the results.  This document defines</td><td> </td><td class="rblock">   determine<span class="insert">s</span> how to interpret the results.  This document defines</td><td class="lineno" valign="top"></td></tr>
    145146      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/1.1 request and response semantics in terms of the architecture</td><td> </td><td class="right">   HTTP/1.1 request and response semantics in terms of the architecture</td><td class="lineno" valign="top"></td></tr>
    146147      <tr><td class="lineno" valign="top"></td><td class="left">   defined in [RFC7230].</td><td> </td><td class="right">   defined in [RFC7230].</td><td class="lineno" valign="top"></td></tr>
     
    165166      <tr><td class="lineno" valign="top"></td><td class="left">2.  Resources</td><td> </td><td class="right">2.  Resources</td><td class="lineno" valign="top"></td></tr>
    166167      <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><a name="diff0010" /></td></tr>
     168      <tr><td><a name="diff0011" /></td></tr>
    168169      <tr><td class="lineno" valign="top"></td><td class="lblock">   The target of an HTTP request is called a <span class="delete">resource</span>.  HTTP does not</td><td> </td><td class="rblock">   The target of an HTTP request is called a <span class="insert">"resource"</span>.  HTTP does not</td><td class="lineno" valign="top"></td></tr>
    169170      <tr><td class="lineno" valign="top"></td><td class="left">   limit the nature of a resource; it merely defines an interface that</td><td> </td><td class="right">   limit the nature of a resource; it merely defines an interface that</td><td class="lineno" valign="top"></td></tr>
     
    189190      <tr><td class="lineno" valign="top"></td><td class="left">   potentially unbounded stream of representation data.</td><td> </td><td class="right">   potentially unbounded stream of representation data.</td><td class="lineno" valign="top"></td></tr>
    190191      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    191       <tr><td><a name="diff0011" /></td></tr>
     192      <tr><td><a name="diff0012" /></td></tr>
    192193      <tr><td class="lineno" valign="top"></td><td class="lblock">   An origin server might be provided with, or capable of generating,</td><td> </td><td class="rblock">   An origin server might be provided with, or <span class="insert">be </span>capable of generating,</td><td class="lineno" valign="top"></td></tr>
    193194      <tr><td class="lineno" valign="top"></td><td class="left">   multiple representations that are each intended to reflect the</td><td> </td><td class="right">   multiple representations that are each intended to reflect the</td><td class="lineno" valign="top"></td></tr>
     
    213214      <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.1.  Media Type</td><td> </td><td class="right">3.1.1.1.  Media Type</td><td class="lineno" valign="top"></td></tr>
    214215      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    215       <tr><td><a name="diff0012" /></td></tr>
     216      <tr><td><a name="diff0013" /></td></tr>
    216217      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP uses Internet <span class="delete">Media T</span>ypes [RFC2046] in the Content-Type</td><td> </td><td class="rblock">   HTTP uses Internet <span class="insert">media t</span>ypes [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr>
    217218      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td> </td><td class="right">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td class="lineno" valign="top"></td></tr>
     
    230231      <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>
    231232      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    232       <tr><td><a name="diff0013" /></td></tr>
     233      <tr><td><a name="diff0014" /></td></tr>
    233234      <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>
    234235      <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>
     
    238239      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    239240      <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>
    240       <tr><td><a name="diff0014" /></td></tr>
     241      <tr><td><a name="diff0015" /></td></tr>
    241242      <tr><td class="lineno" valign="top"></td><td class="lblock">   transmitted <span class="delete">as either</span> a token or within a quoted-string.  The quoted</td><td> </td><td class="rblock">   transmitted <span class="insert">either as</span> a token or within a quoted-string.  The quoted</td><td class="lineno" valign="top"></td></tr>
    242243      <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>
     
    262263      <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>
    263264      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    264       <tr><td><a name="diff0015" /></td></tr>
     265      <tr><td><a name="diff0016" /></td></tr>
    265266      <tr><td class="lineno" valign="top"></td><td class="lblock">   Charset names ought to be registered in IANA <span class="delete">Character Set</span> registry</td><td> </td><td class="rblock">   Charset names ought to be registered in <span class="insert">the</span> IANA <span class="insert">"Character Sets"</span></td><td class="lineno" valign="top"></td></tr>
    266267      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(&lt;http://www.iana.org/assignments/character-sets&gt;)</span> according to the</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>
     
    282283      <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>
    283284      <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>
    284       <tr><td><a name="diff0016" /></td></tr>
     285      <tr><td><a name="diff0017" /></td></tr>
    285286      <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>
    286287      <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>
     
    315316      <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>
    316317      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    317       <tr><td><a name="diff0017" /></td></tr>
     318      <tr><td><a name="diff0018" /></td></tr>
    318319      <tr><td class="lineno" valign="top"></td><td class="lblock">   All content-coding values are <span class="delete">case-insensitive</span> and ought to be</td><td> </td><td class="rblock">   All content-coding values are <span class="insert">case insensitive</span> and ought to be</td><td class="lineno" valign="top"></td></tr>
    319320      <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the <span class="delete">HTTP</span> Content Coding <span class="delete">registry,</span> as defined in</td><td> </td><td class="rblock">   registered within the <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry",</span> as defined in</td><td class="lineno" valign="top"></td></tr>
     
    329330      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    330331      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    331       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 13, line 24</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 13, line 24</em></th><td></td></tr>
    332       <tr><td class="lineno" valign="top"></td><td class="left">   HTTP uses language tags within the Accept-Language and Content-</td><td> </td><td class="right">   HTTP uses language tags within the Accept-Language and Content-</td><td class="lineno" valign="top"></td></tr>
    333       <tr><td class="lineno" valign="top"></td><td class="left">   Language header fields.  Accept-Language uses the broader language-</td><td> </td><td class="right">   Language header fields.  Accept-Language uses the broader language-</td><td class="lineno" valign="top"></td></tr>
    334       <tr><td class="lineno" valign="top"></td><td class="left">   range production defined in Section 5.3.5, whereas Content-Language</td><td> </td><td class="right">   range production defined in Section 5.3.5, whereas Content-Language</td><td class="lineno" valign="top"></td></tr>
    335       <tr><td class="lineno" valign="top"></td><td class="left">   uses the language-tag production defined below.</td><td> </td><td class="right">   uses the language-tag production defined below.</td><td class="lineno" valign="top"></td></tr>
    336       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    337       <tr><td class="lineno" valign="top"></td><td class="left">     language-tag = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;</td><td> </td><td class="right">     language-tag = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;</td><td class="lineno" valign="top"></td></tr>
    338       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    339       <tr><td class="lineno" valign="top"></td><td class="left">   A language tag is a sequence of one or more case-insensitive subtags,</td><td> </td><td class="right">   A language tag is a sequence of one or more case-insensitive subtags,</td><td class="lineno" valign="top"></td></tr>
    340       <tr><td class="lineno" valign="top"></td><td class="left">   each separated by a hyphen character ("-", %x2D).  In most cases, a</td><td> </td><td class="right">   each separated by a hyphen character ("-", %x2D).  In most cases, a</td><td class="lineno" valign="top"></td></tr>
    341       <tr><td class="lineno" valign="top"></td><td class="left">   language tag consists of a primary language subtag that identifies a</td><td> </td><td class="right">   language tag consists of a primary language subtag that identifies a</td><td class="lineno" valign="top"></td></tr>
    342       <tr><td><a name="diff0018" /></td></tr>
    343       <tr><td class="lineno" valign="top"></td><td class="lblock">   broad family of related languages (e.g., "en" = English) which is</td><td> </td><td class="rblock">   broad family of related languages (e.g., "en" = English)<span class="insert">,</span> which is</td><td class="lineno" valign="top"></td></tr>
    344       <tr><td class="lineno" valign="top"></td><td class="left">   optionally followed by a series of subtags that refine or narrow that</td><td> </td><td class="right">   optionally followed by a series of subtags that refine or narrow that</td><td class="lineno" valign="top"></td></tr>
    345       <tr><td class="lineno" valign="top"></td><td class="left">   language's range (e.g., "en-CA" = the variety of English as</td><td> </td><td class="right">   language's range (e.g., "en-CA" = the variety of English as</td><td class="lineno" valign="top"></td></tr>
    346       <tr><td class="lineno" valign="top"></td><td class="left">   communicated in Canada).  Whitespace is not allowed within a language</td><td> </td><td class="right">   communicated in Canada).  Whitespace is not allowed within a language</td><td class="lineno" valign="top"></td></tr>
    347       <tr><td class="lineno" valign="top"></td><td class="left">   tag.  Example tags include:</td><td> </td><td class="right">   tag.  Example tags include:</td><td class="lineno" valign="top"></td></tr>
    348       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    349       <tr><td class="lineno" valign="top"></td><td class="left">     fr, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN</td><td> </td><td class="right">     fr, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN</td><td class="lineno" valign="top"></td></tr>
    350       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    351       <tr><td class="lineno" valign="top"></td><td class="left">   See [RFC5646] for further information.</td><td> </td><td class="right">   See [RFC5646] for further information.</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" valign="top"></td><td class="left">3.1.3.2.  Content-Language</td><td> </td><td class="right">3.1.3.2.  Content-Language</td><td class="lineno" valign="top"></td></tr>
    354       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    355       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
     332      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
    356333      <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>
    357334      <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>
     
    377354      <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>
    378355      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    379       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr>
     356      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 20, line 37</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 20, line 37</em></th><td></td></tr>
    380357      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    381358      <tr><td class="lineno" valign="top"></td><td class="left">   A server might choose not to send an initial representation, other</td><td> </td><td class="right">   A server might choose not to send an initial representation, other</td><td class="lineno" valign="top"></td></tr>
     
    401378      <tr><td class="lineno" valign="top"></td><td class="left">   selection, though it does not prevent such a mechanism from being</td><td> </td><td class="right">   selection, though it does not prevent such a mechanism from being</td><td class="lineno" valign="top"></td></tr>
    402379      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    403       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>
     380      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 21, line 26</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 21, line 26</em></th><td></td></tr>
    404381      <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>
    405382      <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>
     
    431408      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    432409      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    433       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>
     410      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 22, line 31</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 22, line 31</em></th><td></td></tr>
    434411      <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>
    435412      <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>
     
    456433      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    457434      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    458       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>
     435      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 23, line 5</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 23, line 5</em></th><td></td></tr>
    459436      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    460437      <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>
     
    490467      <tr><td class="lineno" valign="top"></td><td class="left">   untrusted content.</td><td> </td><td class="right">   untrusted content.</td><td class="lineno" valign="top"></td></tr>
    491468      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    492       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 23, line 39</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 23, line 39</em></th><td></td></tr>
     469      <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 23, line 39</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 23, line 39</em></th><td></td></tr>
    493470      <tr><td class="lineno" valign="top"></td><td class="left">   made aware of an unsafe action before it is requested.</td><td> </td><td class="right">   made aware of an unsafe action before it is requested.</td><td class="lineno" valign="top"></td></tr>
    494471      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    530507      <tr><td class="lineno" valign="top"></td><td class="left">   request succeeded, though the response might differ.</td><td> </td><td class="right">   request succeeded, though the response might differ.</td><td class="lineno" valign="top"></td></tr>
    531508      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    532       <tr><td class="lineno" valign="top"></td><td class="left">4.2.3.  Cacheable Methods</td><td> </td><td class="right">4.2.3.  Cacheable Methods</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">   Request methods can be defined as "cacheable" to indicate that</td><td> </td><td class="right">   Request methods can be defined as "cacheable" to indicate that</td><td class="lineno" valign="top"></td></tr>
    535       <tr><td class="lineno" valign="top"></td><td class="left">   responses to them are allowed to be stored for future reuse; for</td><td> </td><td class="right">   responses to them are allowed to be stored for future reuse; for</td><td class="lineno" valign="top"></td></tr>
    536       <tr><td class="lineno" valign="top"></td><td class="left">   specific requirements see [RFC7234].  In general, safe methods that</td><td> </td><td class="right">   specific requirements see [RFC7234].  In general, safe methods that</td><td class="lineno" valign="top"></td></tr>
    537       <tr><td class="lineno" valign="top"></td><td class="left">   do not depend on a current or authoritative response are defined as</td><td> </td><td class="right">   do not depend on a current or authoritative response are defined as</td><td class="lineno" valign="top"></td></tr>
    538       <tr><td><a name="diff0027" /></td></tr>
    539       <tr><td class="lineno" valign="top"></td><td class="lblock">   cacheable; this specification defines GET, HEAD and POST as</td><td> </td><td class="rblock">   cacheable; this specification defines GET, HEAD<span class="insert">,</span> and POST as</td><td class="lineno" valign="top"></td></tr>
    540       <tr><td class="lineno" valign="top"></td><td class="left">   cacheable, although the overwhelming majority of cache</td><td> </td><td class="right">   cacheable, although the overwhelming majority of cache</td><td class="lineno" valign="top"></td></tr>
    541       <tr><td class="lineno" valign="top"></td><td class="left">   implementations only support GET and HEAD.</td><td> </td><td class="right">   implementations only support GET and HEAD.</td><td class="lineno" valign="top"></td></tr>
    542       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    543       <tr><td class="lineno" valign="top"></td><td class="left">4.3.  Method Definitions</td><td> </td><td class="right">4.3.  Method Definitions</td><td class="lineno" valign="top"></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">4.3.1.  GET</td><td> </td><td class="right">4.3.1.  GET</td><td class="lineno" valign="top"></td></tr>
    546       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    547       <tr><td class="lineno" valign="top"></td><td class="left">   The GET method requests transfer of a current selected representation</td><td> </td><td class="right">   The GET method requests transfer of a current selected representation</td><td class="lineno" valign="top"></td></tr>
    548       <tr><td class="lineno" valign="top"></td><td class="left">   for the target resource.  GET is the primary mechanism of information</td><td> </td><td class="right">   for the target resource.  GET is the primary mechanism of information</td><td class="lineno" valign="top"></td></tr>
    549       <tr><td class="lineno" valign="top"></td><td class="left">   retrieval and the focus of almost all performance optimizations.</td><td> </td><td class="right">   retrieval and the focus of almost all performance optimizations.</td><td class="lineno" valign="top"></td></tr>
    550       <tr><td class="lineno" valign="top"></td><td class="left">   Hence, when people speak of retrieving some identifiable information</td><td> </td><td class="right">   Hence, when people speak of retrieving some identifiable information</td><td class="lineno" valign="top"></td></tr>
    551       <tr><td class="lineno" valign="top"></td><td class="left">   via HTTP, they are generally referring to making a GET request.</td><td> </td><td class="right">   via HTTP, they are generally referring to making a GET request.</td><td class="lineno" valign="top"></td></tr>
    552       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    553       <tr><td class="lineno" valign="top"></td><td class="left">   It is tempting to think of resource identifiers as remote file system</td><td> </td><td class="right">   It is tempting to think of resource identifiers as remote file system</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">   pathnames<span class="delete">,</span> and of representations as being a copy of the contents of</td><td> </td><td class="rblock">   pathnames and of representations as being a copy of the contents of</td><td class="lineno" valign="top"></td></tr>
    556       <tr><td class="lineno" valign="top"></td><td class="left">   such files.  In fact, that is how many resources are implemented (see</td><td> </td><td class="right">   such files.  In fact, that is how many resources are implemented (see</td><td class="lineno" valign="top"></td></tr>
    557       <tr><td class="lineno" valign="top"></td><td class="left">   Section 9.1 for related security considerations).  However, there are</td><td> </td><td class="right">   Section 9.1 for related security considerations).  However, there are</td><td class="lineno" valign="top"></td></tr>
    558       <tr><td class="lineno" valign="top"></td><td class="left">   no such limitations in practice.  The HTTP interface for a resource</td><td> </td><td class="right">   no such limitations in practice.  The HTTP interface for a resource</td><td class="lineno" valign="top"></td></tr>
    559       <tr><td class="lineno" valign="top"></td><td class="left">   is just as likely to be implemented as a tree of content objects, a</td><td> </td><td class="right">   is just as likely to be implemented as a tree of content objects, a</td><td class="lineno" valign="top"></td></tr>
    560       <tr><td class="lineno" valign="top"></td><td class="left">   programmatic view on various database records, or a gateway to other</td><td> </td><td class="right">   programmatic view on various database records, or a gateway to other</td><td class="lineno" valign="top"></td></tr>
    561       <tr><td class="lineno" valign="top"></td><td class="left">   information systems.  Even when the URI mapping mechanism is tied to</td><td> </td><td class="right">   information systems.  Even when the URI mapping mechanism is tied to</td><td class="lineno" valign="top"></td></tr>
    562       <tr><td class="lineno" valign="top"></td><td class="left">   a file system, an origin server might be configured to execute the</td><td> </td><td class="right">   a file system, an origin server might be configured to execute the</td><td class="lineno" valign="top"></td></tr>
    563       <tr><td class="lineno" valign="top"></td><td class="left">   files with the request as input and send the output as the</td><td> </td><td class="right">   files with the request as input and send the output as the</td><td class="lineno" valign="top"></td></tr>
    564       <tr><td><a name="diff0029" /></td></tr>
    565       <tr><td class="lineno" valign="top"></td><td class="lblock">   representation<span class="delete">,</span> rather than transfer the files directly.  Regardless,</td><td> </td><td class="rblock">   representation rather than transfer the files directly.  Regardless,</td><td class="lineno" valign="top"></td></tr>
    566       <tr><td class="lineno" valign="top"></td><td class="left">   only the origin server needs to know how each of its resource</td><td> </td><td class="right">   only the origin server needs to know how each of its resource</td><td class="lineno" valign="top"></td></tr>
    567       <tr><td><a name="diff0030" /></td></tr>
    568       <tr><td class="lineno" valign="top"></td><td class="lblock">   identifiers corresponds to an implementation<span class="delete">,</span> and how each</td><td> </td><td class="rblock">   identifiers corresponds to an implementation and how each</td><td class="lineno" valign="top"></td></tr>
    569       <tr><td class="lineno" valign="top"></td><td class="left">   implementation manages to select and send a current representation of</td><td> </td><td class="right">   implementation manages to select and send a current representation of</td><td class="lineno" valign="top"></td></tr>
    570       <tr><td class="lineno" valign="top"></td><td class="left">   the target resource in a response to GET.</td><td> </td><td class="right">   the target resource in a response to GET.</td><td class="lineno" valign="top"></td></tr>
    571       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    572       <tr><td class="lineno" valign="top"></td><td class="left">   A client can alter the semantics of GET to be a "range request",</td><td> </td><td class="right">   A client can alter the semantics of GET to be a "range request",</td><td class="lineno" valign="top"></td></tr>
    573       <tr><td class="lineno" valign="top"></td><td class="left">   requesting transfer of only some part(s) of the selected</td><td> </td><td class="right">   requesting transfer of only some part(s) of the selected</td><td class="lineno" valign="top"></td></tr>
    574       <tr><td class="lineno" valign="top"></td><td class="left">   representation, by sending a Range header field in the request</td><td> </td><td class="right">   representation, by sending a Range header field in the request</td><td class="lineno" valign="top"></td></tr>
    575       <tr><td class="lineno" valign="top"></td><td class="left">   ([RFC7233]).</td><td> </td><td class="right">   ([RFC7233]).</td><td class="lineno" valign="top"></td></tr>
    576       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    577       <tr><td class="lineno" valign="top"></td><td class="left">   A payload within a GET request message has no defined semantics;</td><td> </td><td class="right">   A payload within a GET request message has no defined semantics;</td><td class="lineno" valign="top"></td></tr>
    578       <tr><td class="lineno" valign="top"></td><td class="left">   sending a payload body on a GET request might cause some existing</td><td> </td><td class="right">   sending a payload body on a GET request might cause some existing</td><td class="lineno" valign="top"></td></tr>
    579       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    580       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 26, line 14</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 26, line 14</em></th><td></td></tr>
     509      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     510      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 26, line 14</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 26, line 14</em></th><td></td></tr>
    581511      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    582512      <tr><td class="lineno" valign="top"></td><td class="left">   o  Creating a new resource that has yet to be identified by the</td><td> </td><td class="right">   o  Creating a new resource that has yet to be identified by the</td><td class="lineno" valign="top"></td></tr>
     
    589519      <tr><td class="lineno" valign="top"></td><td class="left">   POST request; almost all of the status codes defined by this</td><td> </td><td class="right">   POST request; almost all of the status codes defined by this</td><td class="lineno" valign="top"></td></tr>
    590520      <tr><td class="lineno" valign="top"></td><td class="left">   specification might be received in a response to POST (the exceptions</td><td> </td><td class="right">   specification might be received in a response to POST (the exceptions</td><td class="lineno" valign="top"></td></tr>
    591       <tr><td><a name="diff0031" /></td></tr>
     521      <tr><td><a name="diff0027" /></td></tr>
    592522      <tr><td class="lineno" valign="top"></td><td class="lblock">   being <span class="delete">206, 304,</span> and <span class="delete">416).</span></td><td> </td><td class="rblock">   being <span class="insert">206 (Partial Content), 304 (Not Modified),</span> and <span class="insert">416 (Range Not</span></td><td class="lineno" valign="top"></td></tr>
    593523      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Satisfiable)).</span></td><td class="lineno" valign="top"></td></tr>
     
    603533      <tr><td class="lineno" valign="top"></td><td class="left">   explicit freshness information (see Section 4.2.1 of [RFC7234]).</td><td> </td><td class="right">   explicit freshness information (see Section 4.2.1 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
    604534      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    605       <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 28, line 18</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 28, line 19</em></th><td></td></tr>
     535      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 28, line 18</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 28, line 19</em></th><td></td></tr>
    606536      <tr><td class="lineno" valign="top"></td><td class="left">   intentionally hidden by the server.</td><td> </td><td class="right">   intentionally hidden by the server.</td><td class="lineno" valign="top"></td></tr>
    607537      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    614544      <tr><td class="lineno" valign="top"></td><td class="left">   reflects the new representation.  This requirement allows a user</td><td> </td><td class="right">   reflects the new representation.  This requirement allows a user</td><td class="lineno" valign="top"></td></tr>
    615545      <tr><td class="lineno" valign="top"></td><td class="left">   agent to know when the representation body it has in memory remains</td><td> </td><td class="right">   agent to know when the representation body it has in memory remains</td><td class="lineno" valign="top"></td></tr>
    616       <tr><td><a name="diff0032" /></td></tr>
     546      <tr><td><a name="diff0028" /></td></tr>
    617547      <tr><td class="lineno" valign="top"></td><td class="lblock">   current as a result of the PUT, thus not in need of <span class="delete">retrieving</span> again</td><td> </td><td class="rblock">   current as a result of the PUT, thus not in need of <span class="insert">being retrieved</span></td><td class="lineno" valign="top"></td></tr>
    618548      <tr><td class="lineno" valign="top"></td><td class="lblock">   from the origin server, and that the new validator(s) received in the</td><td> </td><td class="rblock">   again from the origin server, and that the new validator(s) received</td><td class="lineno" valign="top"></td></tr>
     
    630560      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    631561      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    632       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 28, line 43</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 28, line 44</em></th><td></td></tr>
     562      <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 28, line 43</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 28, line 44</em></th><td></td></tr>
    633563      <tr><td class="lineno" valign="top"></td><td class="left">   knows which target resource is desired.  A service that selects a</td><td> </td><td class="right">   knows which target resource is desired.  A service that selects a</td><td class="lineno" valign="top"></td></tr>
    634564      <tr><td class="lineno" valign="top"></td><td class="left">   proper URI on behalf of the client, after receiving a state-changing</td><td> </td><td class="right">   proper URI on behalf of the client, after receiving a state-changing</td><td class="lineno" valign="top"></td></tr>
     
    641571      <tr><td class="lineno" valign="top"></td><td class="left">   regarding whether or not to redirect the request.</td><td> </td><td class="right">   regarding whether or not to redirect the request.</td><td class="lineno" valign="top"></td></tr>
    642572      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    643       <tr><td><a name="diff0033" /></td></tr>
     573      <tr><td><a name="diff0029" /></td></tr>
    644574      <tr><td class="lineno" valign="top"></td><td class="lblock">   A PUT request applied to the target resource can have side<span class="delete">-</span>effects on</td><td> </td><td class="rblock">   A PUT request applied to the target resource can have side<span class="insert"> </span>effects on</td><td class="lineno" valign="top"></td></tr>
    645575      <tr><td class="lineno" valign="top"></td><td class="left">   other resources.  For example, an article might have a URI for</td><td> </td><td class="right">   other resources.  For example, an article might have a URI for</td><td class="lineno" valign="top"></td></tr>
     
    654584      <tr><td class="lineno" valign="top"></td><td class="left">   An origin server that allows PUT on a given target resource MUST send</td><td> </td><td class="right">   An origin server that allows PUT on a given target resource MUST send</td><td class="lineno" valign="top"></td></tr>
    655585      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    656       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 29, line 26</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 29, line 27</em></th><td></td></tr>
    657       <tr><td class="lineno" valign="top"></td><td class="left">   request passes through a cache that has one or more stored responses</td><td> </td><td class="right">   request passes through a cache that has one or more stored responses</td><td class="lineno" valign="top"></td></tr>
    658       <tr><td class="lineno" valign="top"></td><td class="left">   for the effective request URI, those stored responses will be</td><td> </td><td class="right">   for the effective request URI, those stored responses will be</td><td class="lineno" valign="top"></td></tr>
    659       <tr><td class="lineno" valign="top"></td><td class="left">   invalidated (see Section 4.4 of [RFC7234]).</td><td> </td><td class="right">   invalidated (see Section 4.4 of [RFC7234]).</td><td class="lineno" valign="top"></td></tr>
    660       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    661       <tr><td class="lineno" valign="top"></td><td class="left">4.3.5.  DELETE</td><td> </td><td class="right">4.3.5.  DELETE</td><td class="lineno" valign="top"></td></tr>
    662       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    663       <tr><td class="lineno" valign="top"></td><td class="left">   The DELETE method requests that the origin server remove the</td><td> </td><td class="right">   The DELETE method requests that the origin server remove the</td><td class="lineno" valign="top"></td></tr>
    664       <tr><td class="lineno" valign="top"></td><td class="left">   association between the target resource and its current</td><td> </td><td class="right">   association between the target resource and its current</td><td class="lineno" valign="top"></td></tr>
    665       <tr><td class="lineno" valign="top"></td><td class="left">   functionality.  In effect, this method is similar to the rm command</td><td> </td><td class="right">   functionality.  In effect, this method is similar to the rm command</td><td class="lineno" valign="top"></td></tr>
    666       <tr><td class="lineno" valign="top"></td><td class="left">   in UNIX: it expresses a deletion operation on the URI mapping of the</td><td> </td><td class="right">   in UNIX: it expresses a deletion operation on the URI mapping of the</td><td class="lineno" valign="top"></td></tr>
    667       <tr><td><a name="diff0034" /></td></tr>
    668       <tr><td class="lineno" valign="top"></td><td class="lblock">   origin server<span class="delete">,</span> rather than an expectation that the previously</td><td> </td><td class="rblock">   origin server rather than an expectation that the previously</td><td class="lineno" valign="top"></td></tr>
    669       <tr><td class="lineno" valign="top"></td><td class="left">   associated information be deleted.</td><td> </td><td class="right">   associated information be deleted.</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">   If the target resource has one or more current representations, they</td><td> </td><td class="right">   If the target resource has one or more current representations, they</td><td class="lineno" valign="top"></td></tr>
    672       <tr><td class="lineno" valign="top"></td><td class="left">   might or might not be destroyed by the origin server, and the</td><td> </td><td class="right">   might or might not be destroyed by the origin server, and the</td><td class="lineno" valign="top"></td></tr>
    673       <tr><td class="lineno" valign="top"></td><td class="left">   associated storage might or might not be reclaimed, depending</td><td> </td><td class="right">   associated storage might or might not be reclaimed, depending</td><td class="lineno" valign="top"></td></tr>
    674       <tr><td class="lineno" valign="top"></td><td class="left">   entirely on the nature of the resource and its implementation by the</td><td> </td><td class="right">   entirely on the nature of the resource and its implementation by the</td><td class="lineno" valign="top"></td></tr>
    675       <tr><td class="lineno" valign="top"></td><td class="left">   origin server (which are beyond the scope of this specification).</td><td> </td><td class="right">   origin server (which are beyond the scope of this specification).</td><td class="lineno" valign="top"></td></tr>
    676       <tr><td class="lineno" valign="top"></td><td class="left">   Likewise, other implementation aspects of a resource might need to be</td><td> </td><td class="right">   Likewise, other implementation aspects of a resource might need to be</td><td class="lineno" valign="top"></td></tr>
    677       <tr><td class="lineno" valign="top"></td><td class="left">   deactivated or archived as a result of a DELETE, such as database or</td><td> </td><td class="right">   deactivated or archived as a result of a DELETE, such as database or</td><td class="lineno" valign="top"></td></tr>
    678       <tr><td class="lineno" valign="top"></td><td class="left">   gateway connections.  In general, it is assumed that the origin</td><td> </td><td class="right">   gateway connections.  In general, it is assumed that the origin</td><td class="lineno" valign="top"></td></tr>
    679       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    680       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 30, line 31</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 30, line 33</em></th><td></td></tr>
     586      <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 30, line 31</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 30, line 33</em></th><td></td></tr>
    681587      <tr><td class="lineno" valign="top"></td><td class="left">   The CONNECT method requests that the recipient establish a tunnel to</td><td> </td><td class="right">   The CONNECT method requests that the recipient establish a tunnel to</td><td class="lineno" valign="top"></td></tr>
    682588      <tr><td class="lineno" valign="top"></td><td class="left">   the destination origin server identified by the request-target and,</td><td> </td><td class="right">   the destination origin server identified by the request-target and,</td><td class="lineno" valign="top"></td></tr>
     
    689595      <tr><td class="lineno" valign="top"></td><td class="left">   CONNECT is intended only for use in requests to a proxy.  An origin</td><td> </td><td class="right">   CONNECT is intended only for use in requests to a proxy.  An origin</td><td class="lineno" valign="top"></td></tr>
    690596      <tr><td class="lineno" valign="top"></td><td class="left">   server that receives a CONNECT request for itself MAY respond with a</td><td> </td><td class="right">   server that receives a CONNECT request for itself MAY respond with a</td><td class="lineno" valign="top"></td></tr>
    691       <tr><td><a name="diff0035" /></td></tr>
     597      <tr><td><a name="diff0030" /></td></tr>
    692598      <tr><td class="lineno" valign="top"></td><td class="lblock">   2xx status code to indicate that a connection is established.</td><td> </td><td class="rblock">   2xx <span class="insert">(Successful)</span> status code to indicate that a connection is</td><td class="lineno" valign="top"></td></tr>
    693599      <tr><td class="lineno" valign="top"></td><td class="lblock">   However, most origin servers do not implement CONNECT.</td><td> </td><td class="rblock">   established.  However, most origin servers do not implement CONNECT.</td><td class="lineno" valign="top"></td></tr>
     
    703609      <tr><td class="lineno" valign="top"></td><td class="left">   The recipient proxy can establish a tunnel either by directly</td><td> </td><td class="right">   The recipient proxy can establish a tunnel either by directly</td><td class="lineno" valign="top"></td></tr>
    704610      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    705       <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 31, line 42</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 31, line 43</em></th><td></td></tr>
     611      <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 31, line 42</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 31, line 43</em></th><td></td></tr>
    706612      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    707613      <tr><td class="lineno" valign="top"></td><td class="left">   A payload within a CONNECT request message has no defined semantics;</td><td> </td><td class="right">   A payload within a CONNECT request message has no defined semantics;</td><td class="lineno" valign="top"></td></tr>
     
    714620      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    715621      <tr><td class="lineno" valign="top"></td><td class="left">   The OPTIONS method requests information about the communication</td><td> </td><td class="right">   The OPTIONS method requests information about the communication</td><td class="lineno" valign="top"></td></tr>
    716       <tr><td><a name="diff0036" /></td></tr>
     622      <tr><td><a name="diff0031" /></td></tr>
    717623      <tr><td class="lineno" valign="top"></td><td class="lblock">   options available for the target resource, <span class="delete">either at</span> the origin</td><td> </td><td class="rblock">   options available for the target resource, <span class="insert">at either</span> the origin</td><td class="lineno" valign="top"></td></tr>
    718624      <tr><td class="lineno" valign="top"></td><td class="left">   server or an intervening intermediary.  This method allows a client</td><td> </td><td class="right">   server or an intervening intermediary.  This method allows a client</td><td class="lineno" valign="top"></td></tr>
     
    727633      <tr><td class="lineno" valign="top"></td><td class="left">   "ping" or "no-op" type of method; it does nothing beyond allowing the</td><td> </td><td class="right">   "ping" or "no-op" type of method; it does nothing beyond allowing the</td><td class="lineno" valign="top"></td></tr>
    728634      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    729       <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
     635      <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
    730636      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    731637      <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>
     
    738644      <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>
    739645      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    740       <tr><td><a name="diff0037" /></td></tr>
     646      <tr><td><a name="diff0032" /></td></tr>
    741647      <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>
    742648      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    751657      <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>
    752658      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    753       <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 36, line 12</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 36, line 12</em></th><td></td></tr>
     659      <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 36, line 12</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 36, line 12</em></th><td></td></tr>
    754660      <tr><td class="lineno" valign="top"></td><td class="left">   determined by examining just the request-line and header fields, or</td><td> </td><td class="right">   determined by examining just the request-line and header fields, or</td><td class="lineno" valign="top"></td></tr>
    755661      <tr><td class="lineno" valign="top"></td><td class="left">   begin forwarding the request toward the origin server by sending a</td><td> </td><td class="right">   begin forwarding the request toward the origin server by sending a</td><td class="lineno" valign="top"></td></tr>
     
    762668      <tr><td class="lineno" valign="top"></td><td class="left">      Note: The Expect header field was added after the original</td><td> </td><td class="right">      Note: The Expect header field was added after the original</td><td class="lineno" valign="top"></td></tr>
    763669      <tr><td class="lineno" valign="top"></td><td class="left">      publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td> </td><td class="right">      publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td class="lineno" valign="top"></td></tr>
    764       <tr><td><a name="diff0038" /></td></tr>
     670      <tr><td><a name="diff0033" /></td></tr>
    765671      <tr><td class="lineno" valign="top"></td><td class="lblock">      interim 100 response and the general mechanism for indicating</td><td> </td><td class="rblock">      interim 100 <span class="insert">(Continue)</span> response and the general mechanism for</td><td class="lineno" valign="top"></td></tr>
    766672      <tr><td class="lineno" valign="top"></td><td class="lblock">      must-understand extensions.  However, the extension mechanism has</td><td> </td><td class="rblock">      indicating must-understand extensions.  However, the extension</td><td class="lineno" valign="top"></td></tr>
     
    781687      <tr><td class="lineno" valign="top"></td><td class="left">     Max-Forwards = 1*DIGIT</td><td> </td><td class="right">     Max-Forwards = 1*DIGIT</td><td class="lineno" valign="top"></td></tr>
    782688      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    783       <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 36, line 40</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 36, line 40</em></th><td></td></tr>
    784       <tr><td class="lineno" valign="top"></td><td class="left">   The Max-Forwards value is a decimal integer indicating the remaining</td><td> </td><td class="right">   The Max-Forwards value is a decimal integer indicating the remaining</td><td class="lineno" valign="top"></td></tr>
    785       <tr><td class="lineno" valign="top"></td><td class="left">   number of times this request message can be forwarded.</td><td> </td><td class="right">   number of times this request message can be forwarded.</td><td class="lineno" valign="top"></td></tr>
    786       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    787       <tr><td class="lineno" valign="top"></td><td class="left">   Each intermediary that receives a TRACE or OPTIONS request containing</td><td> </td><td class="right">   Each intermediary that receives a TRACE or OPTIONS request containing</td><td class="lineno" valign="top"></td></tr>
    788       <tr><td class="lineno" valign="top"></td><td class="left">   a Max-Forwards header field MUST check and update its value prior to</td><td> </td><td class="right">   a Max-Forwards header field MUST check and update its value prior to</td><td class="lineno" valign="top"></td></tr>
    789       <tr><td class="lineno" valign="top"></td><td class="left">   forwarding the request.  If the received value is zero (0), the</td><td> </td><td class="right">   forwarding the request.  If the received value is zero (0), the</td><td class="lineno" valign="top"></td></tr>
    790       <tr><td class="lineno" valign="top"></td><td class="left">   intermediary MUST NOT forward the request; instead, the intermediary</td><td> </td><td class="right">   intermediary MUST NOT forward the request; instead, the intermediary</td><td class="lineno" valign="top"></td></tr>
    791       <tr><td class="lineno" valign="top"></td><td class="left">   MUST respond as the final recipient.  If the received Max-Forwards</td><td> </td><td class="right">   MUST respond as the final recipient.  If the received Max-Forwards</td><td class="lineno" valign="top"></td></tr>
    792       <tr><td class="lineno" valign="top"></td><td class="left">   value is greater than zero, the intermediary MUST generate an updated</td><td> </td><td class="right">   value is greater than zero, the intermediary MUST generate an updated</td><td class="lineno" valign="top"></td></tr>
    793       <tr><td class="lineno" valign="top"></td><td class="left">   Max-Forwards field in the forwarded message with a field-value that</td><td> </td><td class="right">   Max-Forwards field in the forwarded message with a field-value that</td><td class="lineno" valign="top"></td></tr>
    794       <tr><td><a name="diff0039" /></td></tr>
    795       <tr><td class="lineno" valign="top"></td><td class="lblock">   is the lesser of<span class="delete">: a) the received value decremented by one (1),</span> or b)</td><td> </td><td class="rblock">   is the lesser of<span class="insert"> a) the received value decremented by one (1)</span> or b)</td><td class="lineno" valign="top"></td></tr>
    796       <tr><td class="lineno" valign="top"></td><td class="left">   the recipient's maximum supported value for Max-Forwards.</td><td> </td><td class="right">   the recipient's maximum supported value for Max-Forwards.</td><td class="lineno" valign="top"></td></tr>
    797       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    798       <tr><td class="lineno" valign="top"></td><td class="left">   A recipient MAY ignore a Max-Forwards header field received with any</td><td> </td><td class="right">   A recipient MAY ignore a Max-Forwards header field received with any</td><td class="lineno" valign="top"></td></tr>
    799       <tr><td class="lineno" valign="top"></td><td class="left">   other request methods.</td><td> </td><td class="right">   other request methods.</td><td class="lineno" valign="top"></td></tr>
    800       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    801       <tr><td class="lineno" valign="top"></td><td class="left">5.2.  Conditionals</td><td> </td><td class="right">5.2.  Conditionals</td><td class="lineno" valign="top"></td></tr>
    802       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    803       <tr><td class="lineno" valign="top"></td><td class="left">   The HTTP conditional request header fields [RFC7232] allow a client</td><td> </td><td class="right">   The HTTP conditional request header fields [RFC7232] allow a client</td><td class="lineno" valign="top"></td></tr>
    804       <tr><td class="lineno" valign="top"></td><td class="left">   to place a precondition on the state of the target resource, so that</td><td> </td><td class="right">   to place a precondition on the state of the target resource, so that</td><td class="lineno" valign="top"></td></tr>
    805       <tr><td class="lineno" valign="top"></td><td class="left">   the action corresponding to the method semantics will not be applied</td><td> </td><td class="right">   the action corresponding to the method semantics will not be applied</td><td class="lineno" valign="top"></td></tr>
    806       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    807       <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 39, line 12</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 39, line 12</em></th><td></td></tr>
     689      <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 39, line 12</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 39, line 12</em></th><td></td></tr>
    808690      <tr><td class="lineno" valign="top"></td><td class="left">      to be unlikely given the lack of any "q" parameters in the IANA</td><td> </td><td class="right">      to be unlikely given the lack of any "q" parameters in the IANA</td><td class="lineno" valign="top"></td></tr>
    809691      <tr><td class="lineno" valign="top"></td><td class="left">      media type registry and the rare usage of any media type</td><td> </td><td class="right">      media type registry and the rare usage of any media type</td><td class="lineno" valign="top"></td></tr>
     
    816698      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    817699      <tr><td class="lineno" valign="top"></td><td class="left">   is interpreted as "I prefer audio/basic, but send me any audio type</td><td> </td><td class="right">   is interpreted as "I prefer audio/basic, but send me any audio type</td><td class="lineno" valign="top"></td></tr>
    818       <tr><td><a name="diff0040" /></td></tr>
     700      <tr><td><a name="diff0034" /></td></tr>
    819701      <tr><td class="lineno" valign="top"></td><td class="lblock">   if it is the best available after an 80% mark<span class="delete">-</span>down in quality".</td><td> </td><td class="rblock">   if it is the best available after an 80% markdown in quality".</td><td class="lineno" valign="top"></td></tr>
    820702      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    829711      <tr><td class="lineno" valign="top"></td><td class="left">   A more elaborate example is</td><td> </td><td class="right">   A more elaborate example is</td><td class="lineno" valign="top"></td></tr>
    830712      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    831       <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 43, line 4</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 43, line 4</em></th><td></td></tr>
    832       <tr><td class="lineno" valign="top"></td><td class="left">     Accept-Language: da, en-gb;q=0.8, en;q=0.7</td><td> </td><td class="right">     Accept-Language: da, en-gb;q=0.8, en;q=0.7</td><td class="lineno" valign="top"></td></tr>
    833       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    834       <tr><td class="lineno" valign="top"></td><td class="left">   would mean: "I prefer Danish, but will accept British English and</td><td> </td><td class="right">   would mean: "I prefer Danish, but will accept British English and</td><td class="lineno" valign="top"></td></tr>
    835       <tr><td class="lineno" valign="top"></td><td class="left">   other types of English".</td><td> </td><td class="right">   other types of English".</td><td class="lineno" valign="top"></td></tr>
    836       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    837       <tr><td class="lineno" valign="top"></td><td class="left">   A request without any Accept-Language header field implies that the</td><td> </td><td class="right">   A request without any Accept-Language header field implies that the</td><td class="lineno" valign="top"></td></tr>
    838       <tr><td class="lineno" valign="top"></td><td class="left">   user agent will accept any language in response.  If the header field</td><td> </td><td class="right">   user agent will accept any language in response.  If the header field</td><td class="lineno" valign="top"></td></tr>
    839       <tr><td class="lineno" valign="top"></td><td class="left">   is present in a request and none of the available representations for</td><td> </td><td class="right">   is present in a request and none of the available representations for</td><td class="lineno" valign="top"></td></tr>
    840       <tr><td class="lineno" valign="top"></td><td class="left">   the response have a matching language tag, the origin server can</td><td> </td><td class="right">   the response have a matching language tag, the origin server can</td><td class="lineno" valign="top"></td></tr>
    841       <tr><td class="lineno" valign="top"></td><td class="left">   either disregard the header field by treating the response as if it</td><td> </td><td class="right">   either disregard the header field by treating the response as if it</td><td class="lineno" valign="top"></td></tr>
    842       <tr><td><a name="diff0041" /></td></tr>
    843       <tr><td class="lineno" valign="top"></td><td class="lblock">   is not subject to content negotiation<span class="delete">,</span> or honor the header field by</td><td> </td><td class="rblock">   is not subject to content negotiation or honor the header field by</td><td class="lineno" valign="top"></td></tr>
    844       <tr><td class="lineno" valign="top"></td><td class="left">   sending a 406 (Not Acceptable) response.  However, the latter is not</td><td> </td><td class="right">   sending a 406 (Not Acceptable) response.  However, the latter is not</td><td class="lineno" valign="top"></td></tr>
    845       <tr><td class="lineno" valign="top"></td><td class="left">   encouraged, as doing so can prevent users from accessing content that</td><td> </td><td class="right">   encouraged, as doing so can prevent users from accessing content that</td><td class="lineno" valign="top"></td></tr>
    846       <tr><td class="lineno" valign="top"></td><td class="left">   they might be able to use (with translation software, for example).</td><td> </td><td class="right">   they might be able to use (with translation software, for example).</td><td class="lineno" valign="top"></td></tr>
    847       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    848       <tr><td class="lineno" valign="top"></td><td class="left">   Note that some recipients treat the order in which language tags are</td><td> </td><td class="right">   Note that some recipients treat the order in which language tags are</td><td class="lineno" valign="top"></td></tr>
    849       <tr><td class="lineno" valign="top"></td><td class="left">   listed as an indication of descending priority, particularly for tags</td><td> </td><td class="right">   listed as an indication of descending priority, particularly for tags</td><td class="lineno" valign="top"></td></tr>
    850       <tr><td class="lineno" valign="top"></td><td class="left">   that are assigned equal quality values (no value is the same as q=1).</td><td> </td><td class="right">   that are assigned equal quality values (no value is the same as q=1).</td><td class="lineno" valign="top"></td></tr>
    851       <tr><td class="lineno" valign="top"></td><td class="left">   However, this behavior cannot be relied upon.  For consistency and to</td><td> </td><td class="right">   However, this behavior cannot be relied upon.  For consistency and to</td><td class="lineno" valign="top"></td></tr>
    852       <tr><td class="lineno" valign="top"></td><td class="left">   maximize interoperability, many user agents assign each language tag</td><td> </td><td class="right">   maximize interoperability, many user agents assign each language tag</td><td class="lineno" valign="top"></td></tr>
    853       <tr><td class="lineno" valign="top"></td><td class="left">   a unique quality value while also listing them in order of decreasing</td><td> </td><td class="right">   a unique quality value while also listing them in order of decreasing</td><td class="lineno" valign="top"></td></tr>
    854       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    855       <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 43, line 30</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 43, line 30</em></th><td></td></tr>
    856       <tr><td class="lineno" valign="top"></td><td class="left">   scheme for their requirements.  The "Basic Filtering" scheme</td><td> </td><td class="right">   scheme for their requirements.  The "Basic Filtering" scheme</td><td class="lineno" valign="top"></td></tr>
    857       <tr><td class="lineno" valign="top"></td><td class="left">   ([RFC4647], Section 3.3.1) is identical to the matching scheme that</td><td> </td><td class="right">   ([RFC4647], Section 3.3.1) is identical to the matching scheme that</td><td class="lineno" valign="top"></td></tr>
    858       <tr><td class="lineno" valign="top"></td><td class="left">   was previously defined for HTTP in Section 14.4 of [RFC2616].</td><td> </td><td class="right">   was previously defined for HTTP in Section 14.4 of [RFC2616].</td><td class="lineno" valign="top"></td></tr>
    859       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    860       <tr><td class="lineno" valign="top"></td><td class="left">   It might be contrary to the privacy expectations of the user to send</td><td> </td><td class="right">   It might be contrary to the privacy expectations of the user to send</td><td class="lineno" valign="top"></td></tr>
    861       <tr><td class="lineno" valign="top"></td><td class="left">   an Accept-Language header field with the complete linguistic</td><td> </td><td class="right">   an Accept-Language header field with the complete linguistic</td><td class="lineno" valign="top"></td></tr>
    862       <tr><td class="lineno" valign="top"></td><td class="left">   preferences of the user in every request (Section 9.7).</td><td> </td><td class="right">   preferences of the user in every request (Section 9.7).</td><td class="lineno" valign="top"></td></tr>
    863       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    864       <tr><td class="lineno" valign="top"></td><td class="left">   Since intelligibility is highly dependent on the individual user,</td><td> </td><td class="right">   Since intelligibility is highly dependent on the individual user,</td><td class="lineno" valign="top"></td></tr>
    865       <tr><td class="lineno" valign="top"></td><td class="left">   user agents need to allow user control over the linguistic preference</td><td> </td><td class="right">   user agents need to allow user control over the linguistic preference</td><td class="lineno" valign="top"></td></tr>
    866       <tr><td><a name="diff0042" /></td></tr>
    867       <tr><td class="lineno" valign="top"></td><td class="lblock">   (either through configuration of the user agent itself<span class="delete">,</span> or by</td><td> </td><td class="rblock">   (either through configuration of the user agent itself or by</td><td class="lineno" valign="top"></td></tr>
    868       <tr><td class="lineno" valign="top"></td><td class="left">   defaulting to a user controllable system setting).  A user agent that</td><td> </td><td class="right">   defaulting to a user controllable system setting).  A user agent that</td><td class="lineno" valign="top"></td></tr>
    869       <tr><td class="lineno" valign="top"></td><td class="left">   does not provide such control to the user MUST NOT send an Accept-</td><td> </td><td class="right">   does not provide such control to the user MUST NOT send an Accept-</td><td class="lineno" valign="top"></td></tr>
    870       <tr><td class="lineno" valign="top"></td><td class="left">   Language header field.</td><td> </td><td class="right">   Language header field.</td><td class="lineno" valign="top"></td></tr>
    871       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    872       <tr><td class="lineno" valign="top"></td><td class="left">      Note: User agents ought to provide guidance to users when setting</td><td> </td><td class="right">      Note: User agents ought to provide guidance to users when setting</td><td class="lineno" valign="top"></td></tr>
    873       <tr><td class="lineno" valign="top"></td><td class="left">      a preference, since users are rarely familiar with the details of</td><td> </td><td class="right">      a preference, since users are rarely familiar with the details of</td><td class="lineno" valign="top"></td></tr>
    874       <tr><td class="lineno" valign="top"></td><td class="left">      language matching as described above.  For example, users might</td><td> </td><td class="right">      language matching as described above.  For example, users might</td><td class="lineno" valign="top"></td></tr>
    875       <tr><td class="lineno" valign="top"></td><td class="left">      assume that on selecting "en-gb", they will be served any kind of</td><td> </td><td class="right">      assume that on selecting "en-gb", they will be served any kind of</td><td class="lineno" valign="top"></td></tr>
    876       <tr><td class="lineno" valign="top"></td><td class="left">      English document if British English is not available.  A user</td><td> </td><td class="right">      English document if British English is not available.  A user</td><td class="lineno" valign="top"></td></tr>
    877       <tr><td class="lineno" valign="top"></td><td class="left">      agent might suggest, in such a case, to add "en" to the list for</td><td> </td><td class="right">      agent might suggest, in such a case, to add "en" to the list for</td><td class="lineno" valign="top"></td></tr>
    878       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    879       <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>
     713      <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 44, line 30</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 44, line 30</em></th><td></td></tr>
    880714      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+---------------+</td><td> </td><td class="right">   +-------------------+---------------+</td><td class="lineno" valign="top"></td></tr>
    881715      <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>
     
    888722      <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>
    889723      <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>
    890       <tr><td><a name="diff0043" /></td></tr>
     724      <tr><td><a name="diff0035" /></td></tr>
    891725      <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>
    892726      <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>
     
    901735      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    902736      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    903       <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr>
     737      <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 45, line 31</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 45, line 31</em></th><td></td></tr>
    904738      <tr><td class="lineno" valign="top"></td><td class="left">   denying links from other sites (so-called "deep linking") or</td><td> </td><td class="right">   denying links from other sites (so-called "deep linking") or</td><td class="lineno" valign="top"></td></tr>
    905739      <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>
     
    912746      <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>
    913747      <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>
    914       <tr><td><a name="diff0044" /></td></tr>
     748      <tr><td><a name="diff0036" /></td></tr>
    915749      <tr><td class="lineno" valign="top"></td><td class="lblock">   user's bookmarks/favorites), the user agent MUST either exclude</td><td> </td><td class="rblock">   user's bookmarks/favorites), the user agent MUST either exclude<span class="insert"> the</span></td><td class="lineno" valign="top"></td></tr>
    916750      <tr><td class="lineno" valign="top"></td><td class="left">   Referer or send it with a value of "about:blank".</td><td> </td><td class="right">   Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr>
     
    930764      <tr><td class="lineno" valign="top"></td><td class="left">   Some intermediaries have been known to indiscriminately remove</td><td> </td><td class="right">   Some intermediaries have been known to indiscriminately remove</td><td class="lineno" valign="top"></td></tr>
    931765      <tr><td class="lineno" valign="top"></td><td class="left">   Referer header fields from outgoing requests.  This has the</td><td> </td><td class="right">   Referer header fields from outgoing requests.  This has the</td><td class="lineno" valign="top"></td></tr>
    932       <tr><td><a name="diff0045" /></td></tr>
     766      <tr><td><a name="diff0037" /></td></tr>
    933767      <tr><td class="lineno" valign="top"></td><td class="lblock">   unfortunate side<span class="delete">-</span>effect of interfering with protection against CSRF</td><td> </td><td class="rblock">   unfortunate side<span class="insert"> </span>effect of interfering with protection against CSRF</td><td class="lineno" valign="top"></td></tr>
    934768      <tr><td class="lineno" valign="top"></td><td class="left">   attacks, which can be far more harmful to their users.</td><td> </td><td class="right">   attacks, which can be far more harmful to their users.</td><td class="lineno" valign="top"></td></tr>
     
    946780      <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>
    947781      <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>
    948       <tr><td><a name="diff0046" /></td></tr>
     782      <tr><td><a name="diff0038" /></td></tr>
    949783      <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>
    950784      <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>
     
    956790      <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>
    957791      <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>
    958       <tr><td><a name="diff0047" /></td></tr>
     792      <tr><td><a name="diff0039" /></td></tr>
    959793      <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>
    960794      <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>
    961795      <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>
    962       <tr><td><a name="diff0048" /></td></tr>
     796      <tr><td><a name="diff0040" /></td></tr>
    963797      <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>
    964798      <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>
     
    969803      <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>
    970804      <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>
    971       <tr><td><a name="diff0049" /></td></tr>
     805      <tr><td><a name="diff0041" /></td></tr>
    972806      <tr><td class="lineno" valign="top"></td><td class="lblock">   advertising or other non<span class="delete">-</span>essential information within the product</td><td> </td><td class="rblock">   advertising or other nonessential information within the product</td><td class="lineno" valign="top"></td></tr>
    973807      <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>
    974808      <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>
    975       <tr><td><a name="diff0050" /></td></tr>
     809      <tr><td><a name="diff0042" /></td></tr>
    976810      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the same product name ought <span class="delete">to only</span> differ in the product-version</td><td> </td><td class="rblock">   of the same product name ought <span class="insert">only to</span> differ in the product-version</td><td class="lineno" valign="top"></td></tr>
    977811      <tr><td class="lineno" valign="top"></td><td class="left">   portion of the product identifier).</td><td> </td><td class="right">   portion of the product identifier).</td><td class="lineno" valign="top"></td></tr>
     
    993827      <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>
    994828      <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>
    995       <tr><td><a name="diff0051" /></td></tr>
     829      <tr><td><a name="diff0043" /></td></tr>
    996830      <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>
    997831      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    998832      <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>
    999833      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1000       <tr><td><a name="diff0052" /></td></tr>
     834      <tr><td><a name="diff0044" /></td></tr>
    1001835      <tr><td class="lineno" valign="top"></td><td class="lblock">   The status-code element is a <span class="delete">3-digit</span> integer code giving the result</td><td> </td><td class="rblock">   The status-code element is a <span class="insert">three-digit</span> integer code giving the</td><td class="lineno" valign="top"></td></tr>
    1002836      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the attempt to understand and satisfy the request.</td><td> </td><td class="rblock">   result of the attempt to understand and satisfy the request.</td><td class="lineno" valign="top"></td></tr>
     
    1012846      <tr><td class="lineno" valign="top"></td><td class="left">   For example, if an unrecognized status code of 471 is received by a</td><td> </td><td class="right">   For example, if an unrecognized status code of 471 is received by a</td><td class="lineno" valign="top"></td></tr>
    1013847      <tr><td class="lineno" valign="top"></td><td class="left">   client, the client can assume that there was something wrong with its</td><td> </td><td class="right">   client, the client can assume that there was something wrong with its</td><td class="lineno" valign="top"></td></tr>
    1014       <tr><td><a name="diff0053" /></td></tr>
     848      <tr><td><a name="diff0045" /></td></tr>
    1015849      <tr><td class="lineno" valign="top"></td><td class="lblock">   request and treat the response as if it had received a 400 status</td><td> </td><td class="rblock">   request and treat the response as if it had received a 400 <span class="insert">(Bad</span></td><td class="lineno" valign="top"></td></tr>
    1016850      <tr><td class="lineno" valign="top"></td><td class="lblock">   code.  The response message will usually contain a representation</td><td> </td><td class="rblock"><span class="insert">   Request)</span> status code.  The response message will usually contain a</td><td class="lineno" valign="top"></td></tr>
     
    1018852      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1019853      <tr><td class="lineno" valign="top"></td><td class="left">   The first digit of the status-code defines the class of response.</td><td> </td><td class="right">   The first digit of the status-code defines the class of response.</td><td class="lineno" valign="top"></td></tr>
    1020       <tr><td><a name="diff0054" /></td></tr>
     854      <tr><td><a name="diff0046" /></td></tr>
    1021855      <tr><td class="lineno" valign="top"></td><td class="lblock">   The last two digits do not have any categorization role.  There are <span class="delete">5</span></td><td> </td><td class="rblock">   The last two digits do not have any categorization role.  There are</td><td class="lineno" valign="top"></td></tr>
    1022856      <tr><td class="lineno" valign="top"></td><td class="lblock">   values for the first digit:</td><td> </td><td class="rblock">   <span class="insert">five</span> values for the first digit:</td><td class="lineno" valign="top"></td></tr>
     
    1032866      <tr><td class="lineno" valign="top"></td><td class="left">   o  4xx (Client Error): The request contains bad syntax or cannot be</td><td> </td><td class="right">   o  4xx (Client Error): The request contains bad syntax or cannot be</td><td class="lineno" valign="top"></td></tr>
    1033867      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1034       <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr>
     868      <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr>
    1035869      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1036870      <tr><td class="lineno" valign="top"></td><td class="left">6.1.  Overview of Status Codes</td><td> </td><td class="right">6.1.  Overview of Status Codes</td><td class="lineno" valign="top"></td></tr>
     
    1043877      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1044878      <tr><td class="lineno" valign="top"></td><td class="left">   Responses with status codes that are defined as cacheable by default</td><td> </td><td class="right">   Responses with status codes that are defined as cacheable by default</td><td class="lineno" valign="top"></td></tr>
    1045       <tr><td><a name="diff0055" /></td></tr>
     879      <tr><td><a name="diff0047" /></td></tr>
    1046880      <tr><td class="lineno" valign="top"></td><td class="lblock">   (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this</td><td> </td><td class="rblock">   (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, <span class="insert">and</span> 501 in</td><td class="lineno" valign="top"></td></tr>
    1047881      <tr><td class="lineno" valign="top"></td><td class="lblock">   specification) can be reused by a cache with heuristic expiration</td><td> </td><td class="rblock">   this specification) can be reused by a cache with heuristic</td><td class="lineno" valign="top"></td></tr>
     
    1051885      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1052886      <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
    1053       <tr><td><a name="diff0056" /></td></tr>
     887      <tr><td><a name="diff0048" /></td></tr>
    1054888      <tr><td class="lineno" valign="top"></td><td class="lblock">   | <span class="delete">code | reason-p</span>hrase                 | Defined in...            |</td><td> </td><td class="rblock">   | <span class="insert">Code | Reason-P</span>hrase                 | Defined in...            |</td><td class="lineno" valign="top"></td></tr>
    1055889      <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
     
    1064898      <tr><td class="lineno" valign="top"></td><td class="left">   | 206  | Partial Content               | Section 4.1 of [RFC7233] |</td><td> </td><td class="right">   | 206  | Partial Content               | Section 4.1 of [RFC7233] |</td><td class="lineno" valign="top"></td></tr>
    1065899      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1066       <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 50, line 13</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 50, line 13</em></th><td></td></tr>
    1067       <tr><td class="lineno" valign="top"></td><td class="left">   extension status codes defined in other specifications.  The complete</td><td> </td><td class="right">   extension status codes defined in other specifications.  The complete</td><td class="lineno" valign="top"></td></tr>
    1068       <tr><td class="lineno" valign="top"></td><td class="left">   list of status codes is maintained by IANA.  See Section 8.2 for</td><td> </td><td class="right">   list of status codes is maintained by IANA.  See Section 8.2 for</td><td class="lineno" valign="top"></td></tr>
    1069       <tr><td class="lineno" valign="top"></td><td class="left">   details.</td><td> </td><td class="right">   details.</td><td class="lineno" valign="top"></td></tr>
    1070       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1071       <tr><td class="lineno" valign="top"></td><td class="left">6.2.  Informational 1xx</td><td> </td><td class="right">6.2.  Informational 1xx</td><td class="lineno" valign="top"></td></tr>
    1072       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1073       <tr><td class="lineno" valign="top"></td><td class="left">   The 1xx (Informational) class of status code indicates an interim</td><td> </td><td class="right">   The 1xx (Informational) class of status code indicates an interim</td><td class="lineno" valign="top"></td></tr>
    1074       <tr><td class="lineno" valign="top"></td><td class="left">   response for communicating connection status or request progress</td><td> </td><td class="right">   response for communicating connection status or request progress</td><td class="lineno" valign="top"></td></tr>
    1075       <tr><td class="lineno" valign="top"></td><td class="left">   prior to completing the requested action and sending a final</td><td> </td><td class="right">   prior to completing the requested action and sending a final</td><td class="lineno" valign="top"></td></tr>
    1076       <tr><td class="lineno" valign="top"></td><td class="left">   response.  All 1xx responses consist of only the status-line and</td><td> </td><td class="right">   response.  All 1xx responses consist of only the status-line and</td><td class="lineno" valign="top"></td></tr>
    1077       <tr><td><a name="diff0057" /></td></tr>
    1078       <tr><td class="lineno" valign="top"></td><td class="lblock">   optional header fields<span class="delete">, and thus</span> are terminated by the empty line at</td><td> </td><td class="rblock">   optional header fields<span class="insert"> and, thus,</span> are terminated by the empty line at</td><td class="lineno" valign="top"></td></tr>
    1079       <tr><td class="lineno" valign="top"></td><td class="left">   the end of the header section.  Since HTTP/1.0 did not define any 1xx</td><td> </td><td class="right">   the end of the header section.  Since HTTP/1.0 did not define any 1xx</td><td class="lineno" valign="top"></td></tr>
    1080       <tr><td class="lineno" valign="top"></td><td class="left">   status codes, a server MUST NOT send a 1xx response to an HTTP/1.0</td><td> </td><td class="right">   status codes, a server MUST NOT send a 1xx response to an HTTP/1.0</td><td class="lineno" valign="top"></td></tr>
    1081       <tr><td class="lineno" valign="top"></td><td class="left">   client.</td><td> </td><td class="right">   client.</td><td class="lineno" valign="top"></td></tr>
    1082       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1083       <tr><td class="lineno" valign="top"></td><td class="left">   A client MUST be able to parse one or more 1xx responses received</td><td> </td><td class="right">   A client MUST be able to parse one or more 1xx responses received</td><td class="lineno" valign="top"></td></tr>
    1084       <tr><td class="lineno" valign="top"></td><td class="left">   prior to a final response, even if the client does not expect one.  A</td><td> </td><td class="right">   prior to a final response, even if the client does not expect one.  A</td><td class="lineno" valign="top"></td></tr>
    1085       <tr><td class="lineno" valign="top"></td><td class="left">   user agent MAY ignore unexpected 1xx responses.</td><td> </td><td class="right">   user agent MAY ignore unexpected 1xx responses.</td><td class="lineno" valign="top"></td></tr>
    1086       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1087       <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MUST forward 1xx responses unless the proxy itself requested</td><td> </td><td class="right">   A proxy MUST forward 1xx responses unless the proxy itself requested</td><td class="lineno" valign="top"></td></tr>
    1088       <tr><td class="lineno" valign="top"></td><td class="left">   the generation of the 1xx response.  For example, if a proxy adds an</td><td> </td><td class="right">   the generation of the 1xx response.  For example, if a proxy adds an</td><td class="lineno" valign="top"></td></tr>
    1089       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1090       <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 52, line 27</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 52, line 27</em></th><td></td></tr>
     900      <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 52, line 27</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 52, line 27</em></th><td></td></tr>
    1091901      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1092902      <tr><td class="lineno" valign="top"></td><td class="left">6.3.3.  202 Accepted</td><td> </td><td class="right">6.3.3.  202 Accepted</td><td class="lineno" valign="top"></td></tr>
     
    1099909      <tr><td class="lineno" valign="top"></td><td class="left">   operation.</td><td> </td><td class="right">   operation.</td><td class="lineno" valign="top"></td></tr>
    1100910      <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><a name="diff0058" /></td></tr>
     911      <tr><td><a name="diff0049" /></td></tr>
    1102912      <tr><td class="lineno" valign="top"></td><td class="lblock">   The 202 response is intentionally non<span class="delete">-</span>committal.  Its purpose is to</td><td> </td><td class="rblock">   The 202 response is intentionally noncommittal.  Its purpose is to</td><td class="lineno" valign="top"></td></tr>
    1103913      <tr><td class="lineno" valign="top"></td><td class="left">   allow a server to accept a request for some other process (perhaps a</td><td> </td><td class="right">   allow a server to accept a request for some other process (perhaps a</td><td class="lineno" valign="top"></td></tr>
     
    1112922      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1113923      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1114       <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
     924      <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
    1115925      <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>
    1116926      <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>
     
    1123933      <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>
    1124934      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1125       <tr><td><a name="diff0059" /></td></tr>
     935      <tr><td><a name="diff0050" /></td></tr>
    1126936      <tr><td class="lineno" valign="top"></td><td class="lblock">      Note: The original proposal for 300 defined the URI header field</td><td> </td><td class="rblock">      Note: The original proposal for <span class="insert">the</span> 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr>
    1127937      <tr><td class="lineno" valign="top"></td><td class="lblock">      as providing a list of alternative representations, such that it</td><td> </td><td class="rblock">      header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr>
     
    1139949      <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>
    1140950      <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>
    1141       <tr><td><a name="diff0060" /></td></tr>
     951      <tr><td><a name="diff0051" /></td></tr>
    1142952      <tr><td class="lineno" valign="top"></td><td class="lblock">   Clients with link<span class="delete"> </span>editing capabilities ought to automatically re-link</td><td> </td><td class="rblock">   Clients with link<span class="insert">-</span>editing capabilities ought to automatically re-link</td><td class="lineno" valign="top"></td></tr>
    1143953      <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>
     
    1152962      <tr><td class="lineno" valign="top"></td><td class="left">      Note: For historical reasons, a user agent MAY change the request</td><td> </td><td class="right">      Note: For historical reasons, a user agent MAY change the request</td><td class="lineno" valign="top"></td></tr>
    1153963      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1154       <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 57, line 26</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 57, line 26</em></th><td></td></tr>
    1155       <tr><td class="lineno" valign="top"></td><td class="left">   a retrieval request targeting that URI (a GET or HEAD request if</td><td> </td><td class="right">   a retrieval request targeting that URI (a GET or HEAD request if</td><td class="lineno" valign="top"></td></tr>
    1156       <tr><td class="lineno" valign="top"></td><td class="left">   using HTTP), which might also be redirected, and present the eventual</td><td> </td><td class="right">   using HTTP), which might also be redirected, and present the eventual</td><td class="lineno" valign="top"></td></tr>
    1157       <tr><td class="lineno" valign="top"></td><td class="left">   result as an answer to the original request.  Note that the new URI</td><td> </td><td class="right">   result as an answer to the original request.  Note that the new URI</td><td class="lineno" valign="top"></td></tr>
    1158       <tr><td class="lineno" valign="top"></td><td class="left">   in the Location header field is not considered equivalent to the</td><td> </td><td class="right">   in the Location header field is not considered equivalent to the</td><td class="lineno" valign="top"></td></tr>
    1159       <tr><td class="lineno" valign="top"></td><td class="left">   effective request URI.</td><td> </td><td class="right">   effective request URI.</td><td class="lineno" valign="top"></td></tr>
    1160       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1161       <tr><td class="lineno" valign="top"></td><td class="left">   This status code is applicable to any HTTP method.  It is primarily</td><td> </td><td class="right">   This status code is applicable to any HTTP method.  It is primarily</td><td class="lineno" valign="top"></td></tr>
    1162       <tr><td class="lineno" valign="top"></td><td class="left">   used to allow the output of a POST action to redirect the user agent</td><td> </td><td class="right">   used to allow the output of a POST action to redirect the user agent</td><td class="lineno" valign="top"></td></tr>
    1163       <tr><td class="lineno" valign="top"></td><td class="left">   to a selected resource, since doing so provides the information</td><td> </td><td class="right">   to a selected resource, since doing so provides the information</td><td class="lineno" valign="top"></td></tr>
    1164       <tr><td class="lineno" valign="top"></td><td class="left">   corresponding to the POST response in a form that can be separately</td><td> </td><td class="right">   corresponding to the POST response in a form that can be separately</td><td class="lineno" valign="top"></td></tr>
    1165       <tr><td><a name="diff0061" /></td></tr>
    1166       <tr><td class="lineno" valign="top"></td><td class="lblock">   identified, bookmarked, and cached independent of the original</td><td> </td><td class="rblock">   identified, bookmarked, and cached<span class="insert">,</span> independent of the original</td><td class="lineno" valign="top"></td></tr>
    1167       <tr><td class="lineno" valign="top"></td><td class="left">   request.</td><td> </td><td class="right">   request.</td><td class="lineno" valign="top"></td></tr>
    1168       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1169       <tr><td class="lineno" valign="top"></td><td class="left">   A 303 response to a GET request indicates that the origin server does</td><td> </td><td class="right">   A 303 response to a GET request indicates that the origin server does</td><td class="lineno" valign="top"></td></tr>
    1170       <tr><td class="lineno" valign="top"></td><td class="left">   not have a representation of the target resource that can be</td><td> </td><td class="right">   not have a representation of the target resource that can be</td><td class="lineno" valign="top"></td></tr>
    1171       <tr><td class="lineno" valign="top"></td><td class="left">   transferred by the server over HTTP.  However, the Location field</td><td> </td><td class="right">   transferred by the server over HTTP.  However, the Location field</td><td class="lineno" valign="top"></td></tr>
    1172       <tr><td class="lineno" valign="top"></td><td class="left">   value refers to a resource that is descriptive of the target</td><td> </td><td class="right">   value refers to a resource that is descriptive of the target</td><td class="lineno" valign="top"></td></tr>
    1173       <tr><td class="lineno" valign="top"></td><td class="left">   resource, such that making a retrieval request on that other resource</td><td> </td><td class="right">   resource, such that making a retrieval request on that other resource</td><td class="lineno" valign="top"></td></tr>
    1174       <tr><td class="lineno" valign="top"></td><td class="left">   might result in a representation that is useful to recipients without</td><td> </td><td class="right">   might result in a representation that is useful to recipients without</td><td class="lineno" valign="top"></td></tr>
    1175       <tr><td class="lineno" valign="top"></td><td class="left">   implying that it represents the original target resource.  Note that</td><td> </td><td class="right">   implying that it represents the original target resource.  Note that</td><td class="lineno" valign="top"></td></tr>
    1176       <tr><td class="lineno" valign="top"></td><td class="left">   answers to the questions of what can be represented, what</td><td> </td><td class="right">   answers to the questions of what can be represented, what</td><td class="lineno" valign="top"></td></tr>
    1177       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1178       <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
     964      <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
    1179965      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1180966      <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>
     
    1187973      <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>
    1188974      <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>
    1189       <tr><td><a name="diff0062" /></td></tr>
     975      <tr><td><a name="diff0052" /></td></tr>
    1190976      <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>
    1191977      <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>
     
    1203989      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1204990      <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code indicates that the server cannot or</td><td> </td><td class="right">   The 400 (Bad Request) status code indicates that the server cannot or</td><td class="lineno" valign="top"></td></tr>
    1205       <tr><td><a name="diff0063" /></td></tr>
     991      <tr><td><a name="diff0053" /></td></tr>
    1206992      <tr><td class="lineno" valign="top"></td><td class="lblock">   will not process the request due to something <span class="delete">which</span> is perceived to</td><td> </td><td class="rblock">   will not process the request due to something <span class="insert">that</span> is perceived to be</td><td class="lineno" valign="top"></td></tr>
    1207993      <tr><td class="lineno" valign="top"></td><td class="lblock">   be a client error (e.g., malformed request syntax, invalid request</td><td> </td><td class="rblock">   a client error (e.g., malformed request syntax, invalid request</td><td class="lineno" valign="top"></td></tr>
     
    12171003      <tr><td class="lineno" valign="top"></td><td class="left">   the request but refuses to authorize it.  A server that wishes to</td><td> </td><td class="right">   the request but refuses to authorize it.  A server that wishes to</td><td class="lineno" valign="top"></td></tr>
    12181004      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1219       <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 61, line 39</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 61, line 39</em></th><td></td></tr>
    1220       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1221       <tr><td class="lineno" valign="top"></td><td class="left">6.5.12.  414 URI Too Long</td><td> </td><td class="right">6.5.12.  414 URI Too Long</td><td class="lineno" valign="top"></td></tr>
    1222       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1223       <tr><td class="lineno" valign="top"></td><td class="left">   The 414 (URI Too Long) status code indicates that the server is</td><td> </td><td class="right">   The 414 (URI Too Long) status code indicates that the server is</td><td class="lineno" valign="top"></td></tr>
    1224       <tr><td class="lineno" valign="top"></td><td class="left">   refusing to service the request because the request-target (Section</td><td> </td><td class="right">   refusing to service the request because the request-target (Section</td><td class="lineno" valign="top"></td></tr>
    1225       <tr><td class="lineno" valign="top"></td><td class="left">   5.3 of [RFC7230]) is longer than the server is willing to interpret.</td><td> </td><td class="right">   5.3 of [RFC7230]) is longer than the server is willing to interpret.</td><td class="lineno" valign="top"></td></tr>
    1226       <tr><td class="lineno" valign="top"></td><td class="left">   This rare condition is only likely to occur when a client has</td><td> </td><td class="right">   This rare condition is only likely to occur when a client has</td><td class="lineno" valign="top"></td></tr>
    1227       <tr><td class="lineno" valign="top"></td><td class="left">   improperly converted a POST request to a GET request with long query</td><td> </td><td class="right">   improperly converted a POST request to a GET request with long query</td><td class="lineno" valign="top"></td></tr>
    1228       <tr><td class="lineno" valign="top"></td><td class="left">   information, when the client has descended into a "black hole" of</td><td> </td><td class="right">   information, when the client has descended into a "black hole" of</td><td class="lineno" valign="top"></td></tr>
    1229       <tr><td class="lineno" valign="top"></td><td class="left">   redirection (e.g., a redirected URI prefix that points to a suffix of</td><td> </td><td class="right">   redirection (e.g., a redirected URI prefix that points to a suffix of</td><td class="lineno" valign="top"></td></tr>
    1230       <tr><td><a name="diff0064" /></td></tr>
    1231       <tr><td class="lineno" valign="top"></td><td class="lblock">   itself)<span class="delete">,</span> or when the server is under attack by a client attempting to</td><td> </td><td class="rblock">   itself) or when the server is under attack by a client attempting to</td><td class="lineno" valign="top"></td></tr>
    1232       <tr><td class="lineno" valign="top"></td><td class="left">   exploit potential security holes.</td><td> </td><td class="right">   exploit potential security holes.</td><td class="lineno" valign="top"></td></tr>
    1233       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1234       <tr><td class="lineno" valign="top"></td><td class="left">   A 414 response is cacheable by default; i.e., unless otherwise</td><td> </td><td class="right">   A 414 response is cacheable by default; i.e., unless otherwise</td><td class="lineno" valign="top"></td></tr>
    1235       <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>
    1236       <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>
    1237       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1238       <tr><td class="lineno" valign="top"></td><td class="left">6.5.13.  415 Unsupported Media Type</td><td> </td><td class="right">6.5.13.  415 Unsupported Media Type</td><td class="lineno" valign="top"></td></tr>
    1239       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1240       <tr><td class="lineno" valign="top"></td><td class="left">   The 415 (Unsupported Media Type) status code indicates that the</td><td> </td><td class="right">   The 415 (Unsupported Media Type) status code indicates that the</td><td class="lineno" valign="top"></td></tr>
    1241       <tr><td class="lineno" valign="top"></td><td class="left">   origin server is refusing to service the request because the payload</td><td> </td><td class="right">   origin server is refusing to service the request because the payload</td><td class="lineno" valign="top"></td></tr>
    1242       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1243       <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr>
     1005      <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 66, line 9</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 66, line 9</em></th><td></td></tr>
    12441006      <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>
    12451007      <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>
     
    12521014      <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>
    12531015      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1254       <tr><td><a name="diff0065" /></td></tr>
     1016      <tr><td><a name="diff0054" /></td></tr>
    12551017      <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>
    12561018      <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>
     
    12651027      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12661028      <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>
    1267       <tr><td><a name="diff0066" /></td></tr>
     1029      <tr><td><a name="diff0055" /></td></tr>
    12681030      <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>
    12691031      <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>
     
    12801042      <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>
    12811043      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1282       <tr><td><a name="diff0067" /></td></tr>
     1044      <tr><td><a name="diff0056" /></td></tr>
    12831045      <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>
    12841046      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12971059      <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>
    12981060      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1299       <tr><td><a name="diff0068" /></td></tr>
     1061      <tr><td><a name="diff0057" /></td></tr>
    13001062      <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>
    13011063      <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>
     
    13161078      <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>
    13171079      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1318       <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 69, line 5</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 69, line 5</em></th><td></td></tr>
     1080      <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 69, line 5</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 69, line 5</em></th><td></td></tr>
    13191081      <tr><td class="lineno" valign="top"></td><td class="left">   The field value consists of a single URI-reference.  When it has the</td><td> </td><td class="right">   The field value consists of a single URI-reference.  When it has the</td><td class="lineno" valign="top"></td></tr>
    13201082      <tr><td class="lineno" valign="top"></td><td class="left">   form of a relative reference ([RFC3986], Section 4.2), the final</td><td> </td><td class="right">   form of a relative reference ([RFC3986], Section 4.2), the final</td><td class="lineno" valign="top"></td></tr>
     
    13271089      <tr><td class="lineno" valign="top"></td><td class="left">   automatically redirecting the request.</td><td> </td><td class="right">   automatically redirecting the request.</td><td class="lineno" valign="top"></td></tr>
    13281090      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1329       <tr><td><a name="diff0069" /></td></tr>
     1091      <tr><td><a name="diff0058" /></td></tr>
    13301092      <tr><td class="lineno" valign="top"></td><td class="lblock">   If the Location value provided in a 3xx (Redirection) does not have a</td><td> </td><td class="rblock">   If the Location value provided in a 3xx (Redirection) <span class="insert">response</span> does</td><td class="lineno" valign="top"></td></tr>
    13311093      <tr><td class="lineno" valign="top"></td><td class="lblock">   fragment component, a user agent MUST process the redirection as if</td><td> </td><td class="rblock">   not have a fragment component, a user agent MUST process the</td><td class="lineno" valign="top"></td></tr>
     
    13441106      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    13451107      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1346       <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr>
     1108      <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 70, line 30</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 70, line 30</em></th><td></td></tr>
    13471109      <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>
    13481110      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    13551117      <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>
    13561118      <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>
    1357       <tr><td><a name="diff0070" /></td></tr>
     1119      <tr><td><a name="diff0059" /></td></tr>
    13581120      <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>
    13591121      <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>
     
    13681130      <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>
    13691131      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1370       <tr bgcolor="gray" ><td></td><th><a name="part-l39" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r39" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>
     1132      <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 71, line 22</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 71, line 22</em></th><td></td></tr>
    13711133      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    13721134      <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>
     
    13791141      <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>
    13801142      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1381       <tr><td><a name="diff0071" /></td></tr>
     1143      <tr><td><a name="diff0060" /></td></tr>
    13821144      <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>
    13831145      <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>
     
    13921154      <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>
    13931155      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1394       <tr bgcolor="gray" ><td></td><th><a name="part-l40" /><small>skipping to change at</small><em> page 72, line 5</em></th><th> </th><th><a name="part-r40" /><small>skipping to change at</small><em> page 72, line 5</em></th><td></td></tr>
     1156      <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 72, line 5</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 72, line 5</em></th><td></td></tr>
    13951157      <tr><td class="lineno" valign="top"></td><td class="left">   fields describe the selected representation chosen by the origin</td><td> </td><td class="right">   fields describe the selected representation chosen by the origin</td><td class="lineno" valign="top"></td></tr>
    13961158      <tr><td class="lineno" valign="top"></td><td class="left">   server while handling the response.  Note that, depending on the</td><td> </td><td class="right">   server while handling the response.  Note that, depending on the</td><td class="lineno" valign="top"></td></tr>
     
    14031165      <tr><td class="lineno" valign="top"></td><td class="left">   selected representation as a result of processing the request.</td><td> </td><td class="right">   selected representation as a result of processing the request.</td><td class="lineno" valign="top"></td></tr>
    14041166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1405       <tr><td><a name="diff0072" /></td></tr>
     1167      <tr><td><a name="diff0061" /></td></tr>
    14061168      <tr><td class="lineno" valign="top"></td><td class="lblock">   For example, an ETag header field in a 201 response communicates the</td><td> </td><td class="rblock">   For example, an ETag header field in a 201 <span class="insert">(Created)</span> response</td><td class="lineno" valign="top"></td></tr>
    14071169      <tr><td class="lineno" valign="top"></td><td class="lblock">   entity-tag of the newly created resource's representation, so that it</td><td> </td><td class="rblock">   communicates the entity-tag of the newly created resource's</td><td class="lineno" valign="top"></td></tr>
     
    14191181      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    14201182      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1421       <tr bgcolor="gray" ><td></td><th><a name="part-l41" /><small>skipping to change at</small><em> page 74, line 6</em></th><th> </th><th><a name="part-r41" /><small>skipping to change at</small><em> page 74, line 6</em></th><td></td></tr>
     1183      <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 74, line 6</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 74, line 6</em></th><td></td></tr>
    14221184      <tr><td class="lineno" valign="top"></td><td class="left">   An origin server SHOULD NOT generate a Server field containing</td><td> </td><td class="right">   An origin server SHOULD NOT generate a Server field containing</td><td class="lineno" valign="top"></td></tr>
    14231185      <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>
     
    14301192      <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>
    14311193      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1432       <tr><td><a name="diff0073" /></td></tr>
     1194      <tr><td><a name="diff0062" /></td></tr>
    14331195      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the request</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr>
    14341196      <tr><td class="lineno" valign="top"></td><td class="lblock">   method token (Section 4).  The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock">   <span class="insert">namespace</span> for the request method token (Section 4).  The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr>
     
    14481210      <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>
    14491211      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1450       <tr><td><a name="diff0074" /></td></tr>
     1212      <tr><td><a name="diff0063" /></td></tr>
    14511213      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this name<span class="delete"> </span>space require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this namespace require IETF Review (see</td><td class="lineno" valign="top"></td></tr>
    14521214      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5226], Section 4.1).</td><td> </td><td class="right">   [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr>
     
    14701232      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    14711233      <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>
    1472       <tr><td><a name="diff0075" /></td></tr>
     1234      <tr><td><a name="diff0064" /></td></tr>
    14731235      <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>
    14741236      <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>
     
    14811243      <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>
    14821244      <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>
    1483       <tr><td class="lineno" valign="top"></td><td class="lblock">   document <span class="delete">this</span> too.</td><td> </td><td class="rblock">   ([RFC7233]), it ought to document <span class="insert">this,</span> too.</td><td class="lineno" valign="top"></td></tr>
     1245      <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>
    14841246      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    14851247      <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>
     
    14891251      <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>
    14901252      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1491       <tr><td><a name="diff0076" /></td></tr>
     1253      <tr><td><a name="diff0065" /></td></tr>
    14921254      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Method <span class="delete">Registry shall be</span> populated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry" has been</span></td><td class="lineno" valign="top"></td></tr>
    14931255      <tr><td class="lineno" valign="top"></td><td class="lblock">   below:</td><td> </td><td class="rblock">   populated with the registrations below:</td><td class="lineno" valign="top"></td></tr>
     
    15081270      <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>
    15091271      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1510       <tr><td><a name="diff0077" /></td></tr>
     1272      <tr><td><a name="diff0066" /></td></tr>
    15111273      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the response</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr>
    15121274      <tr><td class="lineno" valign="top"></td><td class="lblock">   status-code token (Section 6).  The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock">   the <span class="insert">namespace</span> for the response status-code token (Section 6).  The</td><td class="lineno" valign="top"></td></tr>
     
    15141276      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td class="lineno" valign="top"></td></tr>
    15151277      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1516       <tr><td><a name="diff0078" /></td></tr>
     1278      <tr><td><a name="diff0067" /></td></tr>
    15171279      <tr><td class="lineno" valign="top"></td><td class="lblock">   This <span class="delete">S</span>ection replaces the registration procedure for HTTP Status</td><td> </td><td class="rblock">   This <span class="insert">s</span>ection replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr>
    15181280      <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>
     
    15281290      <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>
    15291291      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1530       <tr><td><a name="diff0079" /></td></tr>
     1292      <tr><td><a name="diff0068" /></td></tr>
    15311293      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to the HTTP status code name<span class="delete"> </span>space require IETF</td><td> </td><td class="rblock">   Values to be added to the HTTP status code namespace require IETF</td><td class="lineno" valign="top"></td></tr>
    15321294      <tr><td class="lineno" valign="top"></td><td class="left">   Review (see [RFC5226], Section 4.1).</td><td> </td><td class="right">   Review (see [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr>
     
    15411303      <tr><td class="lineno" valign="top"></td><td class="left">   be registered in a document that isn't specific to a single</td><td> </td><td class="right">   be registered in a document that isn't specific to a single</td><td class="lineno" valign="top"></td></tr>
    15421304      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1543       <tr bgcolor="gray" ><td></td><th><a name="part-l42" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r42" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>
     1305      <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 76, line 49</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 76, line 49</em></th><td></td></tr>
    15441306      <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>
    15451307      <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>
     
    15521314      <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>
    15531315      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1554       <tr><td><a name="diff0080" /></td></tr>
     1316      <tr><td><a name="diff0069" /></td></tr>
    15551317      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Status <span class="delete">Code Registry shall be</span> updated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Status <span class="insert">Codes" registry has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    15561318      <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>
     
    15661328      <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>
    15671329      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1568       <tr bgcolor="gray" ><td></td><th><a name="part-l43" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r43" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr>
     1330      <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 77, line 48</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 77, line 48</em></th><td></td></tr>
    15691331      <tr><td class="lineno" valign="top"></td><td class="left">   | 500   | Internal Server Error         | Section 6.6.1  |</td><td> </td><td class="right">   | 500   | Internal Server Error         | Section 6.6.1  |</td><td class="lineno" valign="top"></td></tr>
    15701332      <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>
     
    15771339      <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>
    15781340      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1579       <tr><td><a name="diff0081" /></td></tr>
     1341      <tr><td><a name="diff0070" /></td></tr>
    15801342      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock">   HTTP header fields are registered within the <span class="insert">"Message Headers"</span></td><td class="lineno" valign="top"></td></tr>
    15811343      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry</span> located at <span class="delete">&lt;http://www.iana.org/assignments/message-headers/</span></td><td> </td><td class="rblock"><span class="insert">   registry</span> located at <span class="insert">&lt;http://www.iana.org/assignments/message-headers&gt;</span></td><td class="lineno" valign="top"></td></tr>
     
    15921354      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    15931355      <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>
    1594       <tr><td><a name="diff0082" /></td></tr>
     1356      <tr><td><a name="diff0071" /></td></tr>
    15951357      <tr><td class="lineno" valign="top"></td><td class="lblock">   name as short as practical and <span class="delete">to not</span> prefix the name with "X-"</td><td> </td><td class="rblock">   name as short as practical and <span class="insert">not to</span> prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr>
    15961358      <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>
    1597       <tr><td><a name="diff0083" /></td></tr>
     1359      <tr><td><a name="diff0072" /></td></tr>
    15981360      <tr><td class="lineno" valign="top"></td><td class="lblock">   "<span class="delete">x</span>-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="rblock">   "<span class="insert">X</span>-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr>
    15991361      <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>
    16001362      <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>
    16011363      <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>
    1602       <tr><td><a name="diff0084" /></td></tr>
     1364      <tr><td><a name="diff0073" /></td></tr>
    16031365      <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet name; see [BCP178] for further information)</td><td> </td><td class="rblock">   Internet name; see [BCP178] for further information)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>
    16041366      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    16051367      <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>
    1606       <tr><td><a name="diff0085" /></td></tr>
     1368      <tr><td><a name="diff0074" /></td></tr>
    16071369      <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>
    16081370      <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>
     
    16191381      <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>
    16201382      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1621       <tr bgcolor="gray" ><td></td><th><a name="part-l44" /><small>skipping to change at</small><em> page 79, line 15</em></th><th> </th><th><a name="part-r44" /><small>skipping to change at</small><em> page 79, line 15</em></th><td></td></tr>
    1622       <tr><td class="lineno" valign="top"></td><td class="left">   Allowing both unquoted (token) and quoted (quoted-string) syntax for</td><td> </td><td class="right">   Allowing both unquoted (token) and quoted (quoted-string) syntax for</td><td class="lineno" valign="top"></td></tr>
    1623       <tr><td class="lineno" valign="top"></td><td class="left">   the parameter value enables recipients to use existing parser</td><td> </td><td class="right">   the parameter value enables recipients to use existing parser</td><td class="lineno" valign="top"></td></tr>
    1624       <tr><td class="lineno" valign="top"></td><td class="left">   components.  When allowing both forms, the meaning of a parameter</td><td> </td><td class="right">   components.  When allowing both forms, the meaning of a parameter</td><td class="lineno" valign="top"></td></tr>
    1625       <tr><td class="lineno" valign="top"></td><td class="left">   value ought to be independent of the syntax used for it (for an</td><td> </td><td class="right">   value ought to be independent of the syntax used for it (for an</td><td class="lineno" valign="top"></td></tr>
    1626       <tr><td class="lineno" valign="top"></td><td class="left">   example, see the notes on parameter handling for media types in</td><td> </td><td class="right">   example, see the notes on parameter handling for media types in</td><td class="lineno" valign="top"></td></tr>
    1627       <tr><td class="lineno" valign="top"></td><td class="left">   Section 3.1.1.1).</td><td> </td><td class="right">   Section 3.1.1.1).</td><td class="lineno" valign="top"></td></tr>
    1628       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1629       <tr><td class="lineno" valign="top"></td><td class="left">   Authors of specifications defining new header fields are advised to</td><td> </td><td class="right">   Authors of specifications defining new header fields are advised to</td><td class="lineno" valign="top"></td></tr>
    1630       <tr><td class="lineno" valign="top"></td><td class="left">   consider documenting:</td><td> </td><td class="right">   consider documenting:</td><td class="lineno" valign="top"></td></tr>
    1631       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1632       <tr><td><a name="diff0086" /></td></tr>
    1633       <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Whether the field is a single value<span class="delete">,</span> or whether it can be a list</td><td> </td><td class="rblock">   o  Whether the field is a single value or whether it can be a list</td><td class="lineno" valign="top"></td></tr>
    1634       <tr><td class="lineno" valign="top"></td><td class="left">      (delimited by commas; see Section 3.2 of [RFC7230]).</td><td> </td><td class="right">      (delimited by commas; see Section 3.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
    1635       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1636       <tr><td class="lineno" valign="top"></td><td class="left">      If it does not use the list syntax, document how to treat messages</td><td> </td><td class="right">      If it does not use the list syntax, document how to treat messages</td><td class="lineno" valign="top"></td></tr>
    1637       <tr><td class="lineno" valign="top"></td><td class="left">      where the field occurs multiple times (a sensible default would be</td><td> </td><td class="right">      where the field occurs multiple times (a sensible default would be</td><td class="lineno" valign="top"></td></tr>
    1638       <tr><td class="lineno" valign="top"></td><td class="left">      to ignore the field, but this might not always be the right</td><td> </td><td class="right">      to ignore the field, but this might not always be the right</td><td class="lineno" valign="top"></td></tr>
    1639       <tr><td class="lineno" valign="top"></td><td class="left">      choice).</td><td> </td><td class="right">      choice).</td><td class="lineno" valign="top"></td></tr>
    1640       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1641       <tr><td class="lineno" valign="top"></td><td class="left">      Note that intermediaries and software libraries might combine</td><td> </td><td class="right">      Note that intermediaries and software libraries might combine</td><td class="lineno" valign="top"></td></tr>
    1642       <tr><td class="lineno" valign="top"></td><td class="left">      multiple header field instances into a single one, despite the</td><td> </td><td class="right">      multiple header field instances into a single one, despite the</td><td class="lineno" valign="top"></td></tr>
    1643       <tr><td class="lineno" valign="top"></td><td class="left">      field's definition not allowing the list syntax.  A robust format</td><td> </td><td class="right">      field's definition not allowing the list syntax.  A robust format</td><td class="lineno" valign="top"></td></tr>
    1644       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1645       <tr bgcolor="gray" ><td></td><th><a name="part-l45" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r45" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr>
     1383      <tr bgcolor="gray" ><td></td><th><a name="part-l36" /><small>skipping to change at</small><em> page 80, line 15</em></th><th> </th><th><a name="part-r36" /><small>skipping to change at</small><em> page 80, line 15</em></th><td></td></tr>
    16461384      <tr><td class="lineno" valign="top"></td><td class="left">   o  Whether the header field is useful or allowable in trailers (see</td><td> </td><td class="right">   o  Whether the header field is useful or allowable in trailers (see</td><td class="lineno" valign="top"></td></tr>
    16471385      <tr><td class="lineno" valign="top"></td><td class="left">      Section 4.1 of [RFC7230]).</td><td> </td><td class="right">      Section 4.1 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
     
    16541392      <tr><td class="lineno" valign="top"></td><td class="left">8.3.2.  Registrations</td><td> </td><td class="right">8.3.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    16551393      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1656       <tr><td><a name="diff0087" /></td></tr>
     1394      <tr><td><a name="diff0075" /></td></tr>
    16571395      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">Message Header Field Registry shall be</span> updated with the following</td><td> </td><td class="rblock">   The <span class="insert">"Message Headers" registry has been</span> updated with the following</td><td class="lineno" valign="top"></td></tr>
    16581396      <tr><td class="lineno" valign="top"></td><td class="left">   permanent registrations:</td><td> </td><td class="right">   permanent registrations:</td><td class="lineno" valign="top"></td></tr>
     
    16741412      <tr><td class="lineno" valign="top"></td><td class="left">   | From              | http     | standard | Section 5.5.1   |</td><td> </td><td class="right">   | From              | http     | standard | Section 5.5.1   |</td><td class="lineno" valign="top"></td></tr>
    16751413      <tr><td class="lineno" valign="top"></td><td class="left">   | Location          | http     | standard | Section 7.1.2   |</td><td> </td><td class="right">   | Location          | http     | standard | Section 7.1.2   |</td><td class="lineno" valign="top"></td></tr>
    1676       <tr><td><a name="diff0088" /></td></tr>
     1414      <tr><td><a name="diff0076" /></td></tr>
    16771415      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   | MIME-Version      | http     | standard | Appendix A.1    |</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16781416      <tr><td class="lineno" valign="top"></td><td class="left">   | Max-Forwards      | http     | standard | Section 5.1.2   |</td><td> </td><td class="right">   | Max-Forwards      | http     | standard | Section 5.1.2   |</td><td class="lineno" valign="top"></td></tr>
    1679       <tr><td><a name="diff0089" /></td></tr>
     1417      <tr><td><a name="diff0077" /></td></tr>
    16801418      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   | MIME-Version      | http     | standard | Appendix A.1    |</span></td><td class="lineno" valign="top"></td></tr>
    16811419      <tr><td class="lineno" valign="top"></td><td class="left">   | Referer           | http     | standard | Section 5.5.2   |</td><td> </td><td class="right">   | Referer           | http     | standard | Section 5.5.2   |</td><td class="lineno" valign="top"></td></tr>
     
    16911429      <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>
    16921430      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1693       <tr><td><a name="diff0090" /></td></tr>
     1431      <tr><td><a name="diff0078" /></td></tr>
    16941432      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the <span class="delete">name space</span> for content</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the <span class="insert">namespace</span> for content</td><td class="lineno" valign="top"></td></tr>
    16951433      <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>
     
    16991437      <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>
    17001438      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1701       <tr><td><a name="diff0091" /></td></tr>
     1439      <tr><td><a name="diff0079" /></td></tr>
    17021440      <tr><td class="lineno" valign="top"></td><td class="lblock">   Content <span class="delete">C</span>oding registrations MUST include the following fields:</td><td> </td><td class="rblock">   Content <span class="insert">c</span>oding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    17031441      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    17131451      <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>
    17141452      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1715       <tr><td><a name="diff0092" /></td></tr>
     1453      <tr><td><a name="diff0080" /></td></tr>
    17161454      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
    17171455      <tr><td class="lineno" valign="top"></td><td class="lblock">   Section 4.1 of <span class="delete">[RFC5226]),</span> and MUST conform to the purpose of content</td><td> </td><td class="rblock">   4.1 of <span class="insert">[RFC5226])</span> and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>
     
    17201458      <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>
    17211459      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1722       <tr><td><a name="diff0093" /></td></tr>
     1460      <tr><td><a name="diff0081" /></td></tr>
    17231461      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP Content Codings Registry shall be</span> updated with the</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Content Codings Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    17241462      <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>
     
    17411479      <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>
    17421480      <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>
    1743       <tr><td><a name="diff0094" /></td></tr>
     1481      <tr><td><a name="diff0082" /></td></tr>
    17441482      <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>
    17451483      <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>
     
    17551493      <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>
    17561494      <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>
    1757       <tr><td><a name="diff0095" /></td></tr>
    1758       <tr><td class="lineno" valign="top"></td><td class="lblock">   names<span class="delete">, and thus</span> depend on the origin server to avoid mapping to file</td><td> </td><td class="rblock">   names<span class="insert"> and, thus,</span> depend on the origin server to avoid mapping to file</td><td class="lineno" valign="top"></td></tr>
     1495      <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>
    17591496      <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>
    17601497      <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>
     
    17621499      <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>
    17631500      <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>
    1764       <tr><td><a name="diff0096" /></td></tr>
     1501      <tr><td><a name="diff0083" /></td></tr>
    17651502      <tr><td class="lineno" valign="top"></td><td class="lblock">   current one, and use specially named paths or file names to send data</td><td> </td><td class="rblock">   current one, and <span class="insert">they</span> use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr>
    17661503      <tr><td class="lineno" valign="top"></td><td class="lblock">   to system devices.  Similar naming conventions might exist within</td><td> </td><td class="rblock">   data to system devices.  Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr>
     
    17811518      <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>
    17821519      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1783       <tr bgcolor="gray" ><td></td><th><a name="part-l46" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r46" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr>
     1520      <tr bgcolor="gray" ><td></td><th><a name="part-l37" /><small>skipping to change at</small><em> page 83, line 41</em></th><th> </th><th><a name="part-r37" /><small>skipping to change at</small><em> page 83, line 41</em></th><td></td></tr>
    17841521      <tr><td class="lineno" valign="top"></td><td class="left">   of sensitive data because that data will be placed in the request-</td><td> </td><td class="right">   of sensitive data because that data will be placed in the request-</td><td class="lineno" valign="top"></td></tr>
    17851522      <tr><td class="lineno" valign="top"></td><td class="left">   target.  Many existing servers, proxies, and user agents log or</td><td> </td><td class="right">   target.  Many existing servers, proxies, and user agents log or</td><td class="lineno" valign="top"></td></tr>
     
    17921529      <tr><td class="lineno" valign="top"></td><td class="left">   information about the user's immediate browsing history and any</td><td> </td><td class="right">   information about the user's immediate browsing history and any</td><td class="lineno" valign="top"></td></tr>
    17931530      <tr><td class="lineno" valign="top"></td><td class="left">   personal information that might be found in the referring resource's</td><td> </td><td class="right">   personal information that might be found in the referring resource's</td><td class="lineno" valign="top"></td></tr>
    1794       <tr><td><a name="diff0097" /></td></tr>
     1531      <tr><td><a name="diff0084" /></td></tr>
    17951532      <tr><td class="lineno" valign="top"></td><td class="lblock">   URI.  Limitations on Referer are described in Section 5.5.2 to</td><td> </td><td class="rblock">   URI.  Limitations on <span class="insert">the</span> Referer <span class="insert">header field</span> are described in</td><td class="lineno" valign="top"></td></tr>
    17961533      <tr><td class="lineno" valign="top"></td><td class="lblock">   address some of its security considerations.</td><td> </td><td class="rblock">   Section 5.5.2 to address some of its security considerations.</td><td class="lineno" valign="top"></td></tr>
     
    18061543      <tr><td class="lineno" valign="top"></td><td class="left">   disclosing one site's fragment to another site.  If the first site</td><td> </td><td class="right">   disclosing one site's fragment to another site.  If the first site</td><td class="lineno" valign="top"></td></tr>
    18071544      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1808       <tr bgcolor="gray" ><td></td><th><a name="part-l47" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r47" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>
     1545      <tr bgcolor="gray" ><td></td><th><a name="part-l38" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r38" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>
    18091546      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    18101547      <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>
     
    18171554      <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>
    18181555      <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>
    1819       <tr><td><a name="diff0098" /></td></tr>
     1556      <tr><td><a name="diff0085" /></td></tr>
    18201557      <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>
    18211558      <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>
    18221559      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    18231560      <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>
    1824       <tr><td><a name="diff0099" /></td></tr>
     1561      <tr><td><a name="diff0086" /></td></tr>
    18251562      <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>
    18261563      <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>
     
    18291566      <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>
    18301567      <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>
    1831       <tr><td><a name="diff0100" /></td></tr>
     1568      <tr><td><a name="diff0087" /></td></tr>
    18321569      <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>
    18331570      <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>
     
    1835