Ignore:
Timestamp:
08/05/14 13:46:33 (6 years ago)
Author:
julian.reschke@…
Message:

min. fixes (reg names, punctuation, etc) (see #553)

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

Legend:

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

    r2659 r2660  
    124124       3.2.2.  Field Order  . . . . . . . . . . . . . . . . . . . . . 23
    125125       3.2.3.  Whitespace . . . . . . . . . . . . . . . . . . . . . . 24
    126        3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 25
     126       3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 24
    127127       3.2.5.  Field Limits . . . . . . . . . . . . . . . . . . . . . 26
    128128       3.2.6.  Field Value Components . . . . . . . . . . . . . . . . 26
    129129     3.3.  Message Body . . . . . . . . . . . . . . . . . . . . . . . 27
    130130       3.3.1.  Transfer-Encoding  . . . . . . . . . . . . . . . . . . 28
    131        3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . 30
     131       3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . 29
    132132       3.3.3.  Message Body Length  . . . . . . . . . . . . . . . . . 31
    133133     3.4.  Handling Incomplete Messages . . . . . . . . . . . . . . . 33
    134134     3.5.  Message Parsing Robustness . . . . . . . . . . . . . . . . 34
    135    4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 35
     135   4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 34
    136136     4.1.  Chunked Transfer Coding  . . . . . . . . . . . . . . . . . 35
    137137       4.1.1.  Chunk Extensions . . . . . . . . . . . . . . . . . . . 36
    138138       4.1.2.  Chunked Trailer Part . . . . . . . . . . . . . . . . . 36
    139139       4.1.3.  Decoding Chunked . . . . . . . . . . . . . . . . . . . 37
    140      4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 38
     140     4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 37
    141141       4.2.1.  Compress Coding  . . . . . . . . . . . . . . . . . . . 38
    142142       4.2.2.  Deflate Coding . . . . . . . . . . . . . . . . . . . . 38
     
    144144     4.3.  TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
    145145     4.4.  Trailer  . . . . . . . . . . . . . . . . . . . . . . . . . 39
    146    5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . 40
     146   5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . 39
    147147     5.1.  Identifying a Target Resource  . . . . . . . . . . . . . . 40
    148148     5.2.  Connecting Inbound . . . . . . . . . . . . . . . . . . . . 40
    149149     5.3.  Request Target . . . . . . . . . . . . . . . . . . . . . . 41
    150150       5.3.1.  origin-form  . . . . . . . . . . . . . . . . . . . . . 41
    151        5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 42
     151       5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 41
    152152       5.3.3.  authority-form . . . . . . . . . . . . . . . . . . . . 42
    153153       5.3.4.  asterisk-form  . . . . . . . . . . . . . . . . . . . . 42
     
    156156     5.6.  Associating a Response to a Request  . . . . . . . . . . . 46
    157157     5.7.  Message Forwarding . . . . . . . . . . . . . . . . . . . . 46
    158        5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 47
     158       5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 46
    159159       5.7.2.  Transformations  . . . . . . . . . . . . . . . . . . . 48
    160160   6.  Connection Management  . . . . . . . . . . . . . . . . . . . . 49
    161161     6.1.  Connection . . . . . . . . . . . . . . . . . . . . . . . . 50
    162162     6.2.  Establishment  . . . . . . . . . . . . . . . . . . . . . . 51
    163      6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 52
    164        6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 53
     163     6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 51
     164       6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 52
    165165       6.3.2.  Pipelining . . . . . . . . . . . . . . . . . . . . . . 53
    166166
     
    178178     6.7.  Upgrade  . . . . . . . . . . . . . . . . . . . . . . . . . 56
    179179   7.  ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58
    180    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 60
    181      8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 60
     180   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 59
     181     8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 59
    182182     8.2.  URI Scheme Registration  . . . . . . . . . . . . . . . . . 60
    183      8.3.  Internet Media Type Registration . . . . . . . . . . . . . 61
     183     8.3.  Internet Media Type Registration . . . . . . . . . . . . . 60
    184184       8.3.1.  Internet Media Type message/http . . . . . . . . . . . 61
    185185       8.3.2.  Internet Media Type application/http . . . . . . . . . 62
     
    188188       8.4.2.  Registration . . . . . . . . . . . . . . . . . . . . . 64
    189189     8.5.  Content Coding Registration  . . . . . . . . . . . . . . . 64
    190      8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 65
     190     8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 64
    191191       8.6.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 65
    192        8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 66
     192       8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 65
    193193   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 66
    194194     9.1.  Establishing Authority . . . . . . . . . . . . . . . . . . 66
    195195     9.2.  Risks of Intermediaries  . . . . . . . . . . . . . . . . . 67
    196      9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 68
     196     9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 67
    197197     9.4.  Response Splitting . . . . . . . . . . . . . . . . . . . . 68
    198198     9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69
    199199     9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69
    200      9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 70
     200     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 69
    201201     9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70
    202    10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 71
     202   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 70
    203203   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
    204204     11.1. Normative References . . . . . . . . . . . . . . . . . . . 72
    205      11.2. Informative References . . . . . . . . . . . . . . . . . . 74
    206    Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 76
    207      A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 77
    208        A.1.1.  Multi-homed Web Servers  . . . . . . . . . . . . . . . 77
     205     11.2. Informative References . . . . . . . . . . . . . . . . . . 73
     206   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 75
     207     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76
     208       A.1.1.  Multi-homed Web Servers  . . . . . . . . . . . . . . . 76
    209209       A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . 77
    210        A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 78
    211      A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 78
     210       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 77
     211     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 77
    212212   Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 80
    213213   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
     
    869869   "absolute-path" rule is defined for protocol elements that can
    870870   contain a non-empty path component.  (This rule differs slightly from
    871    RFC 3986's path-abempty rule, which allows for an empty path to be
    872    used in references, and path-absolute rule, which does not allow
     871   the path-abempty rule of RFC 3986, which allows for an empty path to
     872   be used in references, and path-absolute rule, which does not allow
    873873   paths that begin with "//".)  A "partial-URI" rule is defined for
    874874   protocol elements that can contain a relative URI but not a fragment
     
    11461146   A request-line begins with a method token, followed by a single space
    11471147   (SP), the request-target, another single space (SP), the protocol
    1148    version, and ending with CRLF.
     1148   version, and ends with CRLF.
    11491149
    11501150     request-line   = method SP request-target SP HTTP-version CRLF
     
    12811281
    12821282   All defined header fields ought to be registered with IANA in the
    1283    Message Header Field Registry, as described in Section 8.3 of
    1284    [RFC7231].
     1283   "Message Headers" registry, as described in Section 8.3 of [RFC7231].
    12851284
    128612853.2.2.  Field Order
     
    13041303   name into one "field-name: field-value" pair, without changing the
    13051304   semantics of the message, by appending each subsequent field value to
     1305   the combined field value in order, separated by a comma.  The order
    13061306
    13071307
     
    13131313
    13141314
    1315    the combined field value in order, separated by a comma.  The order
    13161315   in which header fields with the same field name are received is
    13171316   therefore significant to the interpretation of the combined field
     
    13571356                    ; "bad" whitespace
    13581357
    1359 
    1360 
    1361 
    1362 
    1363 
    1364 
    1365 
    1366 Fielding & Reschke      Expires November 9, 2014               [Page 24]
    1367 
    1368 
    1369 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1370 
    1371 
    137213583.2.4.  Field Parsing
    13731359
     
    13751361   individual header field names.  The contents within a given field
    13761362   value are not parsed until a later stage of message interpretation
     1363
     1364
     1365
     1366Fielding & Reschke      Expires November 9, 2014               [Page 24]
     1367
     1368
     1369Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1370
     1371
    13771372   (usually after the message's entire header section has been
    13781373   processed).  Consequently, this specification does not use ABNF rules
     
    14181413   A proxy or gateway that receives an obs-fold in a response message
    14191414   that is not within a message/http container MUST either discard the
    1420 
    1421 
    1422 
    1423 Fielding & Reschke      Expires November 9, 2014               [Page 25]
    1424 
    1425 
    1426 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1427 
    1428 
    14291415   message and replace it with a 502 (Bad Gateway) response, preferably
    14301416   with a representation explaining that unacceptable line folding was
     
    14321418   octets prior to interpreting the field value or forwarding the
    14331419   message downstream.
     1420
     1421
     1422
     1423Fielding & Reschke      Expires November 9, 2014               [Page 25]
     1424
     1425
     1426Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1427
    14341428
    14351429   A user agent that receives an obs-fold in a response message that is
     
    14731467   (DQUOTE and "(),/:;<=>?@[\]{}").
    14741468
    1475 
    1476 
    1477 
    1478 
    1479 
    1480 Fielding & Reschke      Expires November 9, 2014               [Page 26]
    1481 
    1482 
    1483 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1484 
    1485 
    14861469     token          = 1*tchar
    14871470
     
    14921475
    14931476   A string of text is parsed as a single value if it is quoted using
     1477
     1478
     1479
     1480Fielding & Reschke      Expires November 9, 2014               [Page 26]
     1481
     1482
     1483Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1484
     1485
    14941486   double-quote marks.
    14951487
     
    15321524   The presence of a message body in a request is signaled by a Content-
    15331525   Length or Transfer-Encoding header field.  Request message framing is
    1534 
    1535 
    1536 
    1537 Fielding & Reschke      Expires November 9, 2014               [Page 27]
    1538 
    1539 
    1540 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1541 
    1542 
    15431526   independent of method semantics, even if the method does not define
    15441527   any use for a message body.
     
    15491532   of [RFC7231]) never include a message body because the associated
    15501533   response header fields (e.g., Transfer-Encoding, Content-Length,
     1534
     1535
     1536
     1537Fielding & Reschke      Expires November 9, 2014               [Page 27]
     1538
     1539
     1540Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1541
     1542
    15511543   etc.), if present, indicate only what their values would have been if
    15521544   the request method had been GET (Section 4.3.1 of [RFC7231]). 2xx
     
    15871579   by closing the connection.
    15881580
    1589 
    1590 
    1591 
    1592 
    1593 
    1594 Fielding & Reschke      Expires November 9, 2014               [Page 28]
    1595 
    1596 
    1597 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1598 
    1599 
    16001581   For example,
    16011582
     
    16081589   Unlike Content-Encoding (Section 3.1.2.1 of [RFC7231]), Transfer-
    16091590   Encoding is a property of the message, not of the representation, and
     1591
     1592
     1593
     1594Fielding & Reschke      Expires November 9, 2014               [Page 28]
     1595
     1596
     1597Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1598
     1599
    16101600   any recipient along the request/response chain MAY decode the
    16111601   received transfer coding(s) or apply additional transfer coding(s) to
     
    16431633   does not understand SHOULD respond with 501 (Not Implemented).
    16441634
    1645 
    1646 
    1647 
    1648 
    1649 
    1650 
    1651 Fielding & Reschke      Expires November 9, 2014               [Page 29]
    1652 
    1653 
    1654 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1655 
    1656 
    165716353.3.2.  Content-Length
    16581636
     
    16681646     Content-Length = 1*DIGIT
    16691647
     1648
     1649
     1650
     1651Fielding & Reschke      Expires November 9, 2014               [Page 29]
     1652
     1653
     1654Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1655
     1656
    16701657   An example is
    16711658
     
    17031690   [RFC7231]).
    17041691
    1705 
    1706 
    1707 
    1708 Fielding & Reschke      Expires November 9, 2014               [Page 30]
    1709 
    1710 
    1711 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1712 
    1713 
    17141692   Aside from the cases defined above, in the absence of Transfer-
    17151693   Encoding, an origin server SHOULD send a Content-Length header field
     
    17241702   numerals and prevent parsing errors due to integer conversion
    17251703   overflows (Section 9.3).
     1704
     1705
     1706
     1707
     1708Fielding & Reschke      Expires November 9, 2014               [Page 30]
     1709
     1710
     1711Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1712
    17261713
    17271714   If a message is received that has multiple Content-Length header
     
    17601747   3.  If a Transfer-Encoding header field is present and the chunked
    17611748       transfer coding (Section 4.1) is the final encoding, the message
    1762 
    1763 
    1764 
    1765 Fielding & Reschke      Expires November 9, 2014               [Page 31]
    1766 
    1767 
    1768 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1769 
    1770 
    17711749       body length is determined by reading and decoding the chunked
    17721750       data until the transfer coding indicates the data is complete.
     
    17821760
    17831761       If a message is received with both a Transfer-Encoding and a
     1762
     1763
     1764
     1765Fielding & Reschke      Expires November 9, 2014               [Page 31]
     1766
     1767
     1768Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1769
     1770
    17841771       Content-Length header field, the Transfer-Encoding overrides the
    17851772       Content-Length.  Such a message might indicate an attempt to
     
    18171804       connection.
    18181805
    1819 
    1820 
    1821 
    1822 Fielding & Reschke      Expires November 9, 2014               [Page 32]
    1823 
    1824 
    1825 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1826 
    1827 
    18281806   Since there is no way to distinguish a successfully completed, close-
    18291807   delimited message from a partially received message interrupted by
     
    18391817   valid Content-Length header field if the message body length is known
    18401818   in advance, rather than the chunked transfer coding, since some
     1819
     1820
     1821
     1822Fielding & Reschke      Expires November 9, 2014               [Page 32]
     1823
     1824
     1825Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1826
     1827
    18411828   existing services respond to chunked with a 411 (Length Required)
    18421829   status code even though they understand the chunked transfer coding.
     
    18741861
    18751862   If a response terminates in the middle of the header section (before
    1876 
    1877 
    1878 
    1879 Fielding & Reschke      Expires November 9, 2014               [Page 33]
    1880 
    1881 
    1882 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1883 
    1884 
    18851863   the empty line is received) and the status code might rely on header
    18861864   fields to convey the full meaning of the response, then the client
     
    18961874   connection and, thus, is considered complete regardless of the number
    18971875   of message body octets received, provided that the header section was
     1876
     1877
     1878
     1879Fielding & Reschke      Expires November 9, 2014               [Page 33]
     1880
     1881
     1882Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1883
     1884
    18981885   received intact.
    18991886
     
    19311918   receives a sequence of octets that does not match the HTTP-message
    19321919   grammar aside from the robustness exceptions listed above, the server
    1933 
    1934 
    1935 
    1936 Fielding & Reschke      Expires November 9, 2014               [Page 34]
    1937 
    1938 
    1939 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1940 
    1941 
    19421920   SHOULD respond with a 400 (Bad Request) response.
    19431921
     
    19501928   property of the message rather than a property of the representation
    19511929   that is being transferred.
     1930
     1931
     1932
     1933
     1934
     1935
     1936Fielding & Reschke      Expires November 9, 2014               [Page 34]
     1937
     1938
     1939Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1940
    19521941
    19531942     transfer-coding    = "chunked" ; Section 4.1
     
    19891978     chunk-data     = 1*OCTET ; a sequence of chunk-size octets
    19901979
    1991 
    1992 
    1993 Fielding & Reschke      Expires November 9, 2014               [Page 35]
    1994 
    1995 
    1996 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    1997 
    1998 
    19991980   The chunk-size field is a string of hex digits indicating the size of
    20001981   the chunk-data in octets.  The chunked transfer coding is complete
     
    20041985   A recipient MUST be able to parse and decode the chunked transfer
    20051986   coding.
     1987
     1988
     1989
     1990
     1991
     1992
     1993Fielding & Reschke      Expires November 9, 2014               [Page 35]
     1994
     1995
     1996Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     1997
    20061998
    200719994.1.1.  Chunk Extensions
     
    20452037
    20462038   A sender MUST NOT generate a trailer that contains a field necessary
    2047 
    2048 
    2049 
    2050 Fielding & Reschke      Expires November 9, 2014               [Page 36]
    2051 
    2052 
    2053 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2054 
    2055 
    20562039   for message framing (e.g., Transfer-Encoding and Content-Length),
    20572040   routing (e.g., Host), request modifiers (e.g., controls and
     
    20622045
    20632046   When a chunked message containing a non-empty trailer is received,
     2047
     2048
     2049
     2050Fielding & Reschke      Expires November 9, 2014               [Page 36]
     2051
     2052
     2053Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2054
     2055
    20642056   the recipient MAY process the fields (aside from those forbidden
    20652057   above) as if they were appended to the message's header section.  A
     
    21022094     Remove Trailer from existing header fields
    21032095
    2104 
    2105 
    2106 
    2107 Fielding & Reschke      Expires November 9, 2014               [Page 37]
    2108 
    2109 
    2110 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2111 
    2112 
    211320964.2.  Compression Codings
    21142097
    21152098   The codings defined below can be used to compress the payload of a
    21162099   message.
     2100
     2101
     2102
     2103
     2104
     2105
     2106
     2107Fielding & Reschke      Expires November 9, 2014               [Page 37]
     2108
     2109
     2110Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2111
    21172112
    211821134.2.1.  Compress Coding
     
    21602155   Three examples of TE use are below.
    21612156
    2162 
    2163 
    2164 Fielding & Reschke      Expires November 9, 2014               [Page 38]
    2165 
    2166 
    2167 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2168 
    2169 
    21702157     TE: deflate
    21712158     TE:
    21722159     TE: trailers, deflate;q=0.5
     2160
     2161
     2162
     2163
     2164Fielding & Reschke      Expires November 9, 2014               [Page 38]
     2165
     2166
     2167Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2168
    21732169
    21742170   The presence of the keyword "trailers" indicates that the client is
     
    22132209     Trailer = 1#field-name
    22142210
    2215 
    2216 
    2217 
    2218 
    2219 
    2220 
    2221 Fielding & Reschke      Expires November 9, 2014               [Page 39]
    2222 
    2223 
    2224 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2225 
    2226 
    222722115.  Message Routing
    22282212
     
    22322216   response routing follows the same connection chain back to the
    22332217   client.
     2218
     2219
     2220
     2221Fielding & Reschke      Expires November 9, 2014               [Page 39]
     2222
     2223
     2224Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2225
    22342226
    223522275.1.  Identifying a Target Resource
     
    22732265   directly to an authority for the target resource.  How that is
    22742266   accomplished is dependent on the target URI scheme and defined by its
    2275 
    2276 
    2277 
    2278 Fielding & Reschke      Expires November 9, 2014               [Page 40]
    2279 
    2280 
    2281 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2282 
    2283 
    22842267   associated specification, similar to how this specification defines
    22852268   origin server access for resolution of the "http" (Section 2.7.1) and
     
    22882271   HTTP requirements regarding connection management are defined in
    22892272   Section 6.
     2273
     2274
     2275
     2276
     2277
     2278Fielding & Reschke      Expires November 9, 2014               [Page 40]
     2279
     2280
     2281Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2282
    22902283
    229122845.3.  Request Target
     
    23302323   followed by the remainder of the request message.
    23312324
    2332 
    2333 
    2334 
    2335 Fielding & Reschke      Expires November 9, 2014               [Page 41]
    2336 
    2337 
    2338 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2339 
    2340 
    234123255.3.2.  absolute-form
    23422326
     
    23462330
    23472331     absolute-form  = absolute-URI
     2332
     2333
     2334
     2335Fielding & Reschke      Expires November 9, 2014               [Page 41]
     2336
     2337
     2338Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2339
    23482340
    23492341   The proxy is requested to either service that request from a valid
     
    23872379   send only "*" (%x2A) as the request-target.  For example,
    23882380
    2389 
    2390 
    2391 
    2392 Fielding & Reschke      Expires November 9, 2014               [Page 42]
    2393 
    2394 
    2395 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2396 
    2397 
    23982381     OPTIONS * HTTP/1.1
    23992382
     
    24032386   request-target of "*" when it forwards the request to the indicated
    24042387   origin server.
     2388
     2389
     2390
     2391
     2392Fielding & Reschke      Expires November 9, 2014               [Page 42]
     2393
     2394
     2395Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2396
    24052397
    24062398   For example, the request
     
    24442436   A client MUST send a Host header field in an HTTP/1.1 request even if
    24452437   the request-target is in the absolute-form, since this allows the
    2446 
    2447 
    2448 
    2449 Fielding & Reschke      Expires November 9, 2014               [Page 43]
    2450 
    2451 
    2452 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2453 
    2454 
    24552438   Host information to be forwarded through ancient HTTP/1.0 proxies
    24562439   that might not have implemented Host.
     
    24612444   target.  A proxy that forwards such a request MUST generate a new
    24622445   Host field-value based on the received request-target rather than
     2446
     2447
     2448
     2449Fielding & Reschke      Expires November 9, 2014               [Page 43]
     2450
     2451
     2452Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2453
     2454
    24632455   forward the received Host field-value.
    24642456
     
    25012493      fixed URI authority component, that authority is used for the
    25022494      effective request URI.  If not, then if the request-target is in
    2503 
    2504 
    2505 
    2506 Fielding & Reschke      Expires November 9, 2014               [Page 44]
    2507 
    2508 
    2509 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2510 
    2511 
    25122495      authority-form, the effective request URI's authority component is
    25132496      the same as the request-target.  If not, then if a Host header
     
    25182501      differs from the default port for the effective request URI's
    25192502      scheme, then a colon (":") and the incoming port number (in
     2503
     2504
     2505
     2506Fielding & Reschke      Expires November 9, 2014               [Page 44]
     2507
     2508
     2509Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2510
     2511
    25202512      decimal form) are appended to the authority component.
    25212513
     
    25582550   the connection in which the request was received.  For example, the
    25592551   request might have been misdirected, deliberately or accidentally,
    2560 
    2561 
    2562 
    2563 Fielding & Reschke      Expires November 9, 2014               [Page 45]
    2564 
    2565 
    2566 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2567 
    2568 
    25692552   such that the information within a received request-target or Host
    25702553   header field differs from the host or port upon which the connection
     
    25742557   non-public content, or poison a cache.  See Section 9 for security
    25752558   considerations regarding message routing.
     2559
     2560
     2561
     2562
     2563Fielding & Reschke      Expires November 9, 2014               [Page 45]
     2564
     2565
     2566Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2567
    25762568
    257725695.6.  Associating a Response to a Request
     
    26122604   directly.
    26132605
    2614 
    2615 
    2616 
    2617 
    2618 
    2619 
    2620 Fielding & Reschke      Expires November 9, 2014               [Page 46]
    2621 
    2622 
    2623 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2624 
    2625 
    262626065.7.1.  Via
    26272607
     
    26332613   request loops, and identifying the protocol capabilities of senders
    26342614   along the request/response chain.
     2615
     2616
     2617
     2618
     2619
     2620Fielding & Reschke      Expires November 9, 2014               [Page 46]
     2621
     2622
     2623Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2624
    26352625
    26362626     Via = 1#( received-protocol RWS received-by [ RWS comment ] )
     
    26722662   A sender MAY generate comments in the Via header field to identify
    26732663   the software of each recipient, analogous to the User-Agent and
    2674 
    2675 
    2676 
    2677 Fielding & Reschke      Expires November 9, 2014               [Page 47]
    2678 
    2679 
    2680 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2681 
    2682 
    26832664   Server header fields.  However, all comments in the Via field are
    26842665   optional, and a recipient MAY remove them prior to forwarding the
     
    26912672   www.example.com.  The request received by www.example.com would then
    26922673   have the following Via header field:
     2674
     2675
     2676
     2677Fielding & Reschke      Expires November 9, 2014               [Page 47]
     2678
     2679
     2680Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2681
    26932682
    26942683     Via: 1.0 fred, 1.1 p.example.net
     
    27292718   An HTTP-to-HTTP proxy is called a "transforming proxy" if it is
    27302719   designed or configured to modify messages in a semantically
    2731 
    2732 
    2733 
    2734 Fielding & Reschke      Expires November 9, 2014               [Page 48]
    2735 
    2736 
    2737 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2738 
    2739 
    27402720   meaningful way (i.e., modifications, beyond those required by normal
    27412721   HTTP processing, that change the message in a way that would be
     
    27492729
    27502730   If a proxy receives a request-target with a host name that is not a
     2731
     2732
     2733
     2734Fielding & Reschke      Expires November 9, 2014               [Page 48]
     2735
     2736
     2737Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2738
     2739
    27512740   fully qualified domain name, it MAY add its own domain to the host
    27522741   name it received when forwarding the request.  A proxy MUST NOT
     
    27862775   session-layer connection protocol(s).  HTTP only presumes a reliable
    27872776   transport with in-order delivery of requests and the corresponding
    2788 
    2789 
    2790 
    2791 Fielding & Reschke      Expires November 9, 2014               [Page 49]
    2792 
    2793 
    2794 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2795 
    2796 
    27972777   in-order delivery of responses.  The mapping of HTTP request and
    27982778   response structures onto the data units of an underlying transport
     
    28052785   default TCP port of 80, but the client might be configured to use a
    28062786   proxy via some other connection, port, or protocol.
     2787
     2788
     2789
     2790
     2791Fielding & Reschke      Expires November 9, 2014               [Page 49]
     2792
     2793
     2794Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2795
    28072796
    28082797   HTTP implementations are expected to engage in connection management,
     
    28442833   The Connection header field's value has the following grammar:
    28452834
    2846 
    2847 
    2848 Fielding & Reschke      Expires November 9, 2014               [Page 50]
    2849 
    2850 
    2851 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2852 
    2853 
    28542835     Connection        = 1#connection-option
    28552836     connection-option = token
     
    28612842   example, Cache-Control is never appropriate as a connection option
    28622843   (Section 5.2 of [RFC7234]).
     2844
     2845
     2846
     2847
     2848Fielding & Reschke      Expires November 9, 2014               [Page 50]
     2849
     2850
     2851Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2852
    28632853
    28642854   The connection options do not always correspond to a header field
     
    29012891   protocols.  Each connection applies to only one transport link.
    29022892
    2903 
    2904 
    2905 Fielding & Reschke      Expires November 9, 2014               [Page 51]
    2906 
    2907 
    2908 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2909 
    2910 
    291128936.3.  Persistence
    29122894
     
    29182900
    29192901   A recipient determines whether a connection is persistent or not
     2902
     2903
     2904
     2905Fielding & Reschke      Expires November 9, 2014               [Page 51]
     2906
     2907
     2908Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2909
     2910
    29202911   based on the most recently received message's protocol version and
    29212912   Connection header field (if any):
     
    29552946   with HTTP/1.0 clients.
    29562947
    2957 
    2958 
    2959 
    2960 
    2961 
    2962 Fielding & Reschke      Expires November 9, 2014               [Page 52]
    2963 
    2964 
    2965 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    2966 
    2967 
    296829486.3.1.  Retrying Requests
    29692949
     
    29772957   4.2.2 of [RFC7231]).  A proxy MUST NOT automatically retry non-
    29782958   idempotent requests.
     2959
     2960
     2961
     2962Fielding & Reschke      Expires November 9, 2014               [Page 52]
     2963
     2964
     2965Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     2966
    29792967
    29802968   A user agent MUST NOT automatically retry a request with a non-
     
    30143002   Idempotent methods (Section 4.2.2 of [RFC7231]) are significant to
    30153003   pipelining because they can be automatically retried after a
    3016 
    3017 
    3018 
    3019 Fielding & Reschke      Expires November 9, 2014               [Page 53]
    3020 
    3021 
    3022 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3023 
    3024 
    30253004   connection failure.  A user agent SHOULD NOT pipeline requests after
    30263005   a non-idempotent method, until the final response status code for
     
    30353014   response, the pipelining intermediary MAY attempt to retry a sequence
    30363015   of requests that have yet to receive a response if the requests all
     3016
     3017
     3018
     3019Fielding & Reschke      Expires November 9, 2014               [Page 53]
     3020
     3021
     3022Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3023
     3024
    30373025   have idempotent methods; otherwise, the pipelining intermediary
    30383026   SHOULD forward any received responses and then close the
     
    30713059   existence) of this timeout for either the client or the server.
    30723060
    3073 
    3074 
    3075 
    3076 Fielding & Reschke      Expires November 9, 2014               [Page 54]
    3077 
    3078 
    3079 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3080 
    3081 
    30823061   A client or server that wishes to time out SHOULD issue a graceful
    30833062   close on the connection.  Implementations SHOULD constantly monitor
     
    30933072   request is in progress.
    30943073
     3074
     3075
     3076Fielding & Reschke      Expires November 9, 2014               [Page 54]
     3077
     3078
     3079Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3080
     3081
    30953082   A server SHOULD sustain persistent connections, when possible, and
    30963083   allow the underlying transport's flow-control mechanisms to resolve
     
    31293116   on that connection.
    31303117
    3131 
    3132 
    3133 Fielding & Reschke      Expires November 9, 2014               [Page 55]
    3134 
    3135 
    3136 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3137 
    3138 
    31393118   A client that receives a "close" connection option MUST cease sending
    31403119   requests on that connection and close the connection after reading
     
    31493128   sent by the client before receiving the server's response, the
    31503129   server's TCP stack will send a reset packet to the client;
     3130
     3131
     3132
     3133Fielding & Reschke      Expires November 9, 2014               [Page 55]
     3134
     3135
     3136Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3137
     3138
    31513139   unfortunately, the reset packet might erase the client's
    31523140   unacknowledged input buffers before they can be read and interpreted
     
    31853173   A server that sends a 101 (Switching Protocols) response MUST send an
    31863174   Upgrade header field to indicate the new protocol(s) to which the
    3187 
    3188 
    3189 
    3190 Fielding & Reschke      Expires November 9, 2014               [Page 56]
    3191 
    3192 
    3193 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3194 
    3195 
    31963175   connection is being switched; if multiple protocol layers are being
    31973176   switched, the sender MUST list the protocols in layer-ascending
     
    32053184   Upgrade header field to indicate the acceptable protocols, in order
    32063185   of descending preference.
     3186
     3187
     3188
     3189
     3190Fielding & Reschke      Expires November 9, 2014               [Page 56]
     3191
     3192
     3193Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3194
    32073195
    32083196   A server MAY send an Upgrade header field in any other response to
     
    32393227   protocol; an OPTIONS request can be honored by any protocol.
    32403228
    3241 
    3242 
    3243 
    3244 
    3245 
    3246 
    3247 Fielding & Reschke      Expires November 9, 2014               [Page 57]
    3248 
    3249 
    3250 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3251 
    3252 
    32533229   The following is an example response to the above hypothetical
    32543230   request:
     
    32663242   intermediaries that might not implement the listed protocols.  A
    32673243   server MUST ignore an Upgrade header field that is received in an
     3244
     3245
     3246
     3247Fielding & Reschke      Expires November 9, 2014               [Page 57]
     3248
     3249
     3250Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3251
     3252
    32683253   HTTP/1.0 request.
    32693254
     
    32993284   single comma (",") and optional whitespace (OWS).
    33003285
    3301 
    3302 
    3303 
    3304 Fielding & Reschke      Expires November 9, 2014               [Page 58]
    3305 
    3306 
    3307 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3308 
    3309 
    33103286   In any production that uses the list construct, a sender MUST NOT
    33113287   generate empty list elements.  In other words, a sender MUST generate
     
    33233299
    33243300   For compatibility with legacy list rules, a recipient MUST parse and
     3301
     3302
     3303
     3304Fielding & Reschke      Expires November 9, 2014               [Page 58]
     3305
     3306
     3307Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3308
     3309
    33253310   ignore a reasonable number of empty list elements: enough to handle
    33263311   common mistakes by senders that merge values, but not so much that
     
    33553340   constructs have been expanded.
    33563341
    3357 
    3358 
    3359 
    3360 
    3361 Fielding & Reschke      Expires November 9, 2014               [Page 59]
    3362 
    3363 
    3364 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3365 
    3366 
    336733428.  IANA Considerations
    33683343
     
    33763351   "Permanent Message Header Field Names" registry has been updated
    33773352   accordingly (see [BCP90]).
     3353
     3354
     3355
     3356
     3357
     3358
     3359
     3360
     3361Fielding & Reschke      Expires November 9, 2014               [Page 59]
     3362
     3363
     3364Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3365
    33783366
    33793367   +-------------------+----------+----------+---------------+
     
    34123400   URI Schemes" registry has been updated accordingly.
    34133401
    3414 
    3415 
    3416 
    3417 
    3418 Fielding & Reschke      Expires November 9, 2014               [Page 60]
    3419 
    3420 
    3421 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3422 
    3423 
    34243402   +------------+------------------------------------+---------------+
    34253403   | URI Scheme | Description                        | Reference     |
     
    34353413
    34363414   This document serves as the specification for the Internet media
     3415
     3416
     3417
     3418Fielding & Reschke      Expires November 9, 2014               [Page 60]
     3419
     3420
     3421Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3422
     3423
    34373424   types "message/http" and "application/http".  The following has been
    34383425   registered with IANA.
     
    34673454   Interoperability considerations:  N/A
    34683455
     3456   Published specification:  This specification (see Section 8.3.1).
     3457
     3458   Applications that use this media type:  N/A
     3459
     3460   Fragment identifier considerations:  N/A
     3461
     3462   Additional information:
     3463
     3464      Magic number(s):  N/A
     3465
     3466      Deprecated alias names for this type:  N/A
     3467
     3468      File extension(s):  N/A
    34693469
    34703470
     
    34783478Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    34793479
    3480 
    3481    Published specification:  This specification (see Section 8.3.1).
    3482 
    3483    Applications that use this media type:  N/A
    3484 
    3485    Fragment identifier considerations:  N/A
    3486 
    3487    Additional information:
    3488 
    3489       Magic number(s):  N/A
    3490 
    3491       Deprecated alias names for this type:  N/A
    3492 
    3493       File extension(s):  N/A
    34943480
    34953481      Macintosh file type code(s):  N/A
     
    35273513         body.
    35283514
    3529 
    3530 
    3531 
    3532 Fielding & Reschke      Expires November 9, 2014               [Page 62]
    3533 
    3534 
    3535 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3536 
    3537 
    35383515   Encoding considerations:  HTTP messages enclosed by this type are in
    35393516      "binary" format; use of an appropriate Content-Transfer-Encoding
     
    35483525   Applications that use this media type:  N/A
    35493526
     3527
     3528
     3529
     3530
     3531
     3532Fielding & Reschke      Expires November 9, 2014               [Page 62]
     3533
     3534
     3535Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3536
     3537
    35503538   Fragment identifier considerations:  N/A
    35513539
     
    35823570
    35833571   o  Name
    3584 
    3585 
    3586 
    3587 
    3588 
    3589 Fielding & Reschke      Expires November 9, 2014               [Page 63]
    3590 
    3591 
    3592 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3593 
    35943572
    35953573   o  Description
     
    36053583   4.1 of [RFC5226]), and MUST conform to the purpose of transfer coding
    36063584   defined in this specification.
     3585
     3586
     3587
     3588
     3589Fielding & Reschke      Expires November 9, 2014               [Page 63]
     3590
     3591
     3592Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3593
    36073594
    36083595   Use of program names for the identification of encoding formats is
     
    36353622   registrations below:
    36363623
    3637 
    3638 
    3639 
    3640 
    3641 
    3642 
    3643 
    3644 
    3645 
    3646 Fielding & Reschke      Expires November 9, 2014               [Page 64]
    3647 
    3648 
    3649 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3650 
    3651 
    36523624   +------------+--------------------------------------+---------------+
    36533625   | Name       | Description                          | Reference     |
     
    36693641   <http://www.iana.org/assignments/http-upgrade-tokens>.
    36703642
     3643
     3644
     3645
     3646Fielding & Reschke      Expires November 9, 2014               [Page 64]
     3647
     3648
     3649Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3650
     3651
    367136528.6.1.  Procedure
    36723653
     
    36983679       will normally only be used in the case when a responsible party
    36993680       cannot be contacted.
    3700 
    3701 
    3702 
    3703 Fielding & Reschke      Expires November 9, 2014               [Page 65]
    3704 
    3705 
    3706 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3707 
    37083681
    37093682   This registration procedure for HTTP Upgrade Tokens replaces that
     
    37253698   The responsible party is: "IETF (iesg@ietf.org) - Internet
    37263699   Engineering Task Force".
     3700
     3701
     3702
     3703Fielding & Reschke      Expires November 9, 2014               [Page 65]
     3704
     3705
     3706Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3707
    37273708
    372837099.  Security Considerations
     
    37553736   unknown or untrusted source.
    37563737
    3757 
    3758 
    3759 
    3760 Fielding & Reschke      Expires November 9, 2014               [Page 66]
    3761 
    3762 
    3763 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3764 
    3765 
    37663738   When a registered name is used in the authority component, the "http"
    37673739   URI scheme (Section 2.7.1) relies on the user's local name resolution
     
    37833755   authority, provided that the negotiated TLS connection is secured and
    37843756   the client properly verifies that the communicating server's identity
     3757
     3758
     3759
     3760Fielding & Reschke      Expires November 9, 2014               [Page 66]
     3761
     3762
     3763Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3764
     3765
    37853766   matches the target URI's authority component (see [RFC2818]).
    37863767   Correctly implementing such verification can be difficult (see
     
    38113792   than the people who run them; HTTP itself cannot solve this problem.
    38123793
    3813 
    3814 
    3815 
    3816 
    3817 Fielding & Reschke      Expires November 9, 2014               [Page 67]
    3818 
    3819 
    3820 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3821 
    3822 
    382337949.3.  Attacks via Protocol Element Length
    38243795
     
    38413812
    38423813   Recipients ought to carefully limit the extent to which they process
     3814
     3815
     3816
     3817Fielding & Reschke      Expires November 9, 2014               [Page 67]
     3818
     3819
     3820Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3821
     3822
    38433823   other protocol elements, including (but not limited to) request
    38443824   methods, response status phrases, header field-names, numeric values,
     
    38693849
    38703850   For example, a parameter within the request-target might be read by
    3871 
    3872 
    3873 
    3874 Fielding & Reschke      Expires November 9, 2014               [Page 68]
    3875 
    3876 
    3877 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3878 
    3879 
    38803851   an application server and reused within a redirect, resulting in the
    38813852   same parameter being echoed in the Location header field of the
     
    38973868   stream.
    38983869
     3870
     3871
     3872
     3873
     3874Fielding & Reschke      Expires November 9, 2014               [Page 68]
     3875
     3876
     3877Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3878
     3879
    389938809.5.  Request Smuggling
    39003881
     
    39263907   User agents are encouraged to implement configurable means for
    39273908   detecting and reporting failures of message integrity such that those
    3928 
    3929 
    3930 
    3931 Fielding & Reschke      Expires November 9, 2014               [Page 69]
    3932 
    3933 
    3934 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3935 
    3936 
    39373909   means can be enabled within environments for which integrity is
    39383910   necessary.  For example, a browser being used to view medical history
     
    39553927   URI scheme or within user agent configuration.
    39563928
     3929
     3930
     3931Fielding & Reschke      Expires November 9, 2014               [Page 69]
     3932
     3933
     3934Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3935
     3936
    39573937   The "https" scheme can be used to identify resources that require a
    39583938   confidential connection, as described in Section 2.7.2.
     
    39823962   fraud control.
    39833963
    3984 
    3985 
    3986 
    3987 
    3988 Fielding & Reschke      Expires November 9, 2014               [Page 70]
    3989 
    3990 
    3991 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    3992 
    3993 
    3994396410.  Acknowledgments
    39953965
     
    40133983   Anthony Bryan, Asbjorn Ulsberg, Ashok Kumar, Balachander
    40143984   Krishnamurthy, Barry Leiba, Ben Laurie, Benjamin Carlyle, Benjamin
     3985
     3986
     3987
     3988Fielding & Reschke      Expires November 9, 2014               [Page 70]
     3989
     3990
     3991Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     3992
     3993
    40153994   Niven-Jenkins, Benoit Claise, Bil Corry, Bill Burke, Bjoern
    40163995   Hoehrmann, Bob Scheifler, Boris Zbarsky, Brett Slatkin, Brian Kell,
     
    40404019   Sicking, Jonathan A. Rees, Jonathan Billington, Jonathan Moore,
    40414020   Jonathan Silvera, Jordi Ros, Joris Dobbelsteen, Josh Cohen, Julien
    4042 
    4043 
    4044 
    4045 Fielding & Reschke      Expires November 9, 2014               [Page 71]
    4046 
    4047 
    4048 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4049 
    4050 
    40514021   Pierre, Jungshik Shin, Justin Chapweske, Justin Erenkrantz, Justin
    40524022   James, Kalvinder Singh, Karl Dubost, Kathleen Moriarty, Keith
     
    40704040   Simpson, Robert Brewer, Robert Collins, Robert Mattson, Robert
    40714041   O'Callahan, Robert Olofsson, Robert Sayre, Robert Siemer, Robert de
     4042
     4043
     4044
     4045Fielding & Reschke      Expires November 9, 2014               [Page 71]
     4046
     4047
     4048Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4049
     4050
    40724051   Wilde, Roberto Javier Godoy, Roberto Peon, Roland Zink, Ronny
    40734052   Widjaja, Ryan Hamilton, S. Mike Dierken, Salvatore Loreto, Sam
     
    40984077                 RFC 793, September 1981.
    40994078
    4100 
    4101 
    4102 Fielding & Reschke      Expires November 9, 2014               [Page 72]
    4103 
    4104 
    4105 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4106 
    4107 
    41084079   [RFC1950]     Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data
    41094080                 Format Specification version 3.3", RFC 1950, May 1996.
     
    41264097                 Syntax Specifications: ABNF", STD 68, RFC 5234,
    41274098                 January 2008.
     4099
     4100
     4101
     4102Fielding & Reschke      Expires November 9, 2014               [Page 72]
     4103
     4104
     4105Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4106
    41284107
    41294108   [RFC7231]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
     
    41544133   [USASCII]     American National Standards Institute, "Coded Character
    41554134                 Set -- 7-bit American Standard Code for Information
    4156 
    4157 
    4158 
    4159 Fielding & Reschke      Expires November 9, 2014               [Page 73]
    4160 
    4161 
    4162 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4163 
    4164 
    41654135                 Interchange", ANSI X3.4, 1986.
    41664136
     
    41844154   [Georgiev]    Georgiev, M., Iyengar, S., Jana, S., Anubhai, R.,
    41854155                 Boneh, D., and V. Shmatikov, "The Most Dangerous Code
     4156
     4157
     4158
     4159Fielding & Reschke      Expires November 9, 2014               [Page 73]
     4160
     4161
     4162Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4163
     4164
    41864165                 in the World: Validating SSL Certificates in Non-
    41874166                 browser Software", In Proceedings of the 2012 ACM
     
    42124191                 RFC 1919, March 1996.
    42134192
    4214 
    4215 
    4216 Fielding & Reschke      Expires November 9, 2014               [Page 74]
    4217 
    4218 
    4219 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4220 
    4221 
    42224193   [RFC1945]     Berners-Lee, T., Fielding, R., and H. Nielsen,
    42234194                 "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945,
     
    42404211                 RFC 2145, May 1997.
    42414212
     4213
     4214
     4215
     4216Fielding & Reschke      Expires November 9, 2014               [Page 74]
     4217
     4218
     4219Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4220
     4221
    42424222   [RFC2616]     Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
    42434223                 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
     
    42684248                 Security (TLS) Protocol Version 1.2", RFC 5246,
    42694249                 August 2008.
    4270 
    4271 
    4272 
    4273 Fielding & Reschke      Expires November 9, 2014               [Page 75]
    4274 
    4275 
    4276 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4277 
    42784250
    42794251   [RFC5322]     Resnick, P., "Internet Message Format", RFC 5322,
     
    42964268   However, HTTP/1.0 did not sufficiently take into consideration the
    42974269   effects of hierarchical proxies, caching, the need for persistent
     4270
     4271
     4272
     4273Fielding & Reschke      Expires November 9, 2014               [Page 75]
     4274
     4275
     4276Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4277
     4278
    42984279   connections, or name-based virtual hosts.  The proliferation of
    42994280   incompletely implemented applications calling themselves "HTTP/1.0"
     
    43224303   badly constructed HTTP/1.x requests caused by a client failing to
    43234304   properly encode the request-target.
    4324 
    4325 
    4326 
    4327 
    4328 
    4329 
    4330 Fielding & Reschke      Expires November 9, 2014               [Page 76]
    4331 
    4332 
    4333 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4334 
    43354305
    43364306A.1.  Changes from HTTP/1.0
     
    43554325   complete adoption.  At the time of this writing, most HTTP-based
    43564326   services are dependent upon the Host header field for targeting
     4327
     4328
     4329
     4330Fielding & Reschke      Expires November 9, 2014               [Page 76]
     4331
     4332
     4333Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4334
     4335
    43574336   requests.
    43584337
     
    43824361   header field in any requests.
    43834362
    4384 
    4385 
    4386 
    4387 Fielding & Reschke      Expires November 9, 2014               [Page 77]
    4388 
    4389 
    4390 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4391 
    4392 
    43934363   Clients are also encouraged to consider the use of Connection: keep-
    43944364   alive in requests carefully; while they can enable persistent
     
    44134383   handle multi-digit version numbers incorrectly.  (Section 2.6)
    44144384
     4385
     4386
     4387Fielding & Reschke      Expires November 9, 2014               [Page 77]
     4388
     4389
     4390Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4391
     4392
    44154393   Userinfo (i.e., username and password) are now disallowed in HTTP and
    44164394   HTTPS URIs, because of security issues related to their transmission
     
    44384416   Header fields that span multiple lines ("line folding") are
    44394417   deprecated.  (Section 3.2.4)
    4440 
    4441 
    4442 
    4443 
    4444 Fielding & Reschke      Expires November 9, 2014               [Page 78]
    4445 
    4446 
    4447 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4448 
    44494418
    44504419   The NUL octet is no longer allowed in comment and quoted-string text,
     
    44704439
    44714440   Chunk length does not include the count of the octets in the chunk
     4441
     4442
     4443
     4444Fielding & Reschke      Expires November 9, 2014               [Page 78]
     4445
     4446
     4447Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4448
     4449
    44724450   header and trailer.  Line folding in chunk extensions is disallowed.
    44734451   (Section 4.1)
     
    44964474   the server prematurely closes the connection has been removed.  Also,
    44974475   some extraneous requirements about when servers are allowed to close
    4498 
    4499 
    4500 
    4501 Fielding & Reschke      Expires November 9, 2014               [Page 79]
    4502 
    4503 
    4504 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4505 
    4506 
    45074476   connections prematurely have been removed.  (Section 6.3)
    45084477
     
    45264495   requests are pointed out, with use of the latter being discouraged
    45274496   altogether.  (Appendix A.1.2)
     4497
     4498
     4499
     4500
     4501Fielding & Reschke      Expires November 9, 2014               [Page 79]
     4502
     4503
     4504Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4505
    45284506
    45294507Appendix B.  Collected ABNF
     
    45524530   URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>
    45534531   Upgrade = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
    4554 
    4555 
    4556 
    4557 
    4558 Fielding & Reschke      Expires November 9, 2014               [Page 80]
    4559 
    4560 
    4561 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4562 
    45634532
    45644533   Via = *( "," OWS ) ( received-protocol RWS received-by [ RWS comment
     
    45824551   comment = "(" *( ctext / quoted-pair / comment ) ")"
    45834552   connection-option = token
     4553
     4554
     4555
     4556
     4557
     4558Fielding & Reschke      Expires November 9, 2014               [Page 80]
     4559
     4560
     4561Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4562
     4563
    45844564   ctext = HTAB / SP / %x21-27 ; '!'-'''
    45854565    / %x2A-5B ; '*'-'['
     
    46104590   partial-URI = relative-part [ "?" query ]
    46114591   path-abempty = <path-abempty, defined in [RFC3986], Section 3.3>
    4612 
    4613 
    4614 
    4615 Fielding & Reschke      Expires November 9, 2014               [Page 81]
    4616 
    4617 
    4618 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4619 
    4620 
    46214592   port = <port, defined in [RFC3986], Section 3.2.3>
    46224593   protocol = protocol-name [ "/" protocol-version ]
     
    46384609   relative-part = <relative-part, defined in [RFC3986], Section 4.2>
    46394610   request-line = method SP request-target SP HTTP-version CRLF
     4611
     4612
     4613
     4614
     4615Fielding & Reschke      Expires November 9, 2014               [Page 81]
     4616
     4617
     4618Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4619
     4620
    46404621   request-target = origin-form / absolute-form / authority-form /
    46414622    asterisk-form
     
    46634644
    46644645   A
    4665       absolute-form (of request-target)  42
     4646      absolute-form (of request-target)  41
    46664647      accelerator  10
    46674648      application/http Media Type  62
    46684649      asterisk-form (of request-target)  42
    4669 
    4670 
    4671 
    4672 Fielding & Reschke      Expires November 9, 2014               [Page 82]
    4673 
    4674 
    4675 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4676 
    4677 
    46784650      authoritative response  66
    46794651      authority-form (of request-target)  42
     
    46924664      connection  7
    46934665      Connection header field  50, 55
    4694       Content-Length header field  30
     4666      Content-Length header field  29
    46954667
    46964668   D
     4669
     4670
     4671
     4672Fielding & Reschke      Expires November 9, 2014               [Page 82]
     4673
     4674
     4675Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4676
     4677
    46974678      deflate (Coding Format)  38
    46984679      Delimiters  26
     
    47054686      gateway  10
    47064687      Grammar
    4707          absolute-form  41-42
     4688         absolute-form  41
    47084689         absolute-path  16
    47094690         absolute-URI  16
     
    47214702         chunked-body  35-36
    47224703         comment  27
    4723          Connection  51
    4724          connection-option  51
    4725          Content-Length  30
    4726 
    4727 
    4728 
    4729 Fielding & Reschke      Expires November 9, 2014               [Page 83]
    4730 
    4731 
    4732 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4733 
    4734 
     4704         Connection  50
     4705         connection-option  50
     4706         Content-Length  29
    47354707         CR  6
    47364708         CRLF  6
     
    47524724         http-URI  16
    47534725         HTTP-version  13
     4726
     4727
     4728
     4729Fielding & Reschke      Expires November 9, 2014               [Page 83]
     4730
     4731
     4732Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4733
     4734
    47544735         https-URI  18
    47554736         last-chunk  35
     
    47814762         segment  16
    47824763         SP  6
    4783 
    4784 
    4785 
    4786 Fielding & Reschke      Expires November 9, 2014               [Page 84]
    4787 
    4788 
    4789 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4790 
    4791 
    47924764         start-line  20
    47934765         status-code  22
     
    47954767         t-codings  38
    47964768         t-ranking  38
    4797          tchar  27
     4769         tchar  26
    47984770         TE  38
    4799          token  27
     4771         token  26
    48004772         Trailer  39
    48014773         trailer-part  35-36
     
    48094781         VCHAR  6
    48104782         Via  47
     4783
     4784
     4785
     4786Fielding & Reschke      Expires November 9, 2014               [Page 84]
     4787
     4788
     4789Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4790
     4791
    48114792      gzip (Coding Format)  38
    48124793
     
    48384819      origin server  7
    48394820      origin-form (of request-target)  41
    4840 
    4841 
    4842 
    4843 Fielding & Reschke      Expires November 9, 2014               [Page 85]
    4844 
    4845 
    4846 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4847 
    4848 
    48494821      outbound  9
    48504822
     
    48654837      server  7
    48664838      spider  7
     4839
     4840
     4841
     4842
     4843Fielding & Reschke      Expires November 9, 2014               [Page 85]
     4844
     4845
     4846Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
     4847
    48674848
    48684849   T
     
    48854866
    48864867   V
    4887       Via header field  47
    4888 
    4889 
    4890 
    4891 
    4892 
    4893 
    4894 
    4895 
    4896 
    4897 
    4898 
    4899 
    4900 Fielding & Reschke      Expires November 9, 2014               [Page 86]
    4901 
    4902 
    4903 Internet-Draft     HTTP/1.1 Message Syntax and Routing          May 2014
    4904 
     4868      Via header field  46
    49054869
    49064870Authors' Addresses
     
    49344898
    49354899
    4936 
    4937 
    4938 
    4939 
    4940 
    4941 
    4942 
    4943 
    4944 
    4945 
    4946 
    4947 
    4948 
    4949 
    4950 
    4951 
    4952 
    4953 
    4954 
    4955 
    4956 
    4957 Fielding & Reschke      Expires November 9, 2014               [Page 87]
    4958 
    4959 
     4900Fielding & Reschke      Expires November 9, 2014               [Page 86]
     4901
     4902
  • draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt

    r2659 r2660  
    604604
    605605   All content-coding values are case-insensitive and ought to be
    606    registered within the HTTP Content Coding registry, as defined in
     606   registered within the "HTTP Content Coding Registry", as defined in
    607607   Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)
    608608   and Content-Encoding (Section 3.1.2.2) header fields.
     
    12251225   Additional methods, outside the scope of this specification, have
    12261226   been standardized for use in HTTP.  All such methods ought to be
    1227    registered within the HTTP Method Registry maintained by IANA, as
    1228    defined in Section 8.1.
     1227   registered within the "Hypertext Transfer Protocol (HTTP) Method
     1228   Registry" maintained by IANA, as defined in Section 8.1.
    12291229
    12301230   The set of methods allowed by a target resource can be listed in an
     
    12571257
    12581258   This definition of safe methods does not prevent an implementation
    1259    from including behavior that is potentially harmful, not entirely
    1260    read-only, or which causes side effects while invoking a safe method.
    1261    What is important, however, is that the client did not request that
    1262    additional behavior and cannot be held accountable for it.  For
    1263    example, most servers append request information to access log files
    1264    at the completion of every response, regardless of the method, and
    1265    that is considered safe even though the log storage might become full
    1266    and crash the server.  Likewise, a safe request initiated by
    1267    selecting an advertisement on the Web will often have the side effect
    1268    of charging an advertising account.
     1259   from including behavior that is potentially harmful, that is not
     1260   entirely read-only, or that causes side effects while invoking a safe
     1261   method.  What is important, however, is that the client did not
     1262   request that additional behavior and cannot be held accountable for
     1263   it.  For example, most servers append request information to access
     1264   log files at the completion of every response, regardless of the
     1265   method, and that is considered safe even though the log storage might
     1266   become full and crash the server.  Likewise, a safe request initiated
     1267   by selecting an advertisement on the Web will often have the side
     1268   effect of charging an advertising account.
    12691269
    12701270   Of the request methods defined by this specification, the GET, HEAD,
     
    26902690
    26912691   Responses with status codes that are defined as cacheable by default
    2692    (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this
    2693    specification) can be reused by a cache with heuristic expiration
    2694    unless otherwise indicated by the method definition or explicit cache
    2695    controls [RFC7234]; all other status codes are not cacheable by
    2696    default.
     2692   (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, and 501 in
     2693   this specification) can be reused by a cache with heuristic
     2694   expiration unless otherwise indicated by the method definition or
     2695   explicit cache controls [RFC7234]; all other status codes are not
     2696   cacheable by default.
    26972697
    26982698
     
    31393139   Section 4.2.2 of [RFC7234]).
    31403140
    3141       Note: The original proposal for 300 defined the URI header field
    3142       as providing a list of alternative representations, such that it
    3143       would be usable for 200, 300, and 406 responses and be transferred
    3144       in responses to the HEAD method.  However, lack of deployment and
    3145       disagreement over syntax led to both URI and Alternates (a
    3146       subsequent proposal) being dropped from this specification.  It is
    3147       possible to communicate the list using a set of Link header fields
    3148       [RFC5988], each with a relationship of "alternate", though
    3149       deployment is a chicken-and-egg problem.
     3141      Note: The original proposal for the 300 status code defined the
     3142      URI header field as providing a list of alternative
     3143      representations, such that it would be usable for 200, 300, and
     3144      406 responses and be transferred in responses to the HEAD method.
     3145      However, lack of deployment and disagreement over syntax led to
     3146      both URI and Alternates (a subsequent proposal) being dropped from
     3147      this specification.  It is possible to communicate the list using
     3148      a set of Link header fields [RFC5988], each with a relationship of
     3149      "alternate", though deployment is a chicken-and-egg problem.
    31503150
    315131516.4.2.  301 Moved Permanently
     
    42054205   (Section 4.2.1), idempotent (Section 4.2.2), cacheable
    42064206   (Section 4.2.3), what semantics are to be associated with the payload
    4207    body if any is present in the request, and what refinements the
    4208    method makes to header field or status code semantics.  If the new
    4209    method is cacheable, its definition ought to describe how, and under
    4210    what conditions, a cache can store a response and use it to satisfy a
     4207   body if any is present in the request and what refinements the method
     4208   makes to header field or status code semantics.  If the new method is
     4209   cacheable, its definition ought to describe how, and under what
     4210   conditions, a cache can store a response and use it to satisfy a
    42114211   subsequent request.  The new method ought to describe whether it can
    42124212   be made conditional (Section 5.2) and, if so, how a server responds
     
    47134713   information about the user's immediate browsing history and any
    47144714   personal information that might be found in the referring resource's
    4715    URI.  Limitations on Referer are described in Section 5.5.2 to
    4716    address some of its security considerations.
     4715   URI.  Limitations on the Referer header field are described in
     4716   Section 5.5.2 to address some of its security considerations.
    47174717
    471847189.5.  Disclosure of Fragment after Redirects
     
    51205120   representations and representations from resources.
    51215121
    5122    A new requirement has been added that semantics embedded in a URI
    5123    should be disabled when those semantics are inconsistent with the
    5124    request method, since this is a common cause of interoperability
     5122   A new requirement has been added that semantics embedded in a URI be
     5123   disabled when those semantics are inconsistent with the request
     5124   method, since this is a common cause of interoperability failure.
    51255125
    51265126
     
    51325132
    51335133
    5134    failure.  (Section 2)
     5134   (Section 2)
    51355135
    51365136   An algorithm has been added for determining if a payload is
  • draft-ietf-httpbis/latest/auth48/rfc7230.abdiff.txt

    r2659 r2660  
    127127        3.2.2.  Field Order  . . . . . . . . . . . . . . . . . . . . . 23
    128128        3.2.3.  Whitespace . . . . . . . . . . . . . . . . . . . . . . 24
    129         3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 25
     129        3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 24
    130130        3.2.5.  Field Limits . . . . . . . . . . . . . . . . . . . . . 26
    131131        3.2.6.  Field Value Components . . . . . . . . . . . . . . . . 26
    132132      3.3.  Message Body . . . . . . . . . . . . . . . . . . . . . . . 27
    133133        3.3.1.  Transfer-Encoding  . . . . . . . . . . . . . . . . . . 28
    134         3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . 30
     134        3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . 29
    135135        3.3.3.  Message Body Length  . . . . . . . . . . . . . . . . . 31
    136136      3.4.  Handling Incomplete Messages . . . . . . . . . . . . . . . 33
    137137      3.5.  Message Parsing Robustness . . . . . . . . . . . . . . . . 34
    138     4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 35
     138    4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 34
    139139      4.1.  Chunked Transfer Coding  . . . . . . . . . . . . . . . . . 35
    140140        4.1.1.  Chunk Extensions . . . . . . . . . . . . . . . . . . . 36
    141141        4.1.2.  Chunked Trailer Part . . . . . . . . . . . . . . . . . 36
    142142        4.1.3.  Decoding Chunked . . . . . . . . . . . . . . . . . . . 37
    143       4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 38
     143      4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 37
    144144        4.2.1.  Compress Coding  . . . . . . . . . . . . . . . . . . . 38
    145145        4.2.2.  Deflate Coding . . . . . . . . . . . . . . . . . . . . 38
     
    147147      4.3.  TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
    148148      4.4.  Trailer  . . . . . . . . . . . . . . . . . . . . . . . . . 39
    149     5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . 40
     149    5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . 39
    150150      5.1.  Identifying a Target Resource  . . . . . . . . . . . . . . 40
    151151      5.2.  Connecting Inbound . . . . . . . . . . . . . . . . . . . . 40
    152152      5.3.  Request Target . . . . . . . . . . . . . . . . . . . . . . 41
    153153        5.3.1.  origin-form  . . . . . . . . . . . . . . . . . . . . . 41
    154         5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 42
     154        5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 41
    155155        5.3.3.  authority-form . . . . . . . . . . . . . . . . . . . . 42
    156156        5.3.4.  asterisk-form  . . . . . . . . . . . . . . . . . . . . 42
     
    159159      5.6.  Associating a Response to a Request  . . . . . . . . . . . 46
    160160      5.7.  Message Forwarding . . . . . . . . . . . . . . . . . . . . 46
    161         5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 47
     161        5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 46
    162162        5.7.2.  Transformations  . . . . . . . . . . . . . . . . . . . 48
    163163    6.  Connection Management  . . . . . . . . . . . . . . . . . . . . 49
    164164      6.1.  Connection . . . . . . . . . . . . . . . . . . . . . . . . 50
    165165      6.2.  Establishment  . . . . . . . . . . . . . . . . . . . . . . 51
    166       6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 52
    167         6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 53
     166      6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 51
     167        6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 52
    168168        6.3.2.  Pipelining . . . . . . . . . . . . . . . . . . . . . . 53
    169169 
     
    173173      6.7.  Upgrade  . . . . . . . . . . . . . . . . . . . . . . . . . 56
    174174    7.  ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58
    175     8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 60
    176       8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 60
     175    8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 59
     176      8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 59
    177177      8.2.  URI Scheme Registration  . . . . . . . . . . . . . . . . . 60
    178       8.3.  Internet Media Type Registration . . . . . . . . . . . . . 61
     178      8.3.  Internet Media Type Registration . . . . . . . . . . . . . 60
    179179        8.3.1.  Internet Media Type message/http . . . . . . . . . . . 61
    180180        8.3.2.  Internet Media Type application/http . . . . . . . . . 62
     
    183183        8.4.2.  Registration . . . . . . . . . . . . . . . . . . . . . 64
    184184      8.5.  Content Coding Registration  . . . . . . . . . . . . . . . 64
    185       8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 65
     185      8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 64
    186186        8.6.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 65
    187         8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 66
     187        8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 65
    188188    9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 66
    189189      9.1.  Establishing Authority . . . . . . . . . . . . . . . . . . 66
    190190      9.2.  Risks of Intermediaries  . . . . . . . . . . . . . . . . . 67
    191       9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 68
     191      9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 67
    192192      9.4.  Response Splitting . . . . . . . . . . . . . . . . . . . . 68
    193193      9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69
    194194      9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69
    195       9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 70
     195      9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 69
    196196      9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70
    197     10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 71
     197    10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 70
    198198    11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72
    199199      11.1. Normative References . . . . . . . . . . . . . . . . . . . 72
    200       11.2. Informative References . . . . . . . . . . . . . . . . . . 74
    201     Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 76
    202       A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 77
    203         A.1.1.  Multi-homed Web Servers  . . . . . . . . . . . . . . . 77
     200      11.2. Informative References . . . . . . . . . . . . . . . . . . 73
     201    Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 75
     202      A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76
     203        A.1.1.  Multi-homed Web Servers  . . . . . . . . . . . . . . . 76
    204204        A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . 77
    205         A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 78
    206       A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 78
     205        A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 77
     206      A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 77
    207207    Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 80
    208208    Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
     
    418418
    419419
    420 Section 2.7., paragraph 2:
    421 OLD:
    422 
    423     The definitions of "URI-reference", "absolute-URI", "relative-part",
    424     "scheme", "authority", "port", "host", "path-abempty", "segment",
    425     "query", and "fragment" are adopted from the URI generic syntax.  An
    426     "absolute-path" rule is defined for protocol elements that can
    427     contain a non-empty path component.  (This rule differs slightly from
    428     RFC 3986's path-abempty rule, which allows for an empty path to be
    429     used in references, and path-absolute rule, which does not allow
    430     paths that begin with "//".)  A "partial-URI" rule is defined for
    431     protocol elements that can contain a relative URI but not a fragment
    432     component.
    433 
    434 NEW:
    435 
    436     The definitions of "URI-reference", "absolute-URI", "relative-part",
    437     "scheme", "authority", "port", "host", "path-abempty", "segment",
    438     "query", and "fragment" are adopted from the URI generic syntax.  An
    439     "absolute-path" rule is defined for protocol elements that can
    440     contain a non-empty path component.  (This rule differs slightly from
    441     the path-abempty rule of RFC 3986, which allows for an empty path to
    442     be used in references, and path-absolute rule, which does not allow
    443     paths that begin with "//".)  A "partial-URI" rule is defined for
    444     protocol elements that can contain a relative URI but not a fragment
    445     component.
    446 
    447 
    448420Section 2.7.1., paragraph 1:
    449421OLD:
     
    513485    A request-line begins with a method token, followed by a single space
    514486    (SP), the request-target, another single space (SP), the protocol
    515     version, and ending with CRLF.
     487    version, and ends with CRLF.
    516488
    517489NEW:
     
    554526
    555527    All defined header fields ought to be registered with IANA in the
    556     Message Header Field Registry, as described in Section 8.3 of
    557     [RFC7231].
     528    "Message Headers" registry, as described in Section 8.3 of [RFC7231].
    558529
    559530NEW:
     
    654625
    655626
     627Section 5.3.4., paragraph 3:
     628OLD:
     629
     630    When a client wishes to request OPTIONS for the server as a whole, as
     631    opposed to a specific named resource of that server, the client MUST
     632    send only "*" (%x2A) as the request-target.  For example,
     633 
     634      OPTIONS * HTTP/1.1
     635
     636NEW:
     637
     638    When a client wishes to request OPTIONS for the server as a whole, as
     639    opposed to a specific named resource of that server, the client MUST
     640    send only "*" (%x2A) as the request-target.  For example,
     641      OPTIONS * HTTP/1.1
     642
     643
    656644Section 5.7.2., paragraph 6:
    657645OLD:
     
    808796
    809797
     798Section 8.3.1., paragraph 10:
     799OLD:
     800
     801    Interoperability considerations:  N/A
     802 
     803    Published specification:  This specification (see Section 8.3.1).
     804
     805NEW:
     806
     807    Interoperability considerations:  N/A
     808    Published specification:  This specification (see Section 8.3.1).
     809
     810
     811Section 8.3.1., paragraph 16:
     812OLD:
     813
     814       File extension(s):  N/A
     815       Macintosh file type code(s):  N/A
     816
     817NEW:
     818
     819       File extension(s):  N/A
     820 
     821       Macintosh file type code(s):  N/A
     822
     823
     824Section 8.3.2., paragraph 12:
     825OLD:
     826
     827    Applications that use this media type:  N/A
     828    Fragment identifier considerations:  N/A
     829
     830NEW:
     831
     832    Applications that use this media type:  N/A
     833 
     834    Fragment identifier considerations:  N/A
     835
     836
    810837Section 8.4., paragraph 1:
    811838OLD:
     
    820847    transfer coding names.  It is maintained at
    821848    <http://www.iana.org/assignments/http-parameters>.
     849
     850
     851Section 8.4.1., paragraph 2:
     852OLD:
     853
     854    o  Name
     855 
     856    o  Description
     857
     858NEW:
     859
     860    o  Name
     861    o  Description
    822862
    823863
     
    10541094    single digits, due to the fact that implementations are known to
    10551095    handle multi-digit version numbers incorrectly.  (Section 2.6)
     1096    Userinfo (i.e., username and password) are now disallowed in HTTP and
     1097    HTTPS URIs, because of security issues related to their transmission
     1098    on the wire.  (Section 2.7.1)
    10561099
    10571100NEW:
     
    10611104    single digits, due to the fact that implementations are known to
    10621105    handle multi-digit version numbers incorrectly (Section 2.6).
    1063 
    1064 
    1065 Section 19.7.1, paragraph 10:
    1066 OLD:
    1067 
    1068     Userinfo (i.e., username and password) are now disallowed in HTTP and
    1069     HTTPS URIs, because of security issues related to their transmission
    1070     on the wire.  (Section 2.7.1)
    1071 
    1072 NEW:
    1073 
     1106 
    10741107    Userinfo (i.e., username and password) are now disallowed in HTTP and
    10751108    HTTPS URIs, because of security issues related to their transmission
     
    10771110
    10781111
    1079 Section 19.7.1, paragraph 11:
     1112Section 19.7.1, paragraph 10:
    10801113OLD:
    10811114
     
    10911124
    10921125
    1093 Section 19.7.1, paragraph 12:
     1126Section 19.7.1, paragraph 11:
    10941127OLD:
    10951128
     
    11091142
    11101143
    1111 Section 19.7.1, paragraph 13:
     1144Section 19.7.1, paragraph 12:
    11121145OLD:
    11131146
     
    11251158
    11261159
    1127 Section 19.7.1, paragraph 14:
     1160Section 19.7.1, paragraph 13:
    11281161OLD:
    11291162
     
    11391172
    11401173
    1141 Section 19.7.1, paragraph 15:
     1174Section 19.7.1, paragraph 14:
    11421175OLD:
    11431176
    11441177    Header fields that span multiple lines ("line folding") are
    11451178    deprecated.  (Section 3.2.4)
     1179
     1180NEW:
     1181
     1182    Header fields that span multiple lines ("line folding") are
     1183    deprecated (Section 3.2.4).
     1184
     1185
     1186Section 19.7.1, paragraph 15:
     1187OLD:
     1188
    11461189    The NUL octet is no longer allowed in comment and quoted-string text,
    11471190    and handling of backslash-escaping in them has been clarified.  The
     
    11531196NEW:
    11541197
    1155     Header fields that span multiple lines ("line folding") are
    1156     deprecated (Section 3.2.4).
    1157  
    11581198    The NUL octet is no longer allowed in comment and quoted-string text,
    11591199    and handling of backslash-escaping in them has been clarified.  The
     
    13861426
    13871427
    1388 Appendix B., paragraph 7:
    1389 OLD:
    1390 
    1391     URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>
    1392     Upgrade = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
    1393     Via = *( "," OWS ) ( received-protocol RWS received-by [ RWS comment
    1394      ] ) *( OWS "," [ OWS ( received-protocol RWS received-by [ RWS
    1395      comment ] ) ] )
    1396 
    1397 NEW:
    1398 
    1399     URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>
    1400     Upgrade = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
    1401  
    1402     Via = *( "," OWS ) ( received-protocol RWS received-by [ RWS comment
    1403      ] ) *( OWS "," [ OWS ( received-protocol RWS received-by [ RWS
    1404      comment ] ) ] )
    1405 
    1406 
    1407 Appendix B., paragraph 15:
     1428Appendix B., paragraph 16:
    14081429OLD:
    14091430
     
    14401461
    14411462
     1463Appendix B., paragraph 22:
     1464OLD:
     1465
     1466    A
     1467       absolute-form (of request-target)  41
     1468       accelerator  10
     1469       application/http Media Type  62
     1470       asterisk-form (of request-target)  42
     1471       authoritative response  66
     1472       authority-form (of request-target)  42
     1473
     1474NEW:
     1475
     1476    A
     1477       absolute-form (of request-target)  42
     1478       accelerator  10
     1479       application/http Media Type  62
     1480       asterisk-form (of request-target)  42
     1481       authoritative response  66
     1482       authority-form (of request-target)  42
     1483
     1484
    14421485Appendix B., paragraph 24:
     1486OLD:
     1487
     1488    C
     1489       cache  11
     1490       cacheable  11
     1491       captive portal  11
     1492       chunked (Coding Format)  28, 31, 35
     1493       client  7
     1494       close  50, 55
     1495       compress (Coding Format)  38
     1496       connection  7
     1497       Connection header field  50, 55
     1498       Content-Length header field  29
     1499
     1500NEW:
     1501
     1502    C
     1503       cache  11
     1504       cacheable  11
     1505       captive portal  11
     1506       chunked (Coding Format)  28, 31, 35
     1507       client  7
     1508       close  50, 55
     1509       compress (Coding Format)  38
     1510       connection  7
     1511       Connection header field  50, 55
     1512       Content-Length header field  30
     1513
     1514
     1515Appendix B., paragraph 25:
    14431516OLD:
    14441517
     
    14561529
    14571530
    1458 Appendix B., paragraph 26:
     1531Appendix B., paragraph 27:
    14591532OLD:
    14601533
     
    14621535       gateway  10
    14631536       Grammar
    1464           absolute-form  41-42
     1537          absolute-form  41
    14651538          absolute-path  16
    14661539          absolute-URI  16
     
    14781551          chunked-body  35-36
    14791552          comment  27
    1480           Connection  51
    1481           connection-option  51
    1482           Content-Length  30
     1553          Connection  50
     1554          connection-option  50
     1555          Content-Length  29
    14831556          CR  6
    14841557          CRLF  6
     
    15341607          t-codings  38
    15351608          t-ranking  38
    1536           tchar  27
     1609          tchar  26
    15371610          TE  38
    1538           token  27
     1611          token  26
    15391612          Trailer  39
    15401613          trailer-part  35-36
     
    15481621          VCHAR  6
    15491622          Via  47
     1623 
    15501624       gzip (Coding Format)  38
    15511625
     
    16441718
    16451719
    1646 Appendix B., paragraph 28:
     1720Appendix B., paragraph 29:
    16471721OLD:
    16481722
     
    16601734
    16611735
    1662 Appendix B., paragraph 31:
     1736Appendix B., paragraph 32:
    16631737OLD:
    16641738
     
    16761750
    16771751
    1678 Appendix B., paragraph 36:
     1752Appendix B., paragraph 37:
    16791753OLD:
    16801754
     
    16961770          https  18
    16971771       user agent  7
     1772
     1773
     1774Appendix B., paragraph 38:
     1775OLD:
     1776
     1777    V
     1778       Via header field  46
     1779
     1780NEW:
     1781
     1782    V
     1783       Via header field  47
    16981784
    16991785
  • draft-ietf-httpbis/latest/auth48/rfc7230.diff.html

    r2659 r2660  
    110110      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
    111111      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    112       <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 4, line 4</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 3, line 32</em></th><td></td></tr>
     112      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 3, line 4</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 2, line 33</em></th><td></td></tr>
     113      <tr><td class="lineno" valign="top"></td><td class="left">     2.1.  Client/Server Messaging  . . . . . . . . . . . . . . . . .  7</td><td> </td><td class="right">     2.1.  Client/Server Messaging  . . . . . . . . . . . . . . . . .  7</td><td class="lineno" valign="top"></td></tr>
     114      <tr><td class="lineno" valign="top"></td><td class="left">     2.2.  Implementation Diversity . . . . . . . . . . . . . . . . .  8</td><td> </td><td class="right">     2.2.  Implementation Diversity . . . . . . . . . . . . . . . . .  8</td><td class="lineno" valign="top"></td></tr>
     115      <tr><td class="lineno" valign="top"></td><td class="left">     2.3.  Intermediaries . . . . . . . . . . . . . . . . . . . . . .  9</td><td> </td><td class="right">     2.3.  Intermediaries . . . . . . . . . . . . . . . . . . . . . .  9</td><td class="lineno" valign="top"></td></tr>
     116      <tr><td class="lineno" valign="top"></td><td class="left">     2.4.  Caches . . . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td> </td><td class="right">     2.4.  Caches . . . . . . . . . . . . . . . . . . . . . . . . . . 11</td><td class="lineno" valign="top"></td></tr>
     117      <tr><td class="lineno" valign="top"></td><td class="left">     2.5.  Conformance and Error Handling . . . . . . . . . . . . . . 12</td><td> </td><td class="right">     2.5.  Conformance and Error Handling . . . . . . . . . . . . . . 12</td><td class="lineno" valign="top"></td></tr>
     118      <tr><td class="lineno" valign="top"></td><td class="left">     2.6.  Protocol Versioning  . . . . . . . . . . . . . . . . . . . 13</td><td> </td><td class="right">     2.6.  Protocol Versioning  . . . . . . . . . . . . . . . . . . . 13</td><td class="lineno" valign="top"></td></tr>
     119      <tr><td class="lineno" valign="top"></td><td class="left">     2.7.  Uniform Resource Identifiers . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">     2.7.  Uniform Resource Identifiers . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
     120      <tr><td class="lineno" valign="top"></td><td class="left">       2.7.1.  http URI Scheme  . . . . . . . . . . . . . . . . . . . 16</td><td> </td><td class="right">       2.7.1.  http URI Scheme  . . . . . . . . . . . . . . . . . . . 16</td><td class="lineno" valign="top"></td></tr>
     121      <tr><td class="lineno" valign="top"></td><td class="left">       2.7.2.  https URI Scheme . . . . . . . . . . . . . . . . . . . 18</td><td> </td><td class="right">       2.7.2.  https URI Scheme . . . . . . . . . . . . . . . . . . . 18</td><td class="lineno" valign="top"></td></tr>
     122      <tr><td class="lineno" valign="top"></td><td class="left">       2.7.3.  http and https URI Normalization and Comparison  . . . 19</td><td> </td><td class="right">       2.7.3.  http and https URI Normalization and Comparison  . . . 19</td><td class="lineno" valign="top"></td></tr>
     123      <tr><td><a name="diff0008" /></td></tr>
     124      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     125      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Message Format . . . . . . . . . . . . . . . . . . . . . . . . 19</td><td> </td><td class="right">   3.  Message Format . . . . . . . . . . . . . . . . . . . . . . . . 19</td><td class="lineno" valign="top"></td></tr>
     126      <tr><td class="lineno" valign="top"></td><td class="left">     3.1.  Start Line . . . . . . . . . . . . . . . . . . . . . . . . 20</td><td> </td><td class="right">     3.1.  Start Line . . . . . . . . . . . . . . . . . . . . . . . . 20</td><td class="lineno" valign="top"></td></tr>
     127      <tr><td class="lineno" valign="top"></td><td class="left">       3.1.1.  Request Line . . . . . . . . . . . . . . . . . . . . . 21</td><td> </td><td class="right">       3.1.1.  Request Line . . . . . . . . . . . . . . . . . . . . . 21</td><td class="lineno" valign="top"></td></tr>
     128      <tr><td class="lineno" valign="top"></td><td class="left">       3.1.2.  Status Line  . . . . . . . . . . . . . . . . . . . . . 22</td><td> </td><td class="right">       3.1.2.  Status Line  . . . . . . . . . . . . . . . . . . . . . 22</td><td class="lineno" valign="top"></td></tr>
     129      <tr><td class="lineno" valign="top"></td><td class="left">     3.2.  Header Fields  . . . . . . . . . . . . . . . . . . . . . . 22</td><td> </td><td class="right">     3.2.  Header Fields  . . . . . . . . . . . . . . . . . . . . . . 22</td><td class="lineno" valign="top"></td></tr>
     130      <tr><td class="lineno" valign="top"></td><td class="left">       3.2.1.  Field Extensibility  . . . . . . . . . . . . . . . . . 23</td><td> </td><td class="right">       3.2.1.  Field Extensibility  . . . . . . . . . . . . . . . . . 23</td><td class="lineno" valign="top"></td></tr>
     131      <tr><td class="lineno" valign="top"></td><td class="left">       3.2.2.  Field Order  . . . . . . . . . . . . . . . . . . . . . 23</td><td> </td><td class="right">       3.2.2.  Field Order  . . . . . . . . . . . . . . . . . . . . . 23</td><td class="lineno" valign="top"></td></tr>
     132      <tr><td class="lineno" valign="top"></td><td class="left">       3.2.3.  Whitespace . . . . . . . . . . . . . . . . . . . . . . 24</td><td> </td><td class="right">       3.2.3.  Whitespace . . . . . . . . . . . . . . . . . . . . . . 24</td><td class="lineno" valign="top"></td></tr>
     133      <tr><td><a name="diff0009" /></td></tr>
     134      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 2<span class="delete">4</span></td><td> </td><td class="rblock">       3.2.4.  Field Parsing  . . . . . . . . . . . . . . . . . . . . 2<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
     135      <tr><td class="lineno" valign="top"></td><td class="left">       3.2.5.  Field Limits . . . . . . . . . . . . . . . . . . . . . 26</td><td> </td><td class="right">       3.2.5.  Field Limits . . . . . . . . . . . . . . . . . . . . . 26</td><td class="lineno" valign="top"></td></tr>
     136      <tr><td class="lineno" valign="top"></td><td class="left">       3.2.6.  Field Value Components . . . . . . . . . . . . . . . . 26</td><td> </td><td class="right">       3.2.6.  Field Value Components . . . . . . . . . . . . . . . . 26</td><td class="lineno" valign="top"></td></tr>
     137      <tr><td class="lineno" valign="top"></td><td class="left">     3.3.  Message Body . . . . . . . . . . . . . . . . . . . . . . . 27</td><td> </td><td class="right">     3.3.  Message Body . . . . . . . . . . . . . . . . . . . . . . . 27</td><td class="lineno" valign="top"></td></tr>
     138      <tr><td class="lineno" valign="top"></td><td class="left">       3.3.1.  Transfer-Encoding  . . . . . . . . . . . . . . . . . . 28</td><td> </td><td class="right">       3.3.1.  Transfer-Encoding  . . . . . . . . . . . . . . . . . . 28</td><td class="lineno" valign="top"></td></tr>
     139      <tr><td><a name="diff0010" /></td></tr>
     140      <tr><td class="lineno" valign="top"></td><td class="lblock">       3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . <span class="delete">29</span></td><td> </td><td class="rblock">       3.3.2.  Content-Length . . . . . . . . . . . . . . . . . . . . <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     141      <tr><td class="lineno" valign="top"></td><td class="left">       3.3.3.  Message Body Length  . . . . . . . . . . . . . . . . . 31</td><td> </td><td class="right">       3.3.3.  Message Body Length  . . . . . . . . . . . . . . . . . 31</td><td class="lineno" valign="top"></td></tr>
     142      <tr><td class="lineno" valign="top"></td><td class="left">     3.4.  Handling Incomplete Messages . . . . . . . . . . . . . . . 33</td><td> </td><td class="right">     3.4.  Handling Incomplete Messages . . . . . . . . . . . . . . . 33</td><td class="lineno" valign="top"></td></tr>
     143      <tr><td class="lineno" valign="top"></td><td class="left">     3.5.  Message Parsing Robustness . . . . . . . . . . . . . . . . 34</td><td> </td><td class="right">     3.5.  Message Parsing Robustness . . . . . . . . . . . . . . . . 34</td><td class="lineno" valign="top"></td></tr>
     144      <tr><td><a name="diff0011" /></td></tr>
     145      <tr><td class="lineno" valign="top"></td><td class="lblock">   4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 3<span class="delete">4</span></td><td> </td><td class="rblock">   4.  Transfer Codings . . . . . . . . . . . . . . . . . . . . . . . 3<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
     146      <tr><td class="lineno" valign="top"></td><td class="left">     4.1.  Chunked Transfer Coding  . . . . . . . . . . . . . . . . . 35</td><td> </td><td class="right">     4.1.  Chunked Transfer Coding  . . . . . . . . . . . . . . . . . 35</td><td class="lineno" valign="top"></td></tr>
     147      <tr><td class="lineno" valign="top"></td><td class="left">       4.1.1.  Chunk Extensions . . . . . . . . . . . . . . . . . . . 36</td><td> </td><td class="right">       4.1.1.  Chunk Extensions . . . . . . . . . . . . . . . . . . . 36</td><td class="lineno" valign="top"></td></tr>
     148      <tr><td class="lineno" valign="top"></td><td class="left">       4.1.2.  Chunked Trailer Part . . . . . . . . . . . . . . . . . 36</td><td> </td><td class="right">       4.1.2.  Chunked Trailer Part . . . . . . . . . . . . . . . . . 36</td><td class="lineno" valign="top"></td></tr>
     149      <tr><td class="lineno" valign="top"></td><td class="left">       4.1.3.  Decoding Chunked . . . . . . . . . . . . . . . . . . . 37</td><td> </td><td class="right">       4.1.3.  Decoding Chunked . . . . . . . . . . . . . . . . . . . 37</td><td class="lineno" valign="top"></td></tr>
     150      <tr><td><a name="diff0012" /></td></tr>
     151      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 3<span class="delete">7</span></td><td> </td><td class="rblock">     4.2.  Compression Codings  . . . . . . . . . . . . . . . . . . . 3<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
     152      <tr><td class="lineno" valign="top"></td><td class="left">       4.2.1.  Compress Coding  . . . . . . . . . . . . . . . . . . . 38</td><td> </td><td class="right">       4.2.1.  Compress Coding  . . . . . . . . . . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
     153      <tr><td class="lineno" valign="top"></td><td class="left">       4.2.2.  Deflate Coding . . . . . . . . . . . . . . . . . . . . 38</td><td> </td><td class="right">       4.2.2.  Deflate Coding . . . . . . . . . . . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
     154      <tr><td class="lineno" valign="top"></td><td class="left">       4.2.3.  Gzip Coding  . . . . . . . . . . . . . . . . . . . . . 38</td><td> </td><td class="right">       4.2.3.  Gzip Coding  . . . . . . . . . . . . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
     155      <tr><td class="lineno" valign="top"></td><td class="left">     4.3.  TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38</td><td> </td><td class="right">     4.3.  TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38</td><td class="lineno" valign="top"></td></tr>
     156      <tr><td class="lineno" valign="top"></td><td class="left">     4.4.  Trailer  . . . . . . . . . . . . . . . . . . . . . . . . . 39</td><td> </td><td class="right">     4.4.  Trailer  . . . . . . . . . . . . . . . . . . . . . . . . . 39</td><td class="lineno" valign="top"></td></tr>
     157      <tr><td><a name="diff0013" /></td></tr>
     158      <tr><td class="lineno" valign="top"></td><td class="lblock">   5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">39</span></td><td> </td><td class="rblock">   5.  Message Routing  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">40</span></td><td class="lineno" valign="top"></td></tr>
     159      <tr><td class="lineno" valign="top"></td><td class="left">     5.1.  Identifying a Target Resource  . . . . . . . . . . . . . . 40</td><td> </td><td class="right">     5.1.  Identifying a Target Resource  . . . . . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
     160      <tr><td class="lineno" valign="top"></td><td class="left">     5.2.  Connecting Inbound . . . . . . . . . . . . . . . . . . . . 40</td><td> </td><td class="right">     5.2.  Connecting Inbound . . . . . . . . . . . . . . . . . . . . 40</td><td class="lineno" valign="top"></td></tr>
     161      <tr><td class="lineno" valign="top"></td><td class="left">     5.3.  Request Target . . . . . . . . . . . . . . . . . . . . . . 41</td><td> </td><td class="right">     5.3.  Request Target . . . . . . . . . . . . . . . . . . . . . . 41</td><td class="lineno" valign="top"></td></tr>
     162      <tr><td class="lineno" valign="top"></td><td class="left">       5.3.1.  origin-form  . . . . . . . . . . . . . . . . . . . . . 41</td><td> </td><td class="right">       5.3.1.  origin-form  . . . . . . . . . . . . . . . . . . . . . 41</td><td class="lineno" valign="top"></td></tr>
     163      <tr><td><a name="diff0014" /></td></tr>
     164      <tr><td class="lineno" valign="top"></td><td class="lblock">       5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 4<span class="delete">1</span></td><td> </td><td class="rblock">       5.3.2.  absolute-form  . . . . . . . . . . . . . . . . . . . . 4<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
     165      <tr><td class="lineno" valign="top"></td><td class="left">       5.3.3.  authority-form . . . . . . . . . . . . . . . . . . . . 42</td><td> </td><td class="right">       5.3.3.  authority-form . . . . . . . . . . . . . . . . . . . . 42</td><td class="lineno" valign="top"></td></tr>
     166      <tr><td class="lineno" valign="top"></td><td class="left">       5.3.4.  asterisk-form  . . . . . . . . . . . . . . . . . . . . 42</td><td> </td><td class="right">       5.3.4.  asterisk-form  . . . . . . . . . . . . . . . . . . . . 42</td><td class="lineno" valign="top"></td></tr>
     167      <tr><td class="lineno" valign="top"></td><td class="left">     5.4.  Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 43</td><td> </td><td class="right">     5.4.  Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 43</td><td class="lineno" valign="top"></td></tr>
     168      <tr><td class="lineno" valign="top"></td><td class="left">     5.5.  Effective Request URI  . . . . . . . . . . . . . . . . . . 44</td><td> </td><td class="right">     5.5.  Effective Request URI  . . . . . . . . . . . . . . . . . . 44</td><td class="lineno" valign="top"></td></tr>
    113169      <tr><td class="lineno" valign="top"></td><td class="left">     5.6.  Associating a Response to a Request  . . . . . . . . . . . 46</td><td> </td><td class="right">     5.6.  Associating a Response to a Request  . . . . . . . . . . . 46</td><td class="lineno" valign="top"></td></tr>
    114170      <tr><td class="lineno" valign="top"></td><td class="left">     5.7.  Message Forwarding . . . . . . . . . . . . . . . . . . . . 46</td><td> </td><td class="right">     5.7.  Message Forwarding . . . . . . . . . . . . . . . . . . . . 46</td><td class="lineno" valign="top"></td></tr>
    115       <tr><td class="lineno" valign="top"></td><td class="left">       5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 47</td><td> </td><td class="right">       5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 47</td><td class="lineno" valign="top"></td></tr>
     171      <tr><td><a name="diff0015" /></td></tr>
     172      <tr><td class="lineno" valign="top"></td><td class="lblock">       5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 4<span class="delete">6</span></td><td> </td><td class="rblock">       5.7.1.  Via  . . . . . . . . . . . . . . . . . . . . . . . . . 4<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    116173      <tr><td class="lineno" valign="top"></td><td class="left">       5.7.2.  Transformations  . . . . . . . . . . . . . . . . . . . 48</td><td> </td><td class="right">       5.7.2.  Transformations  . . . . . . . . . . . . . . . . . . . 48</td><td class="lineno" valign="top"></td></tr>
    117174      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Connection Management  . . . . . . . . . . . . . . . . . . . . 49</td><td> </td><td class="right">   6.  Connection Management  . . . . . . . . . . . . . . . . . . . . 49</td><td class="lineno" valign="top"></td></tr>
    118175      <tr><td class="lineno" valign="top"></td><td class="left">     6.1.  Connection . . . . . . . . . . . . . . . . . . . . . . . . 50</td><td> </td><td class="right">     6.1.  Connection . . . . . . . . . . . . . . . . . . . . . . . . 50</td><td class="lineno" valign="top"></td></tr>
    119176      <tr><td class="lineno" valign="top"></td><td class="left">     6.2.  Establishment  . . . . . . . . . . . . . . . . . . . . . . 51</td><td> </td><td class="right">     6.2.  Establishment  . . . . . . . . . . . . . . . . . . . . . . 51</td><td class="lineno" valign="top"></td></tr>
    120       <tr><td class="lineno" valign="top"></td><td class="left">     6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 52</td><td> </td><td class="right">     6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . 52</td><td class="lineno" valign="top"></td></tr>
    121       <tr><td class="lineno" valign="top"></td><td class="left">       6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 53</td><td> </td><td class="right">       6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . 53</td><td class="lineno" valign="top"></td></tr>
     177      <tr><td><a name="diff0016" /></td></tr>
     178      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">51</span></td><td> </td><td class="rblock">     6.3.  Persistence  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">52</span></td><td class="lineno" valign="top"></td></tr>
     179      <tr><td class="lineno" valign="top"></td><td class="lblock">       6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . <span class="delete">52</span></td><td> </td><td class="rblock">       6.3.1.  Retrying Requests  . . . . . . . . . . . . . . . . . . <span class="insert">53</span></td><td class="lineno" valign="top"></td></tr>
    122180      <tr><td class="lineno" valign="top"></td><td class="left">       6.3.2.  Pipelining . . . . . . . . . . . . . . . . . . . . . . 53</td><td> </td><td class="right">       6.3.2.  Pipelining . . . . . . . . . . . . . . . . . . . . . . 53</td><td class="lineno" valign="top"></td></tr>
    123       <tr><td><a name="diff0008" /></td></tr>
     181      <tr><td><a name="diff0017" /></td></tr>
    124182      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    125183      <tr><td class="lineno" valign="top"></td><td class="left">     6.4.  Concurrency  . . . . . . . . . . . . . . . . . . . . . . . 54</td><td> </td><td class="right">     6.4.  Concurrency  . . . . . . . . . . . . . . . . . . . . . . . 54</td><td class="lineno" valign="top"></td></tr>
    126184      <tr><td class="lineno" valign="top"></td><td class="left">     6.5.  Failures and Timeouts  . . . . . . . . . . . . . . . . . . 54</td><td> </td><td class="right">     6.5.  Failures and Timeouts  . . . . . . . . . . . . . . . . . . 54</td><td class="lineno" valign="top"></td></tr>
    127       <tr><td><a name="diff0009" /></td></tr>
     185      <tr><td><a name="diff0018" /></td></tr>
    128186      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.6.  Tear<span class="delete">-down </span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td> </td><td class="rblock">     6.6.  Tear<span class="insert">down .</span> . . . . . . . . . . . . . . . . . . . . . . . . 55</td><td class="lineno" valign="top"></td></tr>
    129187      <tr><td class="lineno" valign="top"></td><td class="left">     6.7.  Upgrade  . . . . . . . . . . . . . . . . . . . . . . . . . 56</td><td> </td><td class="right">     6.7.  Upgrade  . . . . . . . . . . . . . . . . . . . . . . . . . 56</td><td class="lineno" valign="top"></td></tr>
    130188      <tr><td class="lineno" valign="top"></td><td class="left">   7.  ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58</td><td> </td><td class="right">   7.  ABNF List Extension: #rule . . . . . . . . . . . . . . . . . . 58</td><td class="lineno" valign="top"></td></tr>
    131       <tr><td class="lineno" valign="top"></td><td class="left">   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 60</td><td> </td><td class="right">   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 60</td><td class="lineno" valign="top"></td></tr>
    132       <tr><td class="lineno" valign="top"></td><td class="left">     8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 60</td><td> </td><td class="right">     8.1.  Header Field Registration  . . . . . . . . . . . . . . . . 60</td><td class="lineno" valign="top"></td></tr>
     189      <tr><td><a name="diff0019" /></td></tr>
     190      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">59</span></td><td> </td><td class="rblock">   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="insert">60</span></td><td class="lineno" valign="top"></td></tr>
     191      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Header Field Registration  . . . . . . . . . . . . . . . . <span class="delete">59</span></td><td> </td><td class="rblock">     8.1.  Header Field Registration  . . . . . . . . . . . . . . . . <span class="insert">60</span></td><td class="lineno" valign="top"></td></tr>
    133192      <tr><td class="lineno" valign="top"></td><td class="left">     8.2.  URI Scheme Registration  . . . . . . . . . . . . . . . . . 60</td><td> </td><td class="right">     8.2.  URI Scheme Registration  . . . . . . . . . . . . . . . . . 60</td><td class="lineno" valign="top"></td></tr>
    134       <tr><td class="lineno" valign="top"></td><td class="left">     8.3.  Internet Media Type Registration . . . . . . . . . . . . . 61</td><td> </td><td class="right">     8.3.  Internet Media Type Registration . . . . . . . . . . . . . 61</td><td class="lineno" valign="top"></td></tr>
     193      <tr><td><a name="diff0020" /></td></tr>
     194      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.3.  Internet Media Type Registration . . . . . . . . . . . . . 6<span class="delete">0</span></td><td> </td><td class="rblock">     8.3.  Internet Media Type Registration . . . . . . . . . . . . . 6<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
    135195      <tr><td class="lineno" valign="top"></td><td class="left">       8.3.1.  Internet Media Type message/http . . . . . . . . . . . 61</td><td> </td><td class="right">       8.3.1.  Internet Media Type message/http . . . . . . . . . . . 61</td><td class="lineno" valign="top"></td></tr>
    136196      <tr><td class="lineno" valign="top"></td><td class="left">       8.3.2.  Internet Media Type application/http . . . . . . . . . 62</td><td> </td><td class="right">       8.3.2.  Internet Media Type application/http . . . . . . . . . 62</td><td class="lineno" valign="top"></td></tr>
    137197      <tr><td class="lineno" valign="top"></td><td class="left">     8.4.  Transfer Coding Registry . . . . . . . . . . . . . . . . . 63</td><td> </td><td class="right">     8.4.  Transfer Coding Registry . . . . . . . . . . . . . . . . . 63</td><td class="lineno" valign="top"></td></tr>
    138198      <tr><td class="lineno" valign="top"></td><td class="left">       8.4.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 63</td><td> </td><td class="right">       8.4.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 63</td><td class="lineno" valign="top"></td></tr>
    139       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    140       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 4, line 37</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 4, line 16</em></th><td></td></tr>
     199      <tr><td class="lineno" valign="top"></td><td class="left">       8.4.2.  Registration . . . . . . . . . . . . . . . . . . . . . 64</td><td> </td><td class="right">       8.4.2.  Registration . . . . . . . . . . . . . . . . . . . . . 64</td><td class="lineno" valign="top"></td></tr>
     200      <tr><td class="lineno" valign="top"></td><td class="left">     8.5.  Content Coding Registration  . . . . . . . . . . . . . . . 64</td><td> </td><td class="right">     8.5.  Content Coding Registration  . . . . . . . . . . . . . . . 64</td><td class="lineno" valign="top"></td></tr>
     201      <tr><td><a name="diff0021" /></td></tr>
     202      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 6<span class="delete">4</span></td><td> </td><td class="rblock">     8.6.  Upgrade Token Registry . . . . . . . . . . . . . . . . . . 6<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
     203      <tr><td class="lineno" valign="top"></td><td class="left">       8.6.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 65</td><td> </td><td class="right">       8.6.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 65</td><td class="lineno" valign="top"></td></tr>
     204      <tr><td><a name="diff0022" /></td></tr>
     205      <tr><td class="lineno" valign="top"></td><td class="lblock">       8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 6<span class="delete">5</span></td><td> </td><td class="rblock">       8.6.2.  Upgrade Token Registration . . . . . . . . . . . . . . 6<span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
     206      <tr><td class="lineno" valign="top"></td><td class="left">   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 66</td><td> </td><td class="right">   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 66</td><td class="lineno" valign="top"></td></tr>
     207      <tr><td class="lineno" valign="top"></td><td class="left">     9.1.  Establishing Authority . . . . . . . . . . . . . . . . . . 66</td><td> </td><td class="right">     9.1.  Establishing Authority . . . . . . . . . . . . . . . . . . 66</td><td class="lineno" valign="top"></td></tr>
     208      <tr><td class="lineno" valign="top"></td><td class="left">     9.2.  Risks of Intermediaries  . . . . . . . . . . . . . . . . . 67</td><td> </td><td class="right">     9.2.  Risks of Intermediaries  . . . . . . . . . . . . . . . . . 67</td><td class="lineno" valign="top"></td></tr>
     209      <tr><td><a name="diff0023" /></td></tr>
     210      <tr><td class="lineno" valign="top"></td><td class="lblock">     9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 6<span class="delete">7</span></td><td> </td><td class="rblock">     9.3.  Attacks via Protocol Element Length  . . . . . . . . . . . 6<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    141211      <tr><td class="lineno" valign="top"></td><td class="left">     9.4.  Response Splitting . . . . . . . . . . . . . . . . . . . . 68</td><td> </td><td class="right">     9.4.  Response Splitting . . . . . . . . . . . . . . . . . . . . 68</td><td class="lineno" valign="top"></td></tr>
    142212      <tr><td class="lineno" valign="top"></td><td class="left">     9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69</td><td> </td><td class="right">     9.5.  Request Smuggling  . . . . . . . . . . . . . . . . . . . . 69</td><td class="lineno" valign="top"></td></tr>
    143213      <tr><td class="lineno" valign="top"></td><td class="left">     9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69</td><td> </td><td class="right">     9.6.  Message Integrity  . . . . . . . . . . . . . . . . . . . . 69</td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="left">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 70</td><td> </td><td class="right">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . 70</td><td class="lineno" valign="top"></td></tr>
     214      <tr><td><a name="diff0024" /></td></tr>
     215      <tr><td class="lineno" valign="top"></td><td class="lblock">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . <span class="delete">69</span></td><td> </td><td class="rblock">     9.7.  Message Confidentiality  . . . . . . . . . . . . . . . . . <span class="insert">70</span></td><td class="lineno" valign="top"></td></tr>
    145216      <tr><td class="lineno" valign="top"></td><td class="left">     9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70</td><td> </td><td class="right">     9.8.  Privacy of Server Log Information  . . . . . . . . . . . . 70</td><td class="lineno" valign="top"></td></tr>
    146       <tr><td class="lineno" valign="top"></td><td class="left">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 71</td><td> </td><td class="right">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 71</td><td class="lineno" valign="top"></td></tr>
     217      <tr><td><a name="diff0025" /></td></tr>
     218      <tr><td class="lineno" valign="top"></td><td class="lblock">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 7<span class="delete">0</span></td><td> </td><td class="rblock">   10. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 7<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
    147219      <tr><td class="lineno" valign="top"></td><td class="left">   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72</td><td> </td><td class="right">   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 72</td><td class="lineno" valign="top"></td></tr>
    148220      <tr><td class="lineno" valign="top"></td><td class="left">     11.1. Normative References . . . . . . . . . . . . . . . . . . . 72</td><td> </td><td class="right">     11.1. Normative References . . . . . . . . . . . . . . . . . . . 72</td><td class="lineno" valign="top"></td></tr>
    149       <tr><td class="lineno" valign="top"></td><td class="left">     11.2. Informative References . . . . . . . . . . . . . . . . . . 74</td><td> </td><td class="right">     11.2. Informative References . . . . . . . . . . . . . . . . . . 74</td><td class="lineno" valign="top"></td></tr>
    150       <tr><td class="lineno" valign="top"></td><td class="left">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 76</td><td> </td><td class="right">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . 76</td><td class="lineno" valign="top"></td></tr>
    151       <tr><td><a name="diff0010" /></td></tr>
    152       <tr><td class="lineno" valign="top"></td><td class="lblock">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
    153       <tr><td class="lineno" valign="top"></td><td class="lblock">       A.1.1.  <span class="delete">Multi-homed</span> Web Servers  . . . . . . . . . . . . . . . 77</td><td> </td><td class="rblock">       A.1.1.  <span class="insert">Multihomed</span> Web Servers <span class="insert">.</span> . . . . . . . . . . . . . . . 77</td><td class="lineno" valign="top"></td></tr>
     221      <tr><td><a name="diff0026" /></td></tr>
     222      <tr><td class="lineno" valign="top"></td><td class="lblock">     11.2. Informative References . . . . . . . . . . . . . . . . . . <span class="delete">73</span></td><td> </td><td class="rblock">     11.2. Informative References . . . . . . . . . . . . . . . . . . <span class="insert">74</span></td><td class="lineno" valign="top"></td></tr>
     223      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . <span class="delete">75</span></td><td> </td><td class="rblock">   Appendix A.  HTTP Version History  . . . . . . . . . . . . . . . . <span class="insert">76</span></td><td class="lineno" valign="top"></td></tr>
     224      <tr><td class="lineno" valign="top"></td><td class="left">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76</td><td> </td><td class="right">     A.1.  Changes from HTTP/1.0  . . . . . . . . . . . . . . . . . . 76</td><td class="lineno" valign="top"></td></tr>
     225      <tr><td><a name="diff0027" /></td></tr>
     226      <tr><td class="lineno" valign="top"></td><td class="lblock">       A.1.1.  Multi<span class="delete">-homed Web Servers  . . . . . . . . . . . . . . . 76</span></td><td> </td><td class="rblock">       A.1.1.  Multi<span class="insert">homed Web Servers . . . . . . . . . . . . . . . . 77</span></td><td class="lineno" valign="top"></td></tr>
    154227      <tr><td class="lineno" valign="top"></td><td class="left">       A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . 77</td><td> </td><td class="right">       A.1.2.  Keep-Alive Connections . . . . . . . . . . . . . . . . 77</td><td class="lineno" valign="top"></td></tr>
    155       <tr><td class="lineno" valign="top"></td><td class="left">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 78</td><td> </td><td class="right">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . 78</td><td class="lineno" valign="top"></td></tr>
    156       <tr><td class="lineno" valign="top"></td><td class="left">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 78</td><td> </td><td class="right">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . 78</td><td class="lineno" valign="top"></td></tr>
     228      <tr><td><a name="diff0028" /></td></tr>
     229      <tr><td class="lineno" valign="top"></td><td class="lblock">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">       A.1.3.  Introduction of Transfer-Encoding  . . . . . . . . . . <span class="insert">78</span></td><td class="lineno" valign="top"></td></tr>
     230      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . <span class="delete">77</span></td><td> </td><td class="rblock">     A.2.  Changes from RFC 2616  . . . . . . . . . . . . . . . . . . <span class="insert">78</span></td><td class="lineno" valign="top"></td></tr>
    157231      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 80</td><td> </td><td class="right">   Appendix B.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 80</td><td class="lineno" valign="top"></td></tr>
    158232      <tr><td class="lineno" valign="top"></td><td class="left">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82</td><td> </td><td class="right">   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82</td><td class="lineno" valign="top"></td></tr>
     
    162236      <tr><td class="lineno" valign="top"></td><td class="left">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td> </td><td class="right">   The Hypertext Transfer Protocol (HTTP) is a stateless application-</td><td class="lineno" valign="top"></td></tr>
    163237      <tr><td class="lineno" valign="top"></td><td class="left">   level request/response protocol that uses extensible semantics and</td><td> </td><td class="right">   level request/response protocol that uses extensible semantics and</td><td class="lineno" valign="top"></td></tr>
    164       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    165       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 5, line 26</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 26</em></th><td></td></tr>
     238      <tr><td class="lineno" valign="top"></td><td class="left">   self-descriptive message payloads for flexible interaction with</td><td> </td><td class="right">   self-descriptive message payloads for flexible interaction with</td><td class="lineno" valign="top"></td></tr>
     239      <tr><td class="lineno" valign="top"></td><td class="left">   network-based hypertext information systems.  This document is the</td><td> </td><td class="right">   network-based hypertext information systems.  This document is the</td><td class="lineno" valign="top"></td></tr>
     240      <tr><td class="lineno" valign="top"></td><td class="left">   first in a series of documents that collectively form the HTTP/1.1</td><td> </td><td class="right">   first in a series of documents that collectively form the HTTP/1.1</td><td class="lineno" valign="top"></td></tr>
     241      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     242      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 5, line 26</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 5, line 26</em></th><td></td></tr>
    166243      <tr><td class="lineno" valign="top"></td><td class="left">      RFC 7231: Semantics and Content</td><td> </td><td class="right">      RFC 7231: Semantics and Content</td><td class="lineno" valign="top"></td></tr>
    167244      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    174251      <tr><td class="lineno" valign="top"></td><td class="left">      RFC 7235: Authentication</td><td> </td><td class="right">      RFC 7235: Authentication</td><td class="lineno" valign="top"></td></tr>
    175252      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    176       <tr><td><a name="diff0011" /></td></tr>
     253      <tr><td><a name="diff0029" /></td></tr>
    177254      <tr><td class="lineno" valign="top"></td><td class="lblock">   This HTTP/1.1 specification obsoletes <span class="delete">RFC 2616</span> and <span class="delete">RFC 2145</span> (on HTTP</td><td> </td><td class="rblock">   This HTTP/1.1 specification obsoletes <span class="insert">[RFC2616]</span> and <span class="insert">[RFC2145]</span> (on</td><td class="lineno" valign="top"></td></tr>
    178255      <tr><td class="lineno" valign="top"></td><td class="lblock">   versioning).  This specification also updates the use of <span class="delete">CONNECT to</span></td><td> </td><td class="rblock">   HTTP versioning).  This specification also updates the use of</td><td class="lineno" valign="top"></td></tr>
     
    191268      <tr><td class="lineno" valign="top"></td><td class="left">   for which implementations can evolve independently over time.</td><td> </td><td class="right">   for which implementations can evolve independently over time.</td><td class="lineno" valign="top"></td></tr>
    192269      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    193       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 10, line 36</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 10, line 39</em></th><td></td></tr>
     270      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 10, line 36</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 10, line 39</em></th><td></td></tr>
    194271      <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>
    195272      <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>
     
    202279      <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>
    203280      <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>
    204       <tr><td><a name="diff0012" /></td></tr>
     281      <tr><td><a name="diff0030" /></td></tr>
    205282      <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>
    206283      <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>
     
    215292      <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>
    216293      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    217       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr>
     294      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 13, line 49</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 14, line 4</em></th><td></td></tr>
    218295      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    219296      <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>
     
    226303      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    227304      <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>
    228       <tr><td><a name="diff0013" /></td></tr>
     305      <tr><td><a name="diff0031" /></td></tr>
    229306      <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>
    230307      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    231308      <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>
    232       <tr><td><a name="diff0014" /></td></tr>
     309      <tr><td><a name="diff0032" /></td></tr>
    233310      <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>
    234311      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    243320      <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>
    244321      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    245       <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr>
     322      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 14, line 36</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 39</em></th><td></td></tr>
    246323      <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>
    247324      <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>
     
    254331      <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>
    255332      <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>
    256       <tr><td><a name="diff0015" /></td></tr>
     333      <tr><td><a name="diff0033" /></td></tr>
    257334      <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>
    258335      <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>
     
    267344      <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>
    268345      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    269       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr>
     346      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 15, line 48</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 15, line 51</em></th><td></td></tr>
    270347      <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>
    271348      <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>
     
    278355      <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>
    279356      <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>
    280       <tr><td><a name="diff0016" /></td></tr>
     357      <tr><td><a name="diff0034" /></td></tr>
    281358      <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>
    282359      <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>
     
    290367      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    291368      <tr><td class="lineno" valign="top"></td><td class="left">   The definitions of "URI-reference", "absolute-URI", "relative-part",</td><td> </td><td class="right">   The definitions of "URI-reference", "absolute-URI", "relative-part",</td><td class="lineno" valign="top"></td></tr>
    292       <tr><td class="lineno" valign="top"></td><td class="left">   "scheme", "authority", "port", "host", "path-abempty", "segment",</td><td> </td><td class="right">   "scheme", "authority", "port", "host", "path-abempty", "segment",</td><td class="lineno" valign="top"></td></tr>
    293       <tr><td class="lineno" valign="top"></td><td class="left">   "query", and "fragment" are adopted from the URI generic syntax.  An</td><td> </td><td class="right">   "query", and "fragment" are adopted from the URI generic syntax.  An</td><td class="lineno" valign="top"></td></tr>
    294       <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>
    295       <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>
    296       <tr><td><a name="diff0017" /></td></tr>
    297       <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>
    298       <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>
    299       <tr><td class="lineno" valign="top"></td><td class="left">   paths that begin with "//".)  A "partial-URI" rule is defined for</td><td> </td><td class="right">   paths that begin with "//".)  A "partial-URI" rule is defined for</td><td class="lineno" valign="top"></td></tr>
    300       <tr><td class="lineno" valign="top"></td><td class="left">   protocol elements that can contain a relative URI but not a fragment</td><td> </td><td class="right">   protocol elements that can contain a relative URI but not a fragment</td><td class="lineno" valign="top"></td></tr>
    301       <tr><td class="lineno" valign="top"></td><td class="left">   component.</td><td> </td><td class="right">   component.</td><td class="lineno" valign="top"></td></tr>
    302       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    303       <tr><td class="lineno" valign="top"></td><td class="left">     URI-reference = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;</td><td> </td><td class="right">     URI-reference = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;</td><td class="lineno" valign="top"></td></tr>
    304       <tr><td class="lineno" valign="top"></td><td class="left">     absolute-URI  = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;</td><td> </td><td class="right">     absolute-URI  = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;</td><td class="lineno" valign="top"></td></tr>
    305       <tr><td class="lineno" valign="top"></td><td class="left">     relative-part = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;</td><td> </td><td class="right">     relative-part = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;</td><td class="lineno" valign="top"></td></tr>
    306       <tr><td class="lineno" valign="top"></td><td class="left">     scheme        = &lt;scheme, defined in [RFC3986], Section 3.1&gt;</td><td> </td><td class="right">     scheme        = &lt;scheme, defined in [RFC3986], Section 3.1&gt;</td><td class="lineno" valign="top"></td></tr>
    307       <tr><td class="lineno" valign="top"></td><td class="left">     authority     = &lt;authority, defined in [RFC3986], Section 3.2&gt;</td><td> </td><td class="right">     authority     = &lt;authority, defined in [RFC3986], Section 3.2&gt;</td><td class="lineno" valign="top"></td></tr>
    308       <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>
    309       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    310       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>
     369      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     370      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 16, line 50</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 16, line 50</em></th><td></td></tr>
    311371      <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>
    312372      <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>
     
    319379      <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>
    320380      <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>
    321       <tr><td><a name="diff0018" /></td></tr>
     381      <tr><td><a name="diff0035" /></td></tr>
    322382      <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>
    323383      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    332392      <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>
    333393      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    334       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr>
     394      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 19, line 18</em></th><td></td></tr>
    335395      <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>
    336396      <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>
     
    343403      <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>
    344404      <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>
    345       <tr><td><a name="diff0019" /></td></tr>
     405      <tr><td><a name="diff0036" /></td></tr>
    346406      <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>
    347407      <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>
     
    356416      <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>
    357417      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    358       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 20, line 45</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 20, line 45</em></th><td></td></tr>
     418      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 20, line 45</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 20, line 45</em></th><td></td></tr>
    359419      <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>
    360420      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    367427      <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>
    368428      <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>
    369       <tr><td><a name="diff0020" /></td></tr>
     429      <tr><td><a name="diff0037" /></td></tr>
    370430      <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>
    371431      <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>
     
    376436      <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>
    377437      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    378       <tr><td><a name="diff0021" /></td></tr>
     438      <tr><td><a name="diff0038" /></td></tr>
    379439      <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>
    380440      <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>
    381       <tr><td class="lineno" valign="top"></td><td class="lblock">   version, and <span class="delete">ending</span> with CRLF.</td><td> </td><td class="rblock">   protocol version, and <span class="insert">ends</span> with CRLF.</td><td class="lineno" valign="top"></td></tr>
     441      <tr><td class="lineno" valign="top"></td><td class="lblock">   version, and ends with CRLF.</td><td> </td><td class="rblock">   protocol version, and ends with CRLF.</td><td class="lineno" valign="top"></td></tr>
    382442      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    383443      <tr><td class="lineno" valign="top"></td><td class="left">     request-line   = method SP request-target SP HTTP-version CRLF</td><td> </td><td class="right">     request-line   = method SP request-target SP HTTP-version CRLF</td><td class="lineno" valign="top"></td></tr>
    384444      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    385445      <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>
    386       <tr><td><a name="diff0022" /></td></tr>
     446      <tr><td><a name="diff0039" /></td></tr>
    387447      <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>
    388448      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    397457      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    398458      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    399       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 22, line 8</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 22, line 8</em></th><td></td></tr>
     459      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 22, line 8</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 22, line 8</em></th><td></td></tr>
    400460      <tr><td class="lineno" valign="top"></td><td class="left">   longer than any URI it wishes to parse MUST respond with a 414 (URI</td><td> </td><td class="right">   longer than any URI it wishes to parse MUST respond with a 414 (URI</td><td class="lineno" valign="top"></td></tr>
    401461      <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>
     
    408468      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    409469      <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>
    410       <tr><td><a name="diff0023" /></td></tr>
     470      <tr><td><a name="diff0040" /></td></tr>
    411471      <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>
    412472      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">space,</span> a possibly empty textual phrase describing the status code,</td><td> </td><td class="rblock"><span class="insert">   (SP),</span> a possibly empty textual phrase describing the status code,</td><td class="lineno" valign="top"></td></tr>
     
    423483      <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>
    424484      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    425       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>
     485      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 23, line 29</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 23, line 29</em></th><td></td></tr>
    426486      <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>
    427487      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    434494      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    435495      <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>
    436       <tr><td><a name="diff0024" /></td></tr>
    437       <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>
    438       <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>
     496      <tr><td><a name="diff0041" /></td></tr>
     497      <tr><td class="lineno" valign="top"></td><td class="lblock">   "Message Headers" registry, as described in Section 8.3 of [RFC7231].</td><td> </td><td class="rblock">   "Message Headers" <span class="insert">field</span> registry, as described in Section 8.3 of</td><td class="lineno" valign="top"></td></tr>
     498      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   [RFC7231].</td><td class="lineno" valign="top"></td></tr>
    439499      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    440500      <tr><td class="lineno" valign="top"></td><td class="left">3.2.2.  Field Order</td><td> </td><td class="right">3.2.2.  Field Order</td><td class="lineno" valign="top"></td></tr>
     
    446506      <tr><td class="lineno" valign="top"></td><td class="left">   when not to handle a message as early as possible.  A server MUST NOT</td><td> </td><td class="right">   when not to handle a message as early as possible.  A server MUST NOT</td><td class="lineno" valign="top"></td></tr>
    447507      <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>
    448       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    449       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 24, line 14</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>
     508      <tr><td class="lineno" valign="top"></td><td class="left">   header section is received, since later header fields might include</td><td> </td><td class="right">   header section is received, since later header fields might include</td><td class="lineno" valign="top"></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-l13" /><small>skipping to change at</small><em> page 24, line 13</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 24, line 14</em></th><td></td></tr>
    450511      <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>
    451512      <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>
     
    458519      <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>
    459520      <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>
    460       <tr><td><a name="diff0025" /></td></tr>
     521      <tr><td><a name="diff0042" /></td></tr>
    461522      <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>
    462523      <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>
     
    471532      <tr><td class="lineno" valign="top"></td><td class="left">   The OWS rule is used where zero or more linear whitespace octets</td><td> </td><td class="right">   The OWS rule is used where zero or more linear whitespace octets</td><td class="lineno" valign="top"></td></tr>
    472533      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    473       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 25, line 12</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>
     534      <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 25, line 6</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 25, line 12</em></th><td></td></tr>
    474535      <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>
    475536      <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>
     
    482543      <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>
    483544      <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>
    484       <tr><td><a name="diff0026" /></td></tr>
     545      <tr><td><a name="diff0043" /></td></tr>
    485546      <tr><td class="lineno" valign="top"></td><td class="lblock">   to define each "<span class="delete">Field-Name: Field V</span>alue" pair, as was done in</td><td> </td><td class="rblock">   to define each "<span class="insert">field-name: field-v</span>alue" pair, as was done in</td><td class="lineno" valign="top"></td></tr>
    486547      <tr><td class="lineno" valign="top"></td><td class="left">   previous editions.  Instead, this specification uses ABNF rules that</td><td> </td><td class="right">   previous editions.  Instead, this specification uses ABNF rules that</td><td class="lineno" valign="top"></td></tr>
     
    495556      <tr><td class="lineno" valign="top"></td><td class="left">   server MUST reject any received request message that contains</td><td> </td><td class="right">   server MUST reject any received request message that contains</td><td class="lineno" valign="top"></td></tr>
    496557      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    497       <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 26, line 16</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 26, line 16</em></th><td></td></tr>
     558      <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 26, line 11</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 26, line 16</em></th><td></td></tr>
    498559      <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>
    499560      <tr><td class="lineno" valign="top"></td><td class="left">   octets prior to interpreting the field value or forwarding the</td><td> </td><td class="right">   octets prior to interpreting the field value or forwarding the</td><td class="lineno" valign="top"></td></tr>
     
    506567      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    507568      <tr><td class="lineno" valign="top"></td><td class="left">   Historically, HTTP has allowed field content with text in the</td><td> </td><td class="right">   Historically, HTTP has allowed field content with text in the</td><td class="lineno" valign="top"></td></tr>
    508       <tr><td><a name="diff0027" /></td></tr>
     569      <tr><td><a name="diff0044" /></td></tr>
    509570      <tr><td class="lineno" valign="top"></td><td class="lblock">   ISO-8859-1 <span class="delete">charset [ISO-8859-1]</span>, supporting other charsets only</td><td> </td><td class="rblock">   ISO-8859-1 <span class="insert">[ISO-8859-1] charset</span>, supporting other charsets only</td><td class="lineno" valign="top"></td></tr>
    510571      <tr><td class="lineno" valign="top"></td><td class="left">   through use of [RFC2047] encoding.  In practice, most HTTP header</td><td> </td><td class="right">   through use of [RFC2047] encoding.  In practice, most HTTP header</td><td class="lineno" valign="top"></td></tr>
     
    519580      <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>
    520581      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    521       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 35, line 26</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>
     582      <tr bgcolor="gray" ><td></td><th><a name="part-l16" /><small>skipping to change at</small><em> page 35, line 16</em></th><th> </th><th><a name="part-r16" /><small>skipping to change at</small><em> page 35, line 26</em></th><td></td></tr>
    522583      <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>
    523584      <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>
     
    530591      <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>
    531592      <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><a name="diff0028" /></td></tr>
     593      <tr><td><a name="diff0045" /></td></tr>
    533594      <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>
    534595      <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>
     
    544605      <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>
    545606      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    546       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 49, line 29</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>
     607      <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 49, line 18</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 49, line 29</em></th><td></td></tr>
    547608      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    548609      <tr><td class="lineno" valign="top"></td><td class="left">   A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td> </td><td class="right">   A proxy MUST NOT modify the "absolute-path" and "query" parts of the</td><td class="lineno" valign="top"></td></tr>
     
    555616      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    556617      <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>
    557       <tr><td><a name="diff0029" /></td></tr>
     618      <tr><td><a name="diff0046" /></td></tr>
    558619      <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>
    559620      <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>
    560621      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    561622      <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>
    562       <tr><td><a name="diff0030" /></td></tr>
     623      <tr><td><a name="diff0047" /></td></tr>
    563624      <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>
    564625      <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>
     
    573634      <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>
    574635      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    575       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 51, line 8</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr>
     636      <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 50, line 46</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 51, line 8</em></th><td></td></tr>
    576637      <tr><td class="lineno" valign="top"></td><td class="left">   recipients on the chain ("end-to-end"), enabling the message to be</td><td> </td><td class="right">   recipients on the chain ("end-to-end"), enabling the message to be</td><td class="lineno" valign="top"></td></tr>
    577638      <tr><td class="lineno" valign="top"></td><td class="left">   self-descriptive and allowing future connection-specific extensions</td><td> </td><td class="right">   self-descriptive and allowing future connection-specific extensions</td><td class="lineno" valign="top"></td></tr>
     
    584645      <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>
    585646      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    586       <tr><td><a name="diff0031" /></td></tr>
     647      <tr><td><a name="diff0048" /></td></tr>
    587648      <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>
    588649      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    597658      <tr><td class="lineno" valign="top"></td><td class="left">   connection option.  In contrast, a connection-specific header field</td><td> </td><td class="right">   connection option.  In contrast, a connection-specific header field</td><td class="lineno" valign="top"></td></tr>
    598659      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    599       <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 55, line 31</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 55, line 31</em></th><td></td></tr>
     660      <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 55, line 18</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 55, line 31</em></th><td></td></tr>
    600661      <tr><td class="lineno" valign="top"></td><td class="left">   expectation that clients will retry.  The latter technique can</td><td> </td><td class="right">   expectation that clients will retry.  The latter technique can</td><td class="lineno" valign="top"></td></tr>
    601662      <tr><td class="lineno" valign="top"></td><td class="left">   exacerbate network congestion.</td><td> </td><td class="right">   exacerbate network congestion.</td><td class="lineno" valign="top"></td></tr>
     
    608669      <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>
    609670      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    610       <tr><td><a name="diff0032" /></td></tr>
     671      <tr><td><a name="diff0049" /></td></tr>
    611672      <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>
    612673      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    616677      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    617678      <tr><td class="lineno" valign="top"></td><td class="left">   A client that sends a "close" connection option MUST NOT send further</td><td> </td><td class="right">   A client that sends a "close" connection option MUST NOT send further</td><td class="lineno" valign="top"></td></tr>
    618       <tr><td><a name="diff0033" /></td></tr>
     679      <tr><td><a name="diff0050" /></td></tr>
    619680      <tr><td class="lineno" valign="top"></td><td class="lblock">   requests on that connection (after the one containing <span class="delete">"close")</span> and</td><td> </td><td class="rblock">   requests on that connection (after the one containing <span class="insert">close)</span> and MUST</td><td class="lineno" valign="top"></td></tr>
    620681      <tr><td class="lineno" valign="top"></td><td class="lblock">   MUST close the connection after reading the final response message</td><td> </td><td class="rblock">   close the connection after reading the final response message</td><td class="lineno" valign="top"></td></tr>
     
    623684      <tr><td class="lineno" valign="top"></td><td class="left">   A server that receives a "close" connection option MUST initiate a</td><td> </td><td class="right">   A server that receives a "close" connection option MUST initiate a</td><td class="lineno" valign="top"></td></tr>
    624685      <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>
    625       <tr><td><a name="diff0034" /></td></tr>
     686      <tr><td><a name="diff0051" /></td></tr>
    626687      <tr><td class="lineno" valign="top"></td><td class="lblock">   to the request that contained <span class="delete">"close".</span>  The server SHOULD send a</td><td> </td><td class="rblock">   to the request that contained <span class="insert">close.</span>  The server SHOULD send a <span class="insert">close</span></td><td class="lineno" valign="top"></td></tr>
    627688      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">"close"</span> connection option in its final response on that connection.</td><td> </td><td class="rblock">   connection option in its final response on that connection.  The</td><td class="lineno" valign="top"></td></tr>
     
    631692      <tr><td class="lineno" valign="top"></td><td class="left">   A server that sends a "close" connection option MUST initiate a close</td><td> </td><td class="right">   A server that sends a "close" connection option MUST initiate a close</td><td class="lineno" valign="top"></td></tr>
    632693      <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>
    633       <tr><td><a name="diff0035" /></td></tr>
     694      <tr><td><a name="diff0052" /></td></tr>
    634695      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">"close".</span>  The server MUST NOT process any further requests received</td><td> </td><td class="rblock">   <span class="insert">close.</span>  The server MUST NOT process any further requests received on</td><td class="lineno" valign="top"></td></tr>
    635696      <tr><td class="lineno" valign="top"></td><td class="lblock">   on that connection.</td><td> </td><td class="rblock">   that connection.</td><td class="lineno" valign="top"></td></tr>
     
    637698      <tr><td class="lineno" valign="top"></td><td class="left">   A client that receives a "close" connection option MUST cease sending</td><td> </td><td class="right">   A client that receives a "close" connection option MUST cease sending</td><td class="lineno" valign="top"></td></tr>
    638699      <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>
    639       <tr><td><a name="diff0036" /></td></tr>
     700      <tr><td><a name="diff0053" /></td></tr>
    640701      <tr><td class="lineno" valign="top"></td><td class="lblock">   the response message containing the <span class="delete">"close"</span>; if additional pipelined</td><td> </td><td class="rblock">   the response message containing the <span class="insert">close</span>; if additional pipelined</td><td class="lineno" valign="top"></td></tr>
    641702      <tr><td class="lineno" valign="top"></td><td class="left">   requests had been sent on the connection, the client SHOULD NOT</td><td> </td><td class="right">   requests had been sent on the connection, the client SHOULD NOT</td><td class="lineno" valign="top"></td></tr>
     
    650711      <tr><td class="lineno" valign="top"></td><td class="left">   unfortunately, the reset packet might erase the client's</td><td> </td><td class="right">   unfortunately, the reset packet might erase the client's</td><td class="lineno" valign="top"></td></tr>
    651712      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    652       <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 59, line 35</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr>
     713      <tr bgcolor="gray" ><td></td><th><a name="part-l20" /><small>skipping to change at</small><em> page 59, line 19</em></th><th> </th><th><a name="part-r20" /><small>skipping to change at</small><em> page 59, line 35</em></th><td></td></tr>
    653714      <tr><td class="lineno" valign="top"></td><td class="left">     #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]</td><td> </td><td class="right">     #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]</td><td class="lineno" valign="top"></td></tr>
    654715      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    661722      <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>
    662723      <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><a name="diff0037" /></td></tr>
     724      <tr><td><a name="diff0054" /></td></tr>
    664725      <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>
    665726      <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>
     
    683744      <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>
    684745      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    685       <tr><td><a name="diff0038" /></td></tr>
     746      <tr><td><a name="diff0055" /></td></tr>
    686747      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP header fields are registered within the "Message Header<span class="delete">s"</span></td><td> </td><td class="rblock">   HTTP header fields are registered within the "Message Header<span class="insert">" field</span></td><td class="lineno" valign="top"></td></tr>
    687748      <tr><td class="lineno" valign="top"></td><td class="left">   registry maintained at</td><td> </td><td class="right">   registry maintained at</td><td class="lineno" valign="top"></td></tr>
     
    696757      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+---------------+</td><td> </td><td class="right">   +-------------------+----------+----------+---------------+</td><td class="lineno" valign="top"></td></tr>
    697758      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    698       <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 62, line 21</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 62, line 21</em></th><td></td></tr>
     759      <tr bgcolor="gray" ><td></td><th><a name="part-l21" /><small>skipping to change at</small><em> page 62, line 4</em></th><th> </th><th><a name="part-r21" /><small>skipping to change at</small><em> page 62, line 17</em></th><td></td></tr>
     760      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     761      <tr><td class="lineno" valign="top"></td><td class="left">   Fragment identifier considerations:  N/A</td><td> </td><td class="right">   Fragment identifier considerations:  N/A</td><td class="lineno" valign="top"></td></tr>
     762      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     763      <tr><td class="lineno" valign="top"></td><td class="left">   Additional information:</td><td> </td><td class="right">   Additional information:</td><td class="lineno" valign="top"></td></tr>
    699764      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    700765      <tr><td class="lineno" valign="top"></td><td class="left">      Magic number(s):  N/A</td><td> </td><td class="right">      Magic number(s):  N/A</td><td class="lineno" valign="top"></td></tr>
     
    703768      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    704769      <tr><td class="lineno" valign="top"></td><td class="left">      File extension(s):  N/A</td><td> </td><td class="right">      File extension(s):  N/A</td><td class="lineno" valign="top"></td></tr>
    705       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     770      <tr><td><a name="diff0056" /></td></tr>
     771      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                                                                         </span></td><td class="lineno" valign="top"></td></tr>
    706772      <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>
    707773      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    708774      <tr><td class="lineno" valign="top"></td><td class="left">   Person and email address to contact for further information:</td><td> </td><td class="right">   Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr>
    709       <tr><td><a name="diff0039" /></td></tr>
     775      <tr><td><a name="diff0057" /></td></tr>
    710776      <tr><td class="lineno" valign="top"></td><td class="lblock">      See Authors' Addresses Section.</td><td> </td><td class="rblock">      See Authors' Addresses <span class="insert"> </span>Section.</td><td class="lineno" valign="top"></td></tr>
    711777      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    720786      <tr><td class="lineno" valign="top"></td><td class="left">8.3.2.  Internet Media Type application/http</td><td> </td><td class="right">8.3.2.  Internet Media Type application/http</td><td class="lineno" valign="top"></td></tr>
    721787      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    722       <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 63, line 42</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 63, line 42</em></th><td></td></tr>
     788      <tr bgcolor="gray" ><td></td><th><a name="part-l22" /><small>skipping to change at</small><em> page 63, line 29</em></th><th> </th><th><a name="part-r22" /><small>skipping to change at</small><em> page 63, line 42</em></th><td></td></tr>
    723789      <tr><td class="lineno" valign="top"></td><td class="left">   Intended usage:  COMMON</td><td> </td><td class="right">   Intended usage:  COMMON</td><td class="lineno" valign="top"></td></tr>
    724790      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    731797      <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>
    732798      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    733       <tr><td><a name="diff0040" /></td></tr>
     799      <tr><td><a name="diff0058" /></td></tr>
    734800      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP Transfer Coding<span class="delete"> Registry"</span> defines the namespace for</td><td> </td><td class="rblock">   The "HTTP Transfer Coding<span class="insert">" registry</span> defines the namespace for</td><td class="lineno" valign="top"></td></tr>
    735801      <tr><td class="lineno" valign="top"></td><td class="left">   transfer coding names.  It is maintained at</td><td> </td><td class="right">   transfer coding names.  It is maintained at</td><td class="lineno" valign="top"></td></tr>
     
    741807      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    742808      <tr><td class="lineno" valign="top"></td><td class="left">   o  Name</td><td> </td><td class="right">   o  Name</td><td class="lineno" valign="top"></td></tr>
     809      <tr><td><a name="diff0059" /></td></tr>
     810      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                                                                         </span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    743811      <tr><td class="lineno" valign="top"></td><td class="left">   o  Description</td><td> </td><td class="right">   o  Description</td><td class="lineno" valign="top"></td></tr>
    744812      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    745       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    746       <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 64, line 43</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 64, line 43</em></th><td></td></tr>
     813      <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>
     814      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     815      <tr><td class="lineno" valign="top"></td><td class="left">   Names of transfer codings MUST NOT overlap with names of content</td><td> </td><td class="right">   Names of transfer codings MUST NOT overlap with names of content</td><td class="lineno" valign="top"></td></tr>
     816      <tr><td class="lineno" valign="top"></td><td class="left">   codings (Section 3.1.2.1 of [RFC7231]) unless the encoding</td><td> </td><td class="right">   codings (Section 3.1.2.1 of [RFC7231]) unless the encoding</td><td class="lineno" valign="top"></td></tr>
     817      <tr><td class="lineno" valign="top"></td><td class="left">   transformation is identical, as is the case for the compression</td><td> </td><td class="right">   transformation is identical, as is the case for the compression</td><td class="lineno" valign="top"></td></tr>
     818      <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>
     819      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     820      <tr><td class="lineno" valign="top"></td><td class="left">   Values to be added to this namespace require IETF Review (see Section</td><td> </td><td class="right">   Values to be added to this namespace require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
     821      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     822      <tr bgcolor="gray" ><td></td><th><a name="part-l23" /><small>skipping to change at</small><em> page 64, line 31</em></th><th> </th><th><a name="part-r23" /><small>skipping to change at</small><em> page 64, line 43</em></th><td></td></tr>
    747823      <tr><td class="lineno" valign="top"></td><td class="left">   | gzip       | GZIP file format [RFC1952]           | Section 4.2.3 |</td><td> </td><td class="right">   | gzip       | GZIP file format [RFC1952]           | Section 4.2.3 |</td><td class="lineno" valign="top"></td></tr>
    748824      <tr><td class="lineno" valign="top"></td><td class="left">   | x-compress | Deprecated (alias for compress)      | Section 4.2.1 |</td><td> </td><td class="right">   | x-compress | Deprecated (alias for compress)      | Section 4.2.1 |</td><td class="lineno" valign="top"></td></tr>
     
    755831      <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>
    756832      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    757       <tr><td><a name="diff0041" /></td></tr>
     833      <tr><td><a name="diff0060" /></td></tr>
    758834      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP Content Coding Registry" has been updated with the</td><td> </td><td class="rblock">   The "HTTP Content Coding<span class="insert">s</span> Registry" has been updated with the</td><td class="lineno" valign="top"></td></tr>
    759835      <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>
     
    768844      <tr><td class="lineno" valign="top"></td><td class="left">   | gzip       | GZIP file format [RFC1952]           | Section 4.2.3 |</td><td> </td><td class="right">   | gzip       | GZIP file format [RFC1952]           | Section 4.2.3 |</td><td class="lineno" valign="top"></td></tr>
    769845      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    770       <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 66, line 10</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr>
     846      <tr bgcolor="gray" ><td></td><th><a name="part-l24" /><small>skipping to change at</small><em> page 65, line 40</em></th><th> </th><th><a name="part-r24" /><small>skipping to change at</small><em> page 66, line 10</em></th><td></td></tr>
    771847      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    772848      <tr><td class="lineno" valign="top"></td><td class="left">   7.  The IESG MAY reassign responsibility for a protocol token.  This</td><td> </td><td class="right">   7.  The IESG MAY reassign responsibility for a protocol token.  This</td><td class="lineno" valign="top"></td></tr>
     
    779855      <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>
    780856      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    781       <tr><td><a name="diff0042" /></td></tr>
     857      <tr><td><a name="diff0061" /></td></tr>
    782858      <tr><td class="lineno" valign="top"></td><td class="lblock">   The "HTTP" entry in the <span class="delete">upgrade token</span> registry <span class="delete">has been</span> updated with</td><td> </td><td class="rblock">   The "HTTP" entry in the <span class="insert">"HTTP Upgrade Token"</span> registry <span class="insert">shall be</span></td><td class="lineno" valign="top"></td></tr>
    783859      <tr><td class="lineno" valign="top"></td><td class="lblock">   the registration below:</td><td> </td><td class="rblock">   updated with the registration below:</td><td class="lineno" valign="top"></td></tr>
     
    793869      <tr><td class="lineno" valign="top"></td><td class="left">   The responsible party is: "IETF (iesg@ietf.org) - Internet</td><td> </td><td class="right">   The responsible party is: "IETF (iesg@ietf.org) - Internet</td><td class="lineno" valign="top"></td></tr>
    794870      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    795       <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 67, line 13</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr>
     871      <tr bgcolor="gray" ><td></td><th><a name="part-l25" /><small>skipping to change at</small><em> page 66, line 42</em></th><th> </th><th><a name="part-r25" /><small>skipping to change at</small><em> page 67, line 13</em></th><td></td></tr>
    796872      <tr><td class="lineno" valign="top"></td><td class="left">   unknown or untrusted source.</td><td> </td><td class="right">   unknown or untrusted source.</td><td class="lineno" valign="top"></td></tr>
    797873      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    804880      <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>
    805881      <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>
    806       <tr><td><a name="diff0043" /></td></tr>
     882      <tr><td><a name="diff0062" /></td></tr>
    807883      <tr><td class="lineno" valign="top"></td><td class="lblock">   mappings; DNS Security Extensions (DNSSEC<span class="delete">, [RFC4033]) are</span> one way to</td><td> </td><td class="rblock">   mappings; DNS Security Extensions (DNSSEC<span class="insert">) ([RFC4033]) is</span> one way to</td><td class="lineno" valign="top"></td></tr>
    808884      <tr><td class="lineno" valign="top"></td><td class="left">   improve authenticity.</td><td> </td><td class="right">   improve authenticity.</td><td class="lineno" valign="top"></td></tr>
     
    822898      <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>
    823899      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    824       <tr><td><a name="diff0044" /></td></tr>
     900      <tr><td><a name="diff0063" /></td></tr>
    825901      <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>
    826902      <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>
     
    836912      <tr><td class="lineno" valign="top"></td><td class="left">   Intermediaries that contain a shared cache are especially vulnerable</td><td> </td><td class="right">   Intermediaries that contain a shared cache are especially vulnerable</td><td class="lineno" valign="top"></td></tr>
    837913      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    838       <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 70, line 9</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr>
     914      <tr bgcolor="gray" ><td></td><th><a name="part-l26" /><small>skipping to change at</small><em> page 69, line 39</em></th><th> </th><th><a name="part-r26" /><small>skipping to change at</small><em> page 70, line 9</em></th><td></td></tr>
    839915      <tr><td class="lineno" valign="top"></td><td class="left">   access mechanism has resulted in its increasing use within</td><td> </td><td class="right">   access mechanism has resulted in its increasing use within</td><td class="lineno" valign="top"></td></tr>
    840916      <tr><td class="lineno" valign="top"></td><td class="left">   environments where verification of message integrity is crucial.</td><td> </td><td class="right">   environments where verification of message integrity is crucial.</td><td class="lineno" valign="top"></td></tr>
     
    847923      <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>
    848924      <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>
    849       <tr><td><a name="diff0045" /></td></tr>
     925      <tr><td><a name="diff0064" /></td></tr>
    850926      <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>
    851927      <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>
     
    860936      <tr><td class="lineno" valign="top"></td><td class="left">   designed to be independent of the transport protocol, such that it</td><td> </td><td class="right">   designed to be independent of the transport protocol, such that it</td><td class="lineno" valign="top"></td></tr>
    861937      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    862       <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 72, line 50</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr>
     938      <tr bgcolor="gray" ><td></td><th><a name="part-l27" /><small>skipping to change at</small><em> page 72, line 29</em></th><th> </th><th><a name="part-r27" /><small>skipping to change at</small><em> page 72, line 50</em></th><td></td></tr>
    863939      <tr><td class="lineno" valign="top"></td><td class="left">   Yuchung Cheng, Yutaka Oiwa, Yves Lafon (long-time member of the</td><td> </td><td class="right">   Yuchung Cheng, Yutaka Oiwa, Yves Lafon (long-time member of the</td><td class="lineno" valign="top"></td></tr>
    864940      <tr><td class="lineno" valign="top"></td><td class="left">   editor team), Zed A. Shaw, and Zhong Yu.</td><td> </td><td class="right">   editor team), Zed A. Shaw, and Zhong Yu.</td><td class="lineno" valign="top"></td></tr>
     
    871947      <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>
    872948      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    873       <tr><td><a name="diff0046" /></td></tr>
     949      <tr><td><a name="diff0065" /></td></tr>
    874950      <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>
    875951      <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>
     
    886962      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    887963      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    888       <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 73, line 28</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr>
     964      <tr bgcolor="gray" ><td></td><th><a name="part-l28" /><small>skipping to change at</small><em> page 73, line 7</em></th><th> </th><th><a name="part-r28" /><small>skipping to change at</small><em> page 73, line 25</em></th><td></td></tr>
    889965      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,</td><td> </td><td class="right">   [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,</td><td class="lineno" valign="top"></td></tr>
    890966      <tr><td class="lineno" valign="top"></td><td class="left">                 "Uniform Resource Identifier (URI): Generic Syntax",</td><td> </td><td class="right">                 "Uniform Resource Identifier (URI): Generic Syntax",</td><td class="lineno" valign="top"></td></tr>
     
    897973      <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>
    898974      <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>
    899       <tr><td><a name="diff0047" /></td></tr>
     975      <tr><td><a name="diff0066" /></td></tr>
    900976      <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>
    901977      <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>
     
    903979      <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>
    904980      <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>
    905       <tr><td><a name="diff0048" /></td></tr>
     981      <tr><td><a name="diff0067" /></td></tr>
    906982      <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>
    907983      <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>
     
    909985      <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>
    910986      <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>
    911       <tr><td><a name="diff0049" /></td></tr>
     987      <tr><td><a name="diff0068" /></td></tr>
    912988      <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>
    913989      <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>
     
    915991      <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>
    916992      <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>
    917       <tr><td><a name="diff0050" /></td></tr>
     993      <tr><td><a name="diff0069" /></td></tr>
    918994      <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>
    919995      <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>
     
    921997      <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>
    922998      <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>
    923       <tr><td><a name="diff0051" /></td></tr>
     999      <tr><td><a name="diff0070" /></td></tr>
    9241000      <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>
    9251001      <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>
     
    9371013      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9381014      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    939       <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 77, line 10</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr>
     1015      <tr bgcolor="gray" ><td></td><th><a name="part-l29" /><small>skipping to change at</small><em> page 76, line 36</em></th><th> </th><th><a name="part-r29" /><small>skipping to change at</small><em> page 77, line 5</em></th><td></td></tr>
    9401016      <tr><td class="lineno" valign="top"></td><td class="left">   implements name-based virtual hosts ought to disable support for</td><td> </td><td class="right">   implements name-based virtual hosts ought to disable support for</td><td class="lineno" valign="top"></td></tr>
    9411017      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP/0.9.  Most requests that appear to be HTTP/0.9 are, in fact,</td><td> </td><td class="right">   HTTP/0.9.  Most requests that appear to be HTTP/0.9 are, in fact,</td><td class="lineno" valign="top"></td></tr>
     
    9481024      <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>
    9491025      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    950       <tr><td><a name="diff0052" /></td></tr>
     1026      <tr><td><a name="diff0071" /></td></tr>
    9511027      <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>
    9521028      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    9611037      <tr><td class="lineno" valign="top"></td><td class="left">   to which that request was directed.  The Host header field was</td><td> </td><td class="right">   to which that request was directed.  The Host header field was</td><td class="lineno" valign="top"></td></tr>
    9621038      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    963       <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 78, line 20</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr>
     1039      <tr bgcolor="gray" ><td></td><th><a name="part-l30" /><small>skipping to change at</small><em> page 77, line 46</em></th><th> </th><th><a name="part-r30" /><small>skipping to change at</small><em> page 78, line 14</em></th><td></td></tr>
    9641040      <tr><td class="lineno" valign="top"></td><td class="left">   not be used by clients at all when a proxy is being used.</td><td> </td><td class="right">   not be used by clients at all when a proxy is being used.</td><td class="lineno" valign="top"></td></tr>
    9651041      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    9721048      <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>
    9731049      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    974       <tr><td><a name="diff0053" /></td></tr>
     1050      <tr><td><a name="diff0072" /></td></tr>
    9751051      <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>
    9761052      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    977       <tr><td><a name="diff0054" /></td></tr>
     1053      <tr><td><a name="diff0073" /></td></tr>
    9781054      <tr><td class="lineno" valign="top"></td><td class="lblock">   The HTTP-version ABNF production has been clarified to be case<span class="delete">-</span></td><td> </td><td class="rblock">   The HTTP-version ABNF production has been clarified to be case</td><td class="lineno" valign="top"></td></tr>
    9791055      <tr><td class="lineno" valign="top"></td><td class="left">   sensitive.  Additionally, version numbers have been restricted to</td><td> </td><td class="right">   sensitive.  Additionally, version numbers have been restricted to</td><td class="lineno" valign="top"></td></tr>
    9801056      <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>
    981       <tr><td><a name="diff0055" /></td></tr>
    982       <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>
    983       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1057      <tr><td><a name="diff0074" /></td></tr>
     1058      <tr><td class="lineno" valign="top"></td><td class="lblock">   handle multi-digit version numbers <span class="delete">incorrectly.</span>  (Section <span class="delete">2.6)</span></td><td> </td><td class="rblock">   handle multi-digit version numbers <span class="insert">incorrectly</span> (Section <span class="insert">2.6).</span></td><td class="lineno" valign="top"></td></tr>
     1059      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
    9841060      <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>
    9851061      <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>
    986       <tr><td><a name="diff0056" /></td></tr>
     1062      <tr><td><a name="diff0075" /></td></tr>
    9871063      <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>
    9881064      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9891065      <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>
    990       <tr><td><a name="diff0057" /></td></tr>
     1066      <tr><td><a name="diff0076" /></td></tr>
    9911067      <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>
    9921068      <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>
     
    9961072      <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>
    9971073      <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>
    998       <tr><td><a name="diff0058" /></td></tr>
     1074      <tr><td><a name="diff0077" /></td></tr>
    9991075      <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>
    10001076      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10011077      <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>
    10021078      <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>
    1003       <tr><td><a name="diff0059" /></td></tr>
     1079      <tr><td><a name="diff0078" /></td></tr>
    10041080      <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>
    10051081      <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>
     
    10071083      <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>
    10081084      <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>
    1009       <tr><td><a name="diff0060" /></td></tr>
     1085      <tr><td><a name="diff0079" /></td></tr>
    10101086      <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>
    10111087      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10121088      <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>
    1013       <tr><td><a name="diff0061" /></td></tr>
    1014       <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>
    1015       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
     1089      <tr><td><a name="diff0080" /></td></tr>
     1090      <tr><td class="lineno" valign="top"></td><td class="lblock">   deprecated<span class="delete">.  (Section 3.2.4)</span></td><td> </td><td class="rblock">   deprecated<span class="insert"> (Section 3.2.4).</span></td><td class="lineno" valign="top"></td></tr>
     1091      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10161092      <tr><td class="lineno" valign="top"></td><td class="left">   The NUL octet is no longer allowed in comment and quoted-string text,</td><td> </td><td class="right">   The NUL octet is no longer allowed in comment and quoted-string text,</td><td class="lineno" valign="top"></td></tr>
    10171093      <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>
    10181094      <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>
    10191095      <tr><td class="lineno" valign="top"></td><td class="left">   than HTAB.  Non-US-ASCII content in header fields and the reason</td><td> </td><td class="right">   than HTAB.  Non-US-ASCII content in header fields and the reason</td><td class="lineno" valign="top"></td></tr>
    1020       <tr><td><a name="diff0062" /></td></tr>
     1096      <tr><td><a name="diff0081" /></td></tr>
    10211097      <tr><td class="lineno" valign="top"></td><td class="lblock">   phrase has been obsoleted and made opaque (the TEXT rule was</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>
    10221098      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">removed).</span>  (Section <span class="delete">3.2.6)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.2.6).</span></td><td class="lineno" valign="top"></td></tr>
    10231099      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10241100      <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>
    1025       <tr><td><a name="diff0063" /></td></tr>
     1101      <tr><td><a name="diff0082" /></td></tr>
    10261102      <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>
    10271103      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    10311107      <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>
    10321108      <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>
    1033       <tr><td><a name="diff0064" /></td></tr>
     1109      <tr><td><a name="diff0083" /></td></tr>
    10341110      <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>
    10351111      <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>
    10361112      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1037       <tr><td><a name="diff0065" /></td></tr>
     1113      <tr><td><a name="diff0084" /></td></tr>
    10381114      <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>
    10391115      <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>
    10401116      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10411117      <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>
    1042       <tr><td><a name="diff0066" /></td></tr>
     1118      <tr><td><a name="diff0085" /></td></tr>
    10431119      <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>
    10441120      <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>
    10451121      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1046       <tr><td><a name="diff0067" /></td></tr>
     1122      <tr><td><a name="diff0086" /></td></tr>
    10471123      <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>
    10481124      <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>
     
    10501126      <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>
    10511127      <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>
    1052       <tr><td><a name="diff0068" /></td></tr>
     1128      <tr><td><a name="diff0087" /></td></tr>
    10531129      <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>
    10541130      <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>
    10551131      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1056       <tr><td><a name="diff0069" /></td></tr>
     1132      <tr><td><a name="diff0088" /></td></tr>
    10571133      <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>
    10581134      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1059       <tr><td><a name="diff0070" /></td></tr>
     1135      <tr><td><a name="diff0089" /></td></tr>
    10601136      <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>
    10611137      <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>
     
    10641140      <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>
    10651141      <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>
    1066       <tr><td><a name="diff0071" /></td></tr>
     1142      <tr><td><a name="diff0090" /></td></tr>
    10671143      <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>
    10681144      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    10721148      <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>
    10731149      <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>
    1074       <tr><td><a name="diff0072" /></td></tr>
     1150      <tr><td><a name="diff0091" /></td></tr>
    10751151      <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>
    10761152      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10771153      <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>
    10781154      <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>
    1079       <tr><td><a name="diff0073" /></td></tr>
     1155      <tr><td><a name="diff0092" /></td></tr>
    10801156      <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>
    10811157      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10821158      <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>
    1083       <tr><td><a name="diff0074" /></td></tr>
     1159      <tr><td><a name="diff0093" /></td></tr>
    10841160      <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>
    10851161      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10861162      <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>
    1087       <tr><td><a name="diff0075" /></td></tr>
     1163      <tr><td><a name="diff0094" /></td></tr>
    10881164      <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>
    10891165      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1090       <tr><td><a name="diff0076" /></td></tr>
     1166      <tr><td><a name="diff0095" /></td></tr>
    10911167      <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>
    10921168      <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>
    10931169      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1094       <tr><td><a name="diff0077" /></td></tr>
     1170      <tr><td><a name="diff0096" /></td></tr>
    10951171      <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>
    10961172      <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>
     
    10981174      <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>
    10991175      <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>
    1100       <tr><td><a name="diff0078" /></td></tr>
     1176      <tr><td><a name="diff0097" /></td></tr>
    11011177      <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>
    11021178      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11111187      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP-message = start-line *( header-field CRLF ) CRLF [ message-body</td><td> </td><td class="right">   HTTP-message = start-line *( header-field CRLF ) CRLF [ message-body</td><td class="lineno" valign="top"></td></tr>
    11121188      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1113       <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 83, line 25</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 83, line 20</em></th><td></td></tr>
     1189      <tr bgcolor="gray" ><td></td><th><a name="part-l31" /><small>skipping to change at</small><em> page 82, line 29</em></th><th> </th><th><a name="part-r31" /><small>skipping to change at</small><em> page 82, line 42</em></th><td></td></tr>
     1190      <tr><td class="lineno" valign="top"></td><td class="left">   transfer-coding = "chunked" / "compress" / "deflate" / "gzip" /</td><td> </td><td class="right">   transfer-coding = "chunked" / "compress" / "deflate" / "gzip" /</td><td class="lineno" valign="top"></td></tr>
     1191      <tr><td class="lineno" valign="top"></td><td class="left">    transfer-extension</td><td> </td><td class="right">    transfer-extension</td><td class="lineno" valign="top"></td></tr>
     1192      <tr><td class="lineno" valign="top"></td><td class="left">   transfer-extension = token *( OWS ";" OWS transfer-parameter )</td><td> </td><td class="right">   transfer-extension = token *( OWS ";" OWS transfer-parameter )</td><td class="lineno" valign="top"></td></tr>
     1193      <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>
     1194      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1195      <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>
     1196      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1197      <tr><td class="lineno" valign="top"></td><td class="left">Index</td><td> </td><td class="right">Index</td><td class="lineno" valign="top"></td></tr>
     1198      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1199      <tr><td class="lineno" valign="top"></td><td class="left">   A</td><td> </td><td class="right">   A</td><td class="lineno" valign="top"></td></tr>
     1200      <tr><td><a name="diff0098" /></td></tr>
     1201      <tr><td class="lineno" valign="top"></td><td class="lblock">      absolute-form (of request-target)  4<span class="delete">1</span></td><td> </td><td class="rblock">      absolute-form (of request-target)  4<span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
     1202      <tr><td class="lineno" valign="top"></td><td class="left">      accelerator  10</td><td> </td><td class="right">      accelerator  10</td><td class="lineno" valign="top"></td></tr>
     1203      <tr><td class="lineno" valign="top"></td><td class="left">      application/http Media Type  62</td><td> </td><td class="right">      application/http Media Type  62</td><td class="lineno" valign="top"></td></tr>
     1204      <tr><td class="lineno" valign="top"></td><td class="left">      asterisk-form (of request-target)  42</td><td> </td><td class="right">      asterisk-form (of request-target)  42</td><td class="lineno" valign="top"></td></tr>
     1205      <tr><td class="lineno" valign="top"></td><td class="left">      authoritative response  66</td><td> </td><td class="right">      authoritative response  66</td><td class="lineno" valign="top"></td></tr>
     1206      <tr><td class="lineno" valign="top"></td><td class="left">      authority-form (of request-target)  42</td><td> </td><td class="right">      authority-form (of request-target)  42</td><td class="lineno" valign="top"></td></tr>
     1207      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1208      <tr><td class="lineno" valign="top"></td><td class="left">   B</td><td> </td><td class="right">   B</td><td class="lineno" valign="top"></td></tr>
     1209      <tr><td class="lineno" valign="top"></td><td class="left">      browser  7</td><td> </td><td class="right">      browser  7</td><td class="lineno" valign="top"></td></tr>
     1210      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1211      <tr><td class="lineno" valign="top"></td><td class="left">   C</td><td> </td><td class="right">   C</td><td class="lineno" valign="top"></td></tr>
     1212      <tr><td class="lineno" valign="top"></td><td class="left">      cache  11</td><td> </td><td class="right">      cache  11</td><td class="lineno" valign="top"></td></tr>
     1213      <tr><td class="lineno" valign="top"></td><td class="left">      cacheable  11</td><td> </td><td class="right">      cacheable  11</td><td class="lineno" valign="top"></td></tr>
     1214      <tr><td class="lineno" valign="top"></td><td class="left">      captive portal  11</td><td> </td><td class="right">      captive portal  11</td><td class="lineno" valign="top"></td></tr>
     1215      <tr><td class="lineno" valign="top"></td><td class="left">      chunked (Coding Format)  28, 31, 35</td><td> </td><td class="right">      chunked (Coding Format)  28, 31, 35</td><td class="lineno" valign="top"></td></tr>
    11141216      <tr><td class="lineno" valign="top"></td><td class="left">      client  7</td><td> </td><td class="right">      client  7</td><td class="lineno" valign="top"></td></tr>
    11151217      <tr><td class="lineno" valign="top"></td><td class="left">      close  50, 55</td><td> </td><td class="right">      close  50, 55</td><td class="lineno" valign="top"></td></tr>
     
    11171219      <tr><td class="lineno" valign="top"></td><td class="left">      connection  7</td><td> </td><td class="right">      connection  7</td><td class="lineno" valign="top"></td></tr>
    11181220      <tr><td class="lineno" valign="top"></td><td class="left">      Connection header field  50, 55</td><td> </td><td class="right">      Connection header field  50, 55</td><td class="lineno" valign="top"></td></tr>
    1119       <tr><td class="lineno" valign="top"></td><td class="left">      Content-Length header field  30</td><td> </td><td class="right">      Content-Length header field  30</td><td class="lineno" valign="top"></td></tr>
     1221      <tr><td><a name="diff0099" /></td></tr>
     1222      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Length header field  <span class="delete">29</span></td><td> </td><td class="rblock">      Content-Length header field  <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
    11201223      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11211224      <tr><td class="lineno" valign="top"></td><td class="left">   D</td><td> </td><td class="right">   D</td><td class="lineno" valign="top"></td></tr>
    11221225      <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>
    11231226      <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>
    1124       <tr><td><a name="diff0079" /></td></tr>
     1227      <tr><td><a name="diff0100" /></td></tr>
    11251228      <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>
    11261229      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    11311234      <tr><td class="lineno" valign="top"></td><td class="left">      gateway  10</td><td> </td><td class="right">      gateway  10</td><td class="lineno" valign="top"></td></tr>
    11321235      <tr><td class="lineno" valign="top"></td><td class="left">      Grammar</td><td> </td><td class="right">      Grammar</td><td class="lineno" valign="top"></td></tr>
    1133       <tr><td class="lineno" valign="top"></td><td class="left">         absolute-form  41-42</td><td> </td><td class="right">         absolute-form  41-42</td><td class="lineno" valign="top"></td></tr>
     1236      <tr><td><a name="diff0101" /></td></tr>
     1237      <tr><td class="lineno" valign="top"></td><td class="lblock">         absolute-form  41</td><td> </td><td class="rblock">         absolute-form  41<span class="insert">-42</span></td><td class="lineno" valign="top"></td></tr>
    11341238      <tr><td class="lineno" valign="top"></td><td class="left">         absolute-path  16</td><td> </td><td class="right">         absolute-path  16</td><td class="lineno" valign="top"></td></tr>
    11351239      <tr><td class="lineno" valign="top"></td><td class="left">         absolute-URI  16</td><td> </td><td class="right">         absolute-URI  16</td><td class="lineno" valign="top"></td></tr>
    1136       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1137       <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 84, line 20</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 84, line 14</em></th><td></td></tr>
     1240      <tr><td class="lineno" valign="top"></td><td class="left">         ALPHA  6</td><td> </td><td class="right">         ALPHA  6</td><td class="lineno" valign="top"></td></tr>
     1241      <tr><td class="lineno" valign="top"></td><td class="left">         asterisk-form  41-42</td><td> </td><td class="right">         asterisk-form  41-42</td><td class="lineno" valign="top"></td></tr>
     1242      <tr><td class="lineno" valign="top"></td><td class="left">         authority  16</td><td> </td><td class="right">         authority  16</td><td class="lineno" valign="top"></td></tr>
     1243      <tr><td class="lineno" valign="top"></td><td class="left">         authority-form  41-42</td><td> </td><td class="right">         authority-form  41-42</td><td class="lineno" valign="top"></td></tr>
     1244      <tr><td class="lineno" valign="top"></td><td class="left">         BWS  24</td><td> </td><td class="right">         BWS  24</td><td class="lineno" valign="top"></td></tr>
     1245      <tr><td class="lineno" valign="top"></td><td class="left">         chunk  35</td><td> </td><td class="right">         chunk  35</td><td class="lineno" valign="top"></td></tr>
     1246      <tr><td class="lineno" valign="top"></td><td class="left">         chunk-data  35</td><td> </td><td class="right">         chunk-data  35</td><td class="lineno" valign="top"></td></tr>
     1247      <tr><td class="lineno" valign="top"></td><td class="left">         chunk-ext  35-36</td><td> </td><td class="right">         chunk-ext  35-36</td><td class="lineno" valign="top"></td></tr>
     1248      <tr><td class="lineno" valign="top"></td><td class="left">         chunk-ext-name  36</td><td> </td><td class="right">         chunk-ext-name  36</td><td class="lineno" valign="top"></td></tr>
     1249      <tr><td class="lineno" valign="top"></td><td class="left">         chunk-ext-val  36</td><td> </td><td class="right">         chunk-ext-val  36</td><td class="lineno" valign="top"></td></tr>
     1250      <tr><td class="lineno" valign="top"></td><td class="left">         chunk-size  35</td><td> </td><td class="right">         chunk-size  35</td><td class="lineno" valign="top"></td></tr>
     1251      <tr><td class="lineno" valign="top"></td><td class="left">         chunked-body  35-36</td><td> </td><td class="right">         chunked-body  35-36</td><td class="lineno" valign="top"></td></tr>
     1252      <tr><td class="lineno" valign="top"></td><td class="left">         comment  27</td><td> </td><td class="right">         comment  27</td><td class="lineno" valign="top"></td></tr>
     1253      <tr><td><a name="diff0102" /></td></tr>
     1254      <tr><td class="lineno" valign="top"></td><td class="lblock">         Connection  <span class="delete">50</span></td><td> </td><td class="rblock">         Connection  <span class="insert">51</span></td><td class="lineno" valign="top"></td></tr>
     1255      <tr><td class="lineno" valign="top"></td><td class="lblock">         connection-option  <span class="delete">50</span></td><td> </td><td class="rblock">         connection-option  <span class="insert">51</span></td><td class="lineno" valign="top"></td></tr>
     1256      <tr><td class="lineno" valign="top"></td><td class="lblock">         Content-Length  <span class="delete">29</span></td><td> </td><td class="rblock">         Content-Length  <span class="insert">30</span></td><td class="lineno" valign="top"></td></tr>
     1257      <tr><td class="lineno" valign="top"></td><td class="left">         CR  6</td><td> </td><td class="right">         CR  6</td><td class="lineno" valign="top"></td></tr>
     1258      <tr><td class="lineno" valign="top"></td><td class="left">         CRLF  6</td><td> </td><td class="right">         CRLF  6</td><td class="lineno" valign="top"></td></tr>
     1259      <tr><td class="lineno" valign="top"></td><td class="left">         ctext  27</td><td> </td><td class="right">         ctext  27</td><td class="lineno" valign="top"></td></tr>
     1260      <tr><td class="lineno" valign="top"></td><td class="left">         CTL  6</td><td> </td><td class="right">         CTL  6</td><td class="lineno" valign="top"></td></tr>
     1261      <tr><td class="lineno" valign="top"></td><td class="left">         DIGIT  6</td><td> </td><td class="right">         DIGIT  6</td><td class="lineno" valign="top"></td></tr>
     1262      <tr><td class="lineno" valign="top"></td><td class="left">         DQUOTE  6</td><td> </td><td class="right">         DQUOTE  6</td><td class="lineno" valign="top"></td></tr>
    11381263      <tr><td class="lineno" valign="top"></td><td class="left">         field-content  22</td><td> </td><td class="right">         field-content  22</td><td class="lineno" valign="top"></td></tr>
    11391264      <tr><td class="lineno" valign="top"></td><td class="left">         field-name  22, 39</td><td> </td><td class="right">         field-name  22, 39</td><td class="lineno" valign="top"></td></tr>
     
    11461271      <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>
    11471272      <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>
    1148       <tr><td><a name="diff0080" /></td></tr>
     1273      <tr><td><a name="diff0103" /></td></tr>
    11491274      <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>
    11501275      <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>
    1151       <tr><td><a name="diff0081" /></td></tr>
     1276      <tr><td><a name="diff0104" /></td></tr>
    11521277      <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>
    11531278      <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>
     
    11621287      <tr><td class="lineno" valign="top"></td><td class="left">         OWS  24</td><td> </td><td class="right">         OWS  24</td><td class="lineno" valign="top"></td></tr>
    11631288      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1164       <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 85, line 34</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr>
     1289      <tr bgcolor="gray" ><td></td><th><a name="part-l32" /><small>skipping to change at</small><em> page 84, line 38</em></th><th> </th><th><a name="part-r32" /><small>skipping to change at</small><em> page 84, line 51</em></th><td></td></tr>
     1290      <tr><td class="lineno" valign="top"></td><td class="left">         request-target  41</td><td> </td><td class="right">         request-target  41</td><td class="lineno" valign="top"></td></tr>
     1291      <tr><td class="lineno" valign="top"></td><td class="left">         RWS  24</td><td> </td><td class="right">         RWS  24</td><td class="lineno" valign="top"></td></tr>
     1292      <tr><td class="lineno" valign="top"></td><td class="left">         scheme  16</td><td> </td><td class="right">         scheme  16</td><td class="lineno" valign="top"></td></tr>
     1293      <tr><td class="lineno" valign="top"></td><td class="left">         segment  16</td><td> </td><td class="right">         segment  16</td><td class="lineno" valign="top"></td></tr>
     1294      <tr><td class="lineno" valign="top"></td><td class="left">         SP  6</td><td> </td><td class="right">         SP  6</td><td class="lineno" valign="top"></td></tr>
     1295      <tr><td class="lineno" valign="top"></td><td class="left">         start-line  20</td><td> </td><td class="right">         start-line  20</td><td class="lineno" valign="top"></td></tr>
     1296      <tr><td class="lineno" valign="top"></td><td class="left">         status-code  22</td><td> </td><td class="right">         status-code  22</td><td class="lineno" valign="top"></td></tr>
     1297      <tr><td class="lineno" valign="top"></td><td class="left">         status-line  22</td><td> </td><td class="right">         status-line  22</td><td class="lineno" valign="top"></td></tr>
     1298      <tr><td class="lineno" valign="top"></td><td class="left">         t-codings  38</td><td> </td><td class="right">         t-codings  38</td><td class="lineno" valign="top"></td></tr>
     1299      <tr><td class="lineno" valign="top"></td><td class="left">         t-ranking  38</td><td> </td><td class="right">         t-ranking  38</td><td class="lineno" valign="top"></td></tr>
     1300      <tr><td><a name="diff0105" /></td></tr>
     1301      <tr><td class="lineno" valign="top"></td><td class="lblock">         tchar  2<span class="delete">6</span></td><td> </td><td class="rblock">         tchar  2<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     1302      <tr><td class="lineno" valign="top"></td><td class="left">         TE  38</td><td> </td><td class="right">         TE  38</td><td class="lineno" valign="top"></td></tr>
     1303      <tr><td><a name="diff0106" /></td></tr>
     1304      <tr><td class="lineno" valign="top"></td><td class="lblock">         token  2<span class="delete">6</span></td><td> </td><td class="rblock">         token  2<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     1305      <tr><td class="lineno" valign="top"></td><td class="left">         Trailer  39</td><td> </td><td class="right">         Trailer  39</td><td class="lineno" valign="top"></td></tr>
     1306      <tr><td class="lineno" valign="top"></td><td class="left">         trailer-part  35-36</td><td> </td><td class="right">         trailer-part  35-36</td><td class="lineno" valign="top"></td></tr>
     1307      <tr><td class="lineno" valign="top"></td><td class="left">         transfer-coding  35</td><td> </td><td class="right">         transfer-coding  35</td><td class="lineno" valign="top"></td></tr>
     1308      <tr><td class="lineno" valign="top"></td><td class="left">         Transfer-Encoding  28</td><td> </td><td class="right">         Transfer-Encoding  28</td><td class="lineno" valign="top"></td></tr>
     1309      <tr><td class="lineno" valign="top"></td><td class="left">         transfer-extension  35</td><td> </td><td class="right">         transfer-extension  35</td><td class="lineno" valign="top"></td></tr>
     1310      <tr><td class="lineno" valign="top"></td><td class="left">         transfer-parameter  35</td><td> </td><td class="right">         transfer-parameter  35</td><td class="lineno" valign="top"></td></tr>
     1311      <tr><td class="lineno" valign="top"></td><td class="left">         Upgrade  56</td><td> </td><td class="right">         Upgrade  56</td><td class="lineno" valign="top"></td></tr>
     1312      <tr><td class="lineno" valign="top"></td><td class="left">         uri-host  16</td><td> </td><td class="right">         uri-host  16</td><td class="lineno" valign="top"></td></tr>
     1313      <tr><td class="lineno" valign="top"></td><td class="left">         URI-reference  16</td><td> </td><td class="right">         URI-reference  16</td><td class="lineno" valign="top"></td></tr>
     1314      <tr><td class="lineno" valign="top"></td><td class="left">         VCHAR  6</td><td> </td><td class="right">         VCHAR  6</td><td class="lineno" valign="top"></td></tr>
     1315      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     1316      <tr bgcolor="gray" ><td></td><th><a name="part-l33" /><small>skipping to change at</small><em> page 85, line 16</em></th><th> </th><th><a name="part-r33" /><small>skipping to change at</small><em> page 85, line 28</em></th><td></td></tr>
    11651317      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11661318      <tr><td class="lineno" valign="top"></td><td class="left">   H</td><td> </td><td class="right">   H</td><td class="lineno" valign="top"></td></tr>
     
    11731325      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    11741326      <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>
    1175       <tr><td><a name="diff0082" /></td></tr>
     1327      <tr><td><a name="diff0107" /></td></tr>
    11761328      <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>
    11771329      <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>
     
    11921344      <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>
    11931345      <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>
    1194       <tr><td><a name="diff0083" /></td></tr>
     1346      <tr><td><a name="diff0108" /></td></tr>
    11951347      <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>
    11961348      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12051357      <tr><td class="lineno" valign="top"></td><td class="left">      resource  16</td><td> </td><td class="right">      resource  16</td><td class="lineno" valign="top"></td></tr>
    12061358      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1207       <tr bgcolor="gray" ><td></td><th><a name="part-l35" /><small>skipping to change at</small><em> page 86, line 35</em></th><th> </th><th><a name="part-r35" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr>
     1359      <tr bgcolor="gray" ><td></td><th><a name="part-l34" /><small>skipping to change at</small><em> page 86, line 17</em></th><th> </th><th><a name="part-r34" /><small>skipping to change at</small><em> page 86, line 30</em></th><td></td></tr>
    12081360      <tr><td class="lineno" valign="top"></td><td class="left">      target URI  40</td><td> </td><td class="right">      target URI  40</td><td class="lineno" valign="top"></td></tr>
    12091361      <tr><td class="lineno" valign="top"></td><td class="left">      TE header field  38</td><td> </td><td class="right">      TE header field  38</td><td class="lineno" valign="top"></td></tr>
     
    12161368      <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>
    12171369      <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>
    1218       <tr><td><a name="diff0084" /></td></tr>
     1370      <tr><td><a name="diff0109" /></td></tr>
    12191371      <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>
    12201372      <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>
     
    12241376      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12251377      <tr><td class="lineno" valign="top"></td><td class="left">   V</td><td> </td><td class="right">   V</td><td class="lineno" valign="top"></td></tr>
    1226       <tr><td class="lineno" valign="top"></td><td class="left">      Via header field  47</td><td> </td><td class="right">      Via header field  47</td><td class="lineno" valign="top"></td></tr>
     1378      <tr><td><a name="diff0110" /></td></tr>
     1379      <tr><td class="lineno" valign="top"></td><td class="lblock">      Via header field  4<span class="delete">6</span></td><td> </td><td class="rblock">      Via header field  4<span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    12271380      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12281381      <tr><td class="lineno" valign="top"></td><td class="left">Authors' Addresses</td><td> </td><td class="right">Authors' Addresses</td><td class="lineno" valign="top"></td></tr>
    12291382      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1383      <tr><td class="lineno" valign="top"></td><td class="left">   Roy T. Fielding (editor)</td><td> </td><td class="right">   Roy T. Fielding (editor)</td><td class="lineno" valign="top"></td></tr>
     1384      <tr><td class="lineno" valign="top"></td><td class="left">   Adobe Systems Incorporated</td><td> </td><td class="right">   Adobe Systems Incorporated</td><td class="lineno" valign="top"></td></tr>
     1385      <tr><td class="lineno" valign="top"></td><td class="left">   345 Park Ave</td><td> </td><td class="right">   345 Park Ave</td><td class="lineno" valign="top"></td></tr>
     1386      <tr><td class="lineno" valign="top"></td><td class="left">   San Jose, CA  95110</td><td> </td><td class="right">   San Jose, CA  95110</td><td class="lineno" valign="top"></td></tr>
     1387      <tr><td class="lineno" valign="top"></td><td class="left">   USA</td><td> </td><td class="right">   USA</td><td class="lineno" valign="top"></td></tr>
     1388      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1389      <tr><td class="lineno" valign="top"></td><td class="left">   EMail: fielding@gbiv.com</td><td> </td><td class="right">   EMail: fielding@gbiv.com</td><td class="lineno" valign="top"></td></tr>
    12301390
    12311391     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    1232      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 84 change blocks.&nbsp;</a></th></tr>
    1233      <tr class="stats"><td></td><th><i>144 lines changed or deleted</i></th><th><i> </i></th><th><i>121 lines changed or added</i></th><td></td></tr>
     1392     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 110 change blocks.&nbsp;</a></th></tr>
     1393     <tr class="stats"><td></td><th><i>173 lines changed or deleted</i></th><th><i> </i></th><th><i>150 lines changed or added</i></th><td></td></tr>
    12341394     <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>
    12351395   </table>
  • draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt

    r2659 r2660  
    493493
    494494    All content-coding values are case-insensitive and ought to be
    495     registered within the HTTP Content Coding registry, as defined in
     495    registered within the "HTTP Content Coding Registry", as defined in
    496496    Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)
    497497    and Content-Encoding (Section 3.1.2.2) header fields.
     
    608608    Additional methods, outside the scope of this specification, have
    609609    been standardized for use in HTTP.  All such methods ought to be
    610     registered within the HTTP Method Registry maintained by IANA, as
    611     defined in Section 8.1.
     610    registered within the "Hypertext Transfer Protocol (HTTP) Method
     611    Registry" maintained by IANA, as defined in Section 8.1.
    612612
    613613NEW:
     
    623623
    624624    This definition of safe methods does not prevent an implementation
    625     from including behavior that is potentially harmful, not entirely
    626     read-only, or which causes side effects while invoking a safe method.
    627     What is important, however, is that the client did not request that
    628     additional behavior and cannot be held accountable for it.  For
    629     example, most servers append request information to access log files
    630     at the completion of every response, regardless of the method, and
    631     that is considered safe even though the log storage might become full
    632     and crash the server.  Likewise, a safe request initiated by
    633     selecting an advertisement on the Web will often have the side effect
    634     of charging an advertising account.
     625    from including behavior that is potentially harmful, that is not
     626    entirely read-only, or that causes side effects while invoking a safe
     627    method.  What is important, however, is that the client did not
     628    request that additional behavior and cannot be held accountable for
     629    it.  For example, most servers append request information to access
     630    log files at the completion of every response, regardless of the
     631    method, and that is considered safe even though the log storage might
     632    become full and crash the server.  Likewise, a safe request initiated
     633    by selecting an advertisement on the Web will often have the side
     634    effect of charging an advertising account.
    635635
    636636NEW:
     
    757757
    758758
    759 Section 6.1., paragraph 2:
    760 OLD:
    761 
    762     Responses with status codes that are defined as cacheable by default
    763     (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501 in this
    764     specification) can be reused by a cache with heuristic expiration
    765     unless otherwise indicated by the method definition or explicit cache
    766     controls [RFC7234]; all other status codes are not cacheable by
    767     default.
    768 
    769 NEW:
    770 
    771     Responses with status codes that are defined as cacheable by default
    772     (e.g., 200, 203, 204, 206, 300, 301, 404, 405, 410, 414, and 501 in
    773     this specification) can be reused by a cache with heuristic
    774     expiration unless otherwise indicated by the method definition or
    775     explicit cache controls [RFC7234]; all other status codes are not
    776     cacheable by default.
    777 
    778 
    779759Section 6.4.1., paragraph 5:
    780760OLD:
    781761
    782        Note: The original proposal for 300 defined the URI header field
    783        as providing a list of alternative representations, such that it
    784        would be usable for 200, 300, and 406 responses and be transferred
    785        in responses to the HEAD method.  However, lack of deployment and
    786        disagreement over syntax led to both URI and Alternates (a
    787        subsequent proposal) being dropped from this specification.  It is
    788        possible to communicate the list using a set of Link header fields
    789        [RFC5988], each with a relationship of "alternate", though
    790        deployment is a chicken-and-egg problem.
     762       Note: The original proposal for the 300 status code defined the
     763       URI header field as providing a list of alternative
     764       representations, such that it would be usable for 200, 300, and
     765       406 responses and be transferred in responses to the HEAD method.
     766       However, lack of deployment and disagreement over syntax led to
     767       both URI and Alternates (a subsequent proposal) being dropped from
     768       this specification.  It is possible to communicate the list using
     769       a set of Link header fields [RFC5988], each with a relationship of
     770       "alternate", though deployment is a chicken-and-egg problem.
    791771
    792772NEW:
     
    993973    (Section 4.2.1), idempotent (Section 4.2.2), cacheable
    994974    (Section 4.2.3), what semantics are to be associated with the payload
    995     body if any is present in the request, and what refinements the
    996     method makes to header field or status code semantics.  If the new
    997     method is cacheable, its definition ought to describe how, and under
    998     what conditions, a cache can store a response and use it to satisfy a
     975    body if any is present in the request and what refinements the method
     976    makes to header field or status code semantics.  If the new method is
     977    cacheable, its definition ought to describe how, and under what
     978    conditions, a cache can store a response and use it to satisfy a
    999979    subsequent request.  The new method ought to describe whether it can
    1000980    be made conditional (Section 5.2) and, if so, how a server responds
     
    11701150
    11711151
    1172 Section 9.4., paragraph 3:
    1173 OLD:
    1174 
    1175     Since the Referer header field tells a target site about the context
    1176     that resulted in a request, it has the potential to reveal
    1177     information about the user's immediate browsing history and any
    1178     personal information that might be found in the referring resource's
    1179     URI.  Limitations on Referer are described in Section 5.5.2 to
    1180     address some of its security considerations.
    1181 
    1182 NEW:
    1183 
    1184     Since the Referer header field tells a target site about the context
    1185     that resulted in a request, it has the potential to reveal
    1186     information about the user's immediate browsing history and any
    1187     personal information that might be found in the referring resource's
    1188     URI.  Limitations on the Referer header field are described in
    1189     Section 5.5.2 to address some of its security considerations.
    1190 
    1191 
    11921152Section 11.1., paragraph 9:
    11931153OLD:
     
    13171277OLD:
    13181278
    1319     A new requirement has been added that semantics embedded in a URI
    1320     should be disabled when those semantics are inconsistent with the
    1321     request method, since this is a common cause of interoperability
    1322     failure.  (Section 2)
     1279    A new requirement has been added that semantics embedded in a URI be
     1280    disabled when those semantics are inconsistent with the request
     1281    method, since this is a common cause of interoperability failure.
     1282 
     1283    (Section 2)
    13231284
    13241285NEW:
  • draft-ietf-httpbis/latest/auth48/rfc7231.diff.html

    r2659 r2660  
    269269      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    270270      <tr><td><a name="diff0014" /></td></tr>
    271       <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>
    272       <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>
     271      <tr><td class="lineno" valign="top"></td><td class="lblock">   All content-coding values are case<span class="delete">-</span>insensitive and ought to be</td><td> </td><td class="rblock">   All content-coding values are case<span class="insert"> </span>insensitive and ought to be</td><td class="lineno" valign="top"></td></tr>
     272      <tr><td class="lineno" valign="top"></td><td class="left">   registered within the "HTTP Content Coding Registry", as defined in</td><td> </td><td class="right">   registered within the "HTTP Content Coding Registry", as defined in</td><td class="lineno" valign="top"></td></tr>
    273273      <tr><td class="lineno" valign="top"></td><td class="left">   Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)</td><td> </td><td class="right">   Section 8.4.  They are used in the Accept-Encoding (Section 5.3.4)</td><td class="lineno" valign="top"></td></tr>
    274274      <tr><td class="lineno" valign="top"></td><td class="left">   and Content-Encoding (Section 3.1.2.2) header fields.</td><td> </td><td class="right">   and Content-Encoding (Section 3.1.2.2) header fields.</td><td class="lineno" valign="top"></td></tr>
     
    280280      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    281281      <tr><td class="lineno" valign="top"></td><td class="left">      deflate: See Section 4.2.2 of [RFC7230].</td><td> </td><td class="right">      deflate: See Section 4.2.2 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    282       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    283282      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    284283      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 14, line 5</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
     
    382381      <tr><td class="lineno" valign="top"></td><td class="left">   been standardized for use in HTTP.  All such methods ought to be</td><td> </td><td class="right">   been standardized for use in HTTP.  All such methods ought to be</td><td class="lineno" valign="top"></td></tr>
    383382      <tr><td><a name="diff0020" /></td></tr>
    384       <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the <span class="delete">HTTP Method Registry</span> maintained by IANA, as</td><td> </td><td class="rblock">   registered within the <span class="insert">"Hypertext Transfer Protocol (HTTP) Method"</span></td><td class="lineno" valign="top"></td></tr>
    385       <tr><td class="lineno" valign="top"></td><td class="lblock">  defined in Section 8.1.</td><td> </td><td class="rblock"><span class="insert">   registry</span> maintained by IANA, as defined in Section 8.1.</td><td class="lineno" valign="top"></td></tr>
     383      <tr><td class="lineno" valign="top"></td><td class="lblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="delete">Method</span></td><td> </td><td class="rblock">   registered within the "Hypertext Transfer Protocol (HTTP) <span class="insert">Method"</span></td><td class="lineno" valign="top"></td></tr>
     384      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry"</span> maintained by IANA, as defined in Section 8.1.</td><td> </td><td class="rblock"><span class="insert">   registry</span> maintained by IANA, as defined in Section 8.1.</td><td class="lineno" valign="top"></td></tr>
    386385      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    387386      <tr><td class="lineno" valign="top"></td><td class="left">   The set of methods allowed by a target resource can be listed in an</td><td> </td><td class="right">   The set of methods allowed by a target resource can be listed in an</td><td class="lineno" valign="top"></td></tr>
     
    407406      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    408407      <tr><td><a name="diff0021" /></td></tr>
    409       <tr><td class="lineno" valign="top"></td><td class="lblock">   This definition of safe <span class="delete">methods</span> does not prevent an implementation</td><td> </td><td class="rblock">   This definition of safe <span class="insert">method</span> does not prevent an implementation</td><td class="lineno" valign="top"></td></tr>
    410       <tr><td class="lineno" valign="top"></td><td class="lblock">   from including behavior that is potentially harmful, not entirely</td><td> </td><td class="rblock">   from including behavior that is potentially harmful, <span class="insert">that is</span> not</td><td class="lineno" valign="top"></td></tr>
    411       <tr><td class="lineno" valign="top"></td><td class="lblock">   read-only, or <span class="delete">which</span> causes side effects while invoking a safe method.</td><td> </td><td class="rblock">   entirely read-only, or <span class="insert">that</span> causes side effects while invoking a safe</td><td class="lineno" valign="top"></td></tr>
    412       <tr><td class="lineno" valign="top"></td><td class="lblock">   What is important, however, is that the client did not request that</td><td> </td><td class="rblock">   method.  What is important, however, is that the client did not</td><td class="lineno" valign="top"></td></tr>
    413       <tr><td class="lineno" valign="top"></td><td class="lblock">   additional behavior and cannot be held accountable for it.  For</td><td> </td><td class="rblock">   request that additional behavior and cannot be held accountable for</td><td class="lineno" valign="top"></td></tr>
    414       <tr><td class="lineno" valign="top"></td><td class="lblock">   example, most servers append request information to access log files</td><td> </td><td class="rblock">   it.  For example, most servers append request information to access</td><td class="lineno" valign="top"></td></tr>
    415       <tr><td class="lineno" valign="top"></td><td class="lblock">   at the completion of every response, regardless of the method, and</td><td> </td><td class="rblock">   log files at the completion of every response, regardless of the</td><td class="lineno" valign="top"></td></tr>
    416       <tr><td class="lineno" valign="top"></td><td class="lblock">   that is considered safe even though the log storage might become full</td><td> </td><td class="rblock">   method, and that is considered safe even though the log storage might</td><td class="lineno" valign="top"></td></tr>
    417       <tr><td class="lineno" valign="top"></td><td class="lblock">   and crash the server.  Likewise, a safe request initiated by</td><td> </td><td class="rblock">   become full and crash the server.  Likewise, a safe request initiated</td><td class="lineno" valign="top"></td></tr>
    418       <tr><td class="lineno" valign="top"></td><td class="lblock">   selecting an advertisement on the Web will often have the side effect</td><td> </td><td class="rblock">   by selecting an advertisement on the Web will often have the side</td><td class="lineno" valign="top"></td></tr>
    419       <tr><td class="lineno" valign="top"></td><td class="lblock">   of charging an advertising account.</td><td> </td><td class="rblock">   effect of charging an advertising account.</td><td class="lineno" valign="top"></td></tr>
    420       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    421       <tr><td class="lineno" valign="top"></td><td class="left">   Of the request methods defined by this specification, the GET, HEAD,</td><td> </td><td class="right">   Of the request methods defined by this specification, the GET, HEAD,</td><td class="lineno" valign="top"></td></tr>
    422       <tr><td class="lineno" valign="top"></td><td class="left">   OPTIONS, and TRACE methods are defined to be safe.</td><td> </td><td class="right">   OPTIONS, and TRACE methods are defined to be safe.</td><td class="lineno" valign="top"></td></tr>
    423       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    424       <tr><td class="lineno" valign="top"></td><td class="left">   The purpose of distinguishing between safe and unsafe methods is to</td><td> </td><td class="right">   The purpose of distinguishing between safe and unsafe methods is to</td><td class="lineno" valign="top"></td></tr>
    425       <tr><td class="lineno" valign="top"></td><td class="left">   allow automated retrieval processes (spiders) and cache performance</td><td> </td><td class="right">   allow automated retrieval processes (spiders) and cache performance</td><td class="lineno" valign="top"></td></tr>
    426       <tr><td class="lineno" valign="top"></td><td class="left">   optimization (pre-fetching) to work without fear of causing harm.  In</td><td> </td><td class="right">   optimization (pre-fetching) to work without fear of causing harm.  In</td><td class="lineno" valign="top"></td></tr>
    427       <tr><td class="lineno" valign="top"></td><td class="left">   addition, it allows a user agent to apply appropriate constraints on</td><td> </td><td class="right">   addition, it allows a user agent to apply appropriate constraints on</td><td class="lineno" valign="top"></td></tr>
    428       <tr><td class="lineno" valign="top"></td><td class="left">   the automated use of unsafe methods when processing potentially</td><td> </td><td class="right">   the automated use of unsafe methods when processing potentially</td><td class="lineno" valign="top"></td></tr>
    429       <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>
     408      <tr><td class="lineno" valign="top"></td><td class="lblock">   This definition of safe method<span class="delete">s</span> does not prevent an implementation</td><td> </td><td class="rblock">   This definition of safe method does not prevent an implementation</td><td class="lineno" valign="top"></td></tr>
     409      <tr><td class="lineno" valign="top"></td><td class="left">   from including behavior that is potentially harmful, that is not</td><td> </td><td class="right">   from including behavior that is potentially harmful, that is not</td><td class="lineno" valign="top"></td></tr>
     410      <tr><td class="lineno" valign="top"></td><td class="left">   entirely read-only, or that causes side effects while invoking a safe</td><td> </td><td class="right">   entirely read-only, or that causes side effects while invoking a safe</td><td class="lineno" valign="top"></td></tr>
     411      <tr><td class="lineno" valign="top"></td><td class="left">   method.  What is important, however, is that the client did not</td><td> </td><td class="right">   method.  What is important, however, is that the client did not</td><td class="lineno" valign="top"></td></tr>
     412      <tr><td class="lineno" valign="top"></td><td class="left">   request that additional behavior and cannot be held accountable for</td><td> </td><td class="right">   request that additional behavior and cannot be held accountable for</td><td class="lineno" valign="top"></td></tr>
     413      <tr><td class="lineno" valign="top"></td><td class="left">   it.  For example, most servers append request information to access</td><td> </td><td class="right">   it.  For example, most servers append request information to access</td><td class="lineno" valign="top"></td></tr>
     414      <tr><td class="lineno" valign="top"></td><td class="left">   log files at the completion of every response, regardless of the</td><td> </td><td class="right">   log files at the completion of every response, regardless of the</td><td class="lineno" valign="top"></td></tr>
     415      <tr><td class="lineno" valign="top"></td><td class="left">   method, and that is considered safe even though the log storage might</td><td> </td><td class="right">   method, and that is considered safe even though the log storage might</td><td class="lineno" valign="top"></td></tr>
     416      <tr><td class="lineno" valign="top"></td><td class="left">   become full and crash the server.  Likewise, a safe request initiated</td><td> </td><td class="right">   become full and crash the server.  Likewise, a safe request initiated</td><td class="lineno" valign="top"></td></tr>
     417      <tr><td class="lineno" valign="top"></td><td class="left">   by selecting an advertisement on the Web will often have the side</td><td> </td><td class="right">   by selecting an advertisement on the Web will often have the side</td><td class="lineno" valign="top"></td></tr>
     418      <tr><td class="lineno" valign="top"></td><td class="left">   effect of charging an advertising account.</td><td> </td><td class="right">   effect of charging an advertising account.</td><td class="lineno" valign="top"></td></tr>
    430419      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    431420      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 34, line 14</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 34, line 14</em></th><td></td></tr>
     
    563552      <tr><td class="lineno" valign="top"></td><td class="left">   understand the class of any status code, as indicated by the first</td><td> </td><td class="right">   understand the class of any status code, as indicated by the first</td><td class="lineno" valign="top"></td></tr>
    564553      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    565       <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 48, line 14</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 48, line 14</em></th><td></td></tr>
    566       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    567       <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>
    568       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    569       <tr><td class="lineno" valign="top"></td><td class="left">   The status codes listed below are defined in this specification,</td><td> </td><td class="right">   The status codes listed below are defined in this specification,</td><td class="lineno" valign="top"></td></tr>
    570       <tr><td class="lineno" valign="top"></td><td class="left">   Section 4 of [RFC7232], Section 4 of [RFC7233], and Section 3 of</td><td> </td><td class="right">   Section 4 of [RFC7232], Section 4 of [RFC7233], and Section 3 of</td><td class="lineno" valign="top"></td></tr>
    571       <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235].  The reason phrases listed here are only recommendations</td><td> </td><td class="right">   [RFC7235].  The reason phrases listed here are only recommendations</td><td class="lineno" valign="top"></td></tr>
    572       <tr><td class="lineno" valign="top"></td><td class="left">   -- they can be replaced by local equivalents without affecting the</td><td> </td><td class="right">   -- they can be replaced by local equivalents without affecting the</td><td class="lineno" valign="top"></td></tr>
    573       <tr><td class="lineno" valign="top"></td><td class="left">   protocol.</td><td> </td><td class="right">   protocol.</td><td class="lineno" valign="top"></td></tr>
    574       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    575       <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>
    576       <tr><td><a name="diff0029" /></td></tr>
    577       <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>
    578       <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>
    579       <tr><td class="lineno" valign="top"></td><td class="lblock">   unless otherwise indicated by the method definition or explicit cache</td><td> </td><td class="rblock">   expiration unless otherwise indicated by the method definition or</td><td class="lineno" valign="top"></td></tr>
    580       <tr><td class="lineno" valign="top"></td><td class="lblock">   controls [RFC7234]; all other status codes are not cacheable by</td><td> </td><td class="rblock">   explicit cache controls [RFC7234]; all other status codes are not</td><td class="lineno" valign="top"></td></tr>
    581       <tr><td class="lineno" valign="top"></td><td class="lblock">   default.</td><td> </td><td class="rblock">   cacheable by default.</td><td class="lineno" valign="top"></td></tr>
    582       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    583       <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
    584       <tr><td class="lineno" valign="top"></td><td class="left">   | Code | Reason-Phrase                 | Defined in...            |</td><td> </td><td class="right">   | Code | Reason-Phrase                 | Defined in...            |</td><td class="lineno" valign="top"></td></tr>
    585       <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
    586       <tr><td class="lineno" valign="top"></td><td class="left">   | 100  | Continue                      | Section 6.2.1            |</td><td> </td><td class="right">   | 100  | Continue                      | Section 6.2.1            |</td><td class="lineno" valign="top"></td></tr>
    587       <tr><td class="lineno" valign="top"></td><td class="left">   | 101  | Switching Protocols           | Section 6.2.2            |</td><td> </td><td class="right">   | 101  | Switching Protocols           | Section 6.2.2            |</td><td class="lineno" valign="top"></td></tr>
    588       <tr><td class="lineno" valign="top"></td><td class="left">   | 200  | OK                            | Section 6.3.1            |</td><td> </td><td class="right">   | 200  | OK                            | Section 6.3.1            |</td><td class="lineno" valign="top"></td></tr>
    589       <tr><td class="lineno" valign="top"></td><td class="left">   | 201  | Created                       | Section 6.3.2            |</td><td> </td><td class="right">   | 201  | Created                       | Section 6.3.2            |</td><td class="lineno" valign="top"></td></tr>
    590       <tr><td class="lineno" valign="top"></td><td class="left">   | 202  | Accepted                      | Section 6.3.3            |</td><td> </td><td class="right">   | 202  | Accepted                      | Section 6.3.3            |</td><td class="lineno" valign="top"></td></tr>
    591       <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>
    592       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    593       <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
     554      <tr bgcolor="gray" ><td></td><th><a name="part-l17" /><small>skipping to change at</small><em> page 56, line 6</em></th><th> </th><th><a name="part-r17" /><small>skipping to change at</small><em> page 56, line 6</em></th><td></td></tr>
    594555      <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>
    595556      <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>
     
    602563      <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>
    603564      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    604       <tr><td><a name="diff0030" /></td></tr>
    605       <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>
    606       <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>
    607       <tr><td class="lineno" valign="top"></td><td class="lblock">      would be usable for 200, 300, and 406 responses and be transferred</td><td> </td><td class="rblock">      such that it would be usable for 200, 300, and 406 responses and</td><td class="lineno" valign="top"></td></tr>
    608       <tr><td class="lineno" valign="top"></td><td class="lblock">      in responses to the HEAD method.  However, lack of deployment and</td><td> </td><td class="rblock">      be transferred in responses to the HEAD method.  However, lack of</td><td class="lineno" valign="top"></td></tr>
    609       <tr><td class="lineno" valign="top"></td><td class="lblock">      disagreement over syntax led to both URI and Alternates (a</td><td> </td><td class="rblock">      deployment and disagreement over syntax led to both URI and</td><td class="lineno" valign="top"></td></tr>
    610       <tr><td class="lineno" valign="top"></td><td class="lblock">      subsequent proposal) being dropped from this specification.  It is</td><td> </td><td class="rblock">      Alternates (a subsequent proposal) being dropped from this</td><td class="lineno" valign="top"></td></tr>
    611       <tr><td class="lineno" valign="top"></td><td class="lblock">      possible to communicate the list using a set of Link header fields</td><td> </td><td class="rblock">      specification.  It is possible to communicate the list using a set</td><td class="lineno" valign="top"></td></tr>
    612       <tr><td class="lineno" valign="top"></td><td class="lblock">      [RFC5988], each with a relationship of "alternate", though</td><td> </td><td class="rblock">      of Link header fields [RFC5988], each with a relationship of</td><td class="lineno" valign="top"></td></tr>
    613       <tr><td class="lineno" valign="top"></td><td class="lblock">      deployment is a chicken-and-egg problem.</td><td> </td><td class="rblock">      "alternate", though deployment is a chicken-and-egg problem.</td><td class="lineno" valign="top"></td></tr>
     565      <tr><td><a name="diff0029" /></td></tr>
     566      <tr><td class="lineno" valign="top"></td><td class="lblock">      Note: The original proposal for the 300 <span class="delete">status code</span> defined the</td><td> </td><td class="rblock">      Note: The original proposal for the 300 <span class="insert">response</span> defined the URI</td><td class="lineno" valign="top"></td></tr>
     567      <tr><td class="lineno" valign="top"></td><td class="lblock">      URI header field as providing a list of alternative</td><td> </td><td class="rblock">      header field as providing a list of alternative representations,</td><td class="lineno" valign="top"></td></tr>
     568      <tr><td class="lineno" valign="top"></td><td class="lblock">      representations, such that it would be usable for 200, 300, and</td><td> </td><td class="rblock">      such that it would be usable for 200, 300, and 406 responses and</td><td class="lineno" valign="top"></td></tr>
     569      <tr><td class="lineno" valign="top"></td><td class="lblock">      406 responses and be transferred in responses to the HEAD method.</td><td> </td><td class="rblock">      be transferred in responses to the HEAD method.  However, lack of</td><td class="lineno" valign="top"></td></tr>
     570      <tr><td class="lineno" valign="top"></td><td class="lblock">      However, lack of deployment and disagreement over syntax led to</td><td> </td><td class="rblock">      deployment and disagreement over syntax led to both URI and</td><td class="lineno" valign="top"></td></tr>
     571      <tr><td class="lineno" valign="top"></td><td class="lblock">      both URI and Alternates (a subsequent proposal) being dropped from</td><td> </td><td class="rblock">      Alternates (a subsequent proposal) being dropped from this</td><td class="lineno" valign="top"></td></tr>
     572      <tr><td class="lineno" valign="top"></td><td class="lblock">      this specification.  It is possible to communicate the list using</td><td> </td><td class="rblock">      specification.  It is possible to communicate the list using a set</td><td class="lineno" valign="top"></td></tr>
     573      <tr><td class="lineno" valign="top"></td><td class="lblock">      a set of Link header fields [RFC5988], each with a relationship of</td><td> </td><td class="rblock">      of Link header fields [RFC5988], each with a relationship of</td><td class="lineno" valign="top"></td></tr>
     574      <tr><td class="lineno" valign="top"></td><td class="left">      "alternate", though deployment is a chicken-and-egg problem.</td><td> </td><td class="right">      "alternate", though deployment is a chicken-and-egg problem.</td><td class="lineno" valign="top"></td></tr>
    614575      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    615576      <tr><td class="lineno" valign="top"></td><td class="left">6.4.2.  301 Moved Permanently</td><td> </td><td class="right">6.4.2.  301 Moved Permanently</td><td class="lineno" valign="top"></td></tr>
     
    621582      <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>
    622583      <tr><td class="lineno" valign="top"></td><td class="left">   references sent by the server, where possible.</td><td> </td><td class="right">   references sent by the server, where possible.</td><td class="lineno" valign="top"></td></tr>
    623       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    624       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    625       <tr bgcolor="gray" ><td></td><th><a name="part-l19" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r19" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
     584      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     585      <tr bgcolor="gray" ><td></td><th><a name="part-l18" /><small>skipping to change at</small><em> page 58, line 23</em></th><th> </th><th><a name="part-r18" /><small>skipping to change at</small><em> page 58, line 23</em></th><td></td></tr>
    626586      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    627587      <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>