Changeset 2635


Ignore:
Timestamp:
May 6, 2014, 4:47:46 AM (6 years ago)
Author:
julian.reschke@…
Message:

insert RFC number for status code 308 (#553)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p2-semantics.unpg.txt

    r2633 r2635  
    250250     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89
    251251     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89
    252      A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 90
     252     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89
    253253     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90
    254254     A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90
     
    32693269      does not allow changing the request method from POST to GET.  This
    32703270      specification defines no equivalent counterpart for 301 (Moved
    3271       Permanently) ([status-308], however, defines the status code 308
     3271      Permanently) ([RFC7238], however, defines the status code 308
    32723272      (Permanent Redirect) for this purpose).
    32733273
     
    4819481911.1.  Normative References
    48204820
    4821    [RFC2045]     Freed, N. and N. Borenstein, "Multipurpose Internet
    4822                  Mail Extensions (MIME) Part One: Format of Internet
    4823                  Message Bodies", RFC 2045, November 1996.
    4824 
    4825    [RFC2046]     Freed, N. and N. Borenstein, "Multipurpose Internet
    4826                  Mail Extensions (MIME) Part Two: Media Types",
    4827                  RFC 2046, November 1996.
    4828 
    4829    [RFC2119]     Bradner, S., "Key words for use in RFCs to Indicate
    4830                  Requirement Levels", BCP 14, RFC 2119, March 1997.
    4831 
    4832    [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,
    4833                  "Uniform Resource Identifier (URI): Generic Syntax",
    4834                  STD 66, RFC 3986, January 2005.
    4835 
    4836    [RFC4647]     Phillips, A., Ed. and M. Davis, Ed., "Matching of
    4837                  Language Tags", BCP 47, RFC 4647, September 2006.
    4838 
    4839    [RFC5234]     Crocker, D., Ed. and P. Overell, "Augmented BNF for
     4821   [RFC2045]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
     4822              Extensions (MIME) Part One: Format of Internet Message
     4823              Bodies", RFC 2045, November 1996.
     4824
     4825   [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
     4826              Extensions (MIME) Part Two: Media Types", RFC 2046,
     4827              November 1996.
     4828
     4829   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
     4830              Requirement Levels", BCP 14, RFC 2119, March 1997.
     4831
     4832   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
     4833              Resource Identifier (URI): Generic Syntax", STD 66,
     4834              RFC 3986, January 2005.
     4835
     4836   [RFC4647]  Phillips, A., Ed. and M. Davis, Ed., "Matching of Language
     4837              Tags", BCP 47, RFC 4647, September 2006.
     4838
     4839   [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
    48404840
    48414841
     
    48474847
    48484848
    4849                  Syntax Specifications: ABNF", STD 68, RFC 5234,
    4850                  January 2008.
    4851 
    4852    [RFC5646]     Phillips, A., Ed. and M. Davis, Ed., "Tags for
    4853                  Identifying Languages", BCP 47, RFC 5646,
    4854                  September 2009.
    4855 
    4856    [RFC6365]     Hoffman, P. and J. Klensin, "Terminology Used in
    4857                  Internationalization in the IETF", BCP 166, RFC 6365,
    4858                  September 2011.
    4859 
    4860    [RFC7230]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    4861                  Transfer Protocol (HTTP/1.1): Message Syntax and
    4862                  Routing", draft-ietf-httpbis-p1-messaging-latest (work
    4863                  in progress), May 2014.
    4864 
    4865    [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    4866                  Transfer Protocol (HTTP/1.1): Conditional Requests",
    4867                  draft-ietf-httpbis-p4-conditional-latest (work in
    4868                  progress), May 2014.
    4869 
    4870    [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
    4871                  "Hypertext Transfer Protocol (HTTP/1.1): Range
    4872                  Requests", draft-ietf-httpbis-p5-range-latest (work in
    4873                  progress), May 2014.
    4874 
    4875    [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
    4876                  Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
    4877                  draft-ietf-httpbis-p6-cache-latest (work in progress),
    4878                  May 2014.
    4879 
    4880    [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    4881                  Transfer Protocol (HTTP/1.1): Authentication",
    4882                  draft-ietf-httpbis-p7-auth-latest (work in progress),
    4883                  May 2014.
     4849              Specifications: ABNF", STD 68, RFC 5234, January 2008.
     4850
     4851   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
     4852              Languages", BCP 47, RFC 5646, September 2009.
     4853
     4854   [RFC6365]  Hoffman, P. and J. Klensin, "Terminology Used in
     4855              Internationalization in the IETF", BCP 166, RFC 6365,
     4856              September 2011.
     4857
     4858   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     4859              Protocol (HTTP/1.1): Message Syntax and Routing",
     4860              draft-ietf-httpbis-p1-messaging-latest (work in progress),
     4861              May 2014.
     4862
     4863   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     4864              Protocol (HTTP/1.1): Conditional Requests",
     4865              draft-ietf-httpbis-p4-conditional-latest (work in
     4866              progress), May 2014.
     4867
     4868   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
     4869              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
     4870              draft-ietf-httpbis-p5-range-latest (work in progress),
     4871              May 2014.
     4872
     4873   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
     4874              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
     4875              draft-ietf-httpbis-p6-cache-latest (work in progress),
     4876              May 2014.
     4877
     4878   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     4879              Protocol (HTTP/1.1): Authentication",
     4880              draft-ietf-httpbis-p7-auth-latest (work in progress),
     4881              May 2014.
    48844882
    4885488311.2.  Informative References
    48864884
    4887    [BCP13]       Freed, N., Klensin, J., and T. Hansen, "Media Type
    4888                  Specifications and Registration Procedures", BCP 13,
    4889                  RFC 6838, January 2013.
    4890 
    4891    [BCP178]      Saint-Andre, P., Crocker, D., and M. Nottingham,
    4892                  "Deprecating the "X-" Prefix and Similar Constructs in
    4893                  Application Protocols", BCP 178, RFC 6648, June 2012.
    4894 
    4895    [BCP90]       Klyne, G., Nottingham, M., and J. Mogul, "Registration
    4896                  Procedures for Message Header Fields", BCP 90,
     4885   [BCP13]    Freed, N., Klensin, J., and T. Hansen, "Media Type
     4886              Specifications and Registration Procedures", BCP 13,
     4887              RFC 6838, January 2013.
     4888
     4889   [BCP178]   Saint-Andre, P., Crocker, D., and M. Nottingham,
     4890              "Deprecating the "X-" Prefix and Similar Constructs in
     4891              Application Protocols", BCP 178, RFC 6648, June 2012.
     4892
     4893   [BCP90]    Klyne, G., Nottingham, M., and J. Mogul, "Registration
     4894              Procedures for Message Header Fields", BCP 90, RFC 3864,
     4895              September 2004.
     4896
    48974897
    48984898
     
    49044904
    49054905
    4906                  RFC 3864, September 2004.
    4907 
    4908    [OWASP]       van der Stock, A., Ed., "A Guide to Building Secure Web
    4909                  Applications and Web Services", The Open Web
    4910                  Application Security Project (OWASP) 2.0.1, July 2005,
    4911                  <https://www.owasp.org/>.
    4912 
    4913    [REST]        Fielding, R., "Architectural Styles and the Design of
    4914                  Network-based Software Architectures",
    4915                  Doctoral Dissertation, University of California,
    4916                  Irvine, September 2000,
    4917                  <http://roy.gbiv.com/pubs/dissertation/top.htm>.
    4918 
    4919    [RFC1945]     Berners-Lee, T., Fielding, R., and H. Nielsen,
    4920                  "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945,
    4921                  May 1996.
    4922 
    4923    [RFC2049]     Freed, N. and N. Borenstein, "Multipurpose Internet
    4924                  Mail Extensions (MIME) Part Five: Conformance Criteria
    4925                  and Examples", RFC 2049, November 1996.
    4926 
    4927    [RFC2068]     Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and
    4928                  T. Berners-Lee, "Hypertext Transfer Protocol --
    4929                  HTTP/1.1", RFC 2068, January 1997.
    4930 
    4931    [RFC2295]     Holtman, K. and A. Mutz, "Transparent Content
    4932                  Negotiation in HTTP", RFC 2295, March 1998.
    4933 
    4934    [RFC2388]     Masinter, L., "Returning Values from Forms:  multipart/
    4935                  form-data", RFC 2388, August 1998.
    4936 
    4937    [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,
    4938                  "MIME Encapsulation of Aggregate Documents, such as
    4939                  HTML (MHTML)", RFC 2557, March 1999.
    4940 
    4941    [RFC2616]     Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
    4942                  Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
    4943                  Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
    4944 
    4945    [RFC2774]     Frystyk, H., Leach, P., and S. Lawrence, "An HTTP
    4946                  Extension Framework", RFC 2774, February 2000.
    4947 
    4948    [RFC2817]     Khare, R. and S. Lawrence, "Upgrading to TLS Within
    4949                  HTTP/1.1", RFC 2817, May 2000.
    4950 
    4951    [RFC2978]     Freed, N. and J. Postel, "IANA Charset Registration
    4952                  Procedures", BCP 19, RFC 2978, October 2000.
    4953 
     4906   [OWASP]    van der Stock, A., Ed., "A Guide to Building Secure Web
     4907              Applications and Web Services", The Open Web Application
     4908              Security Project (OWASP) 2.0.1, July 2005,
     4909              <https://www.owasp.org/>.
     4910
     4911   [REST]     Fielding, R., "Architectural Styles and the Design of
     4912              Network-based Software Architectures",
     4913              Doctoral Dissertation, University of California, Irvine,
     4914              September 2000,
     4915              <http://roy.gbiv.com/pubs/dissertation/top.htm>.
     4916
     4917   [RFC1945]  Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext
     4918              Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.
     4919
     4920   [RFC2049]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
     4921              Extensions (MIME) Part Five: Conformance Criteria and
     4922              Examples", RFC 2049, November 1996.
     4923
     4924   [RFC2068]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
     4925              Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
     4926              RFC 2068, January 1997.
     4927
     4928   [RFC2295]  Holtman, K. and A. Mutz, "Transparent Content Negotiation
     4929              in HTTP", RFC 2295, March 1998.
     4930
     4931   [RFC2388]  Masinter, L., "Returning Values from Forms:  multipart/
     4932              form-data", RFC 2388, August 1998.
     4933
     4934   [RFC2557]  Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,
     4935              "MIME Encapsulation of Aggregate Documents, such as HTML
     4936              (MHTML)", RFC 2557, March 1999.
     4937
     4938   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
     4939              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
     4940              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
     4941
     4942   [RFC2774]  Frystyk, H., Leach, P., and S. Lawrence, "An HTTP
     4943              Extension Framework", RFC 2774, February 2000.
     4944
     4945   [RFC2817]  Khare, R. and S. Lawrence, "Upgrading to TLS Within
     4946              HTTP/1.1", RFC 2817, May 2000.
     4947
     4948   [RFC2978]  Freed, N. and J. Postel, "IANA Charset Registration
     4949              Procedures", BCP 19, RFC 2978, October 2000.
     4950
     4951   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
     4952              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
     4953              May 2008.
    49544954
    49554955
     
    49614961
    49624962
    4963    [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing
    4964                  an IANA Considerations Section in RFCs", BCP 26,
    4965                  RFC 5226, May 2008.
    4966 
    4967    [RFC5246]     Dierks, T. and E. Rescorla, "The Transport Layer
    4968                  Security (TLS) Protocol Version 1.2", RFC 5246,
    4969                  August 2008.
    4970 
    4971    [RFC5322]     Resnick, P., "Internet Message Format", RFC 5322,
    4972                  October 2008.
    4973 
    4974    [RFC5789]     Dusseault, L. and J. Snell, "PATCH Method for HTTP",
    4975                  RFC 5789, March 2010.
    4976 
    4977    [RFC5905]     Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
    4978                  "Network Time Protocol Version 4: Protocol and
    4979                  Algorithms Specification", RFC 5905, June 2010.
    4980 
    4981    [RFC5987]     Reschke, J., "Character Set and Language Encoding for
    4982                  Hypertext Transfer Protocol (HTTP) Header Field
    4983                  Parameters", RFC 5987, August 2010.
    4984 
    4985    [RFC5988]     Nottingham, M., "Web Linking", RFC 5988, October 2010.
    4986 
    4987    [RFC6265]     Barth, A., "HTTP State Management Mechanism", RFC 6265,
    4988                  April 2011.
    4989 
    4990    [RFC6266]     Reschke, J., "Use of the Content-Disposition Header
    4991                  Field in the Hypertext Transfer Protocol (HTTP)",
    4992                  RFC 6266, June 2011.
    4993 
    4994    [status-308]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
    4995                  Status Code 308 (Permanent Redirect)",
    4996                  draft-reschke-http-status-308-07 (work in progress),
    4997                  March 2012.
     4963   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
     4964              (TLS) Protocol Version 1.2", RFC 5246, August 2008.
     4965
     4966   [RFC5322]  Resnick, P., "Internet Message Format", RFC 5322,
     4967              October 2008.
     4968
     4969   [RFC5789]  Dusseault, L. and J. Snell, "PATCH Method for HTTP",
     4970              RFC 5789, March 2010.
     4971
     4972   [RFC5905]  Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
     4973              "Network Time Protocol Version 4: Protocol and Algorithms
     4974              Specification", RFC 5905, June 2010.
     4975
     4976   [RFC5987]  Reschke, J., "Character Set and Language Encoding for
     4977              Hypertext Transfer Protocol (HTTP) Header Field
     4978              Parameters", RFC 5987, August 2010.
     4979
     4980   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.
     4981
     4982   [RFC6265]  Barth, A., "HTTP State Management Mechanism", RFC 6265,
     4983              April 2011.
     4984
     4985   [RFC6266]  Reschke, J., "Use of the Content-Disposition Header Field
     4986              in the Hypertext Transfer Protocol (HTTP)", RFC 6266,
     4987              June 2011.
     4988
     4989   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
     4990              Status Code 308 (Permanent Redirect)",
     4991              draft-reschke-http-status-308-07 (work in progress),
     4992              March 2012.
    49984993
    49994994Appendix A.  Differences between HTTP and MIME
     
    50095004   greater freedom in the use of new media types, to make date
    50105005   comparisons easier, and to acknowledge the practice of some early
    5011 
    5012 
    5013 
    5014 Fielding & Reschke      Expires November 7, 2014               [Page 88]
    5015 
    5016 
    5017 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5018 
    5019 
    50205006   HTTP servers and clients.
    50215007
     
    50235009   Proxies and gateways to and from strict MIME environments need to be
    50245010   aware of these differences and provide the appropriate conversions
     5011
     5012
     5013
     5014Fielding & Reschke      Expires November 7, 2014               [Page 88]
     5015
     5016
     5017Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5018
     5019
    50255020   where necessary.
    50265021
     
    50675062   date if necessary.
    50685063
    5069 
    5070 
    5071 Fielding & Reschke      Expires November 7, 2014               [Page 89]
    5072 
    5073 
    5074 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5075 
    5076 
    50775064A.4.  Conversion of Content-Encoding
    50785065
    50795066   MIME does not include any concept equivalent to HTTP/1.1's Content-
    50805067   Encoding header field.  Since this acts as a modifier on the media
     5068
     5069
     5070
     5071Fielding & Reschke      Expires November 7, 2014               [Page 89]
     5072
     5073
     5074Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5075
     5076
    50815077   type, proxies and gateways from HTTP to MIME-compliant protocols
    50825078   ought to either change the value of the Content-Type header field or
     
    51245120   representations and representations from resources.
    51255121
    5126 
    5127 
    5128 Fielding & Reschke      Expires November 7, 2014               [Page 90]
    5129 
    5130 
    5131 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5132 
    5133 
    51345122   A new requirement has been added that semantics embedded in a URI
    51355123   should be disabled when those semantics are inconsistent with the
    51365124   request method, since this is a common cause of interoperability
     5125
     5126
     5127
     5128Fielding & Reschke      Expires November 7, 2014               [Page 90]
     5129
     5130
     5131Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5132
     5133
    51375134   failure.  (Section 2)
    51385135
     
    51805177   The following status codes are now cacheable (that is, they can be
    51815178   stored and reused by a cache without explicit freshness information
     5179   present): 204, 404, 405, 414, 501.  (Section 6)
     5180
     5181   The 201 (Created) status description has been changed to allow for
    51825182
    51835183
     
    51895189
    51905190
    5191    present): 204, 404, 405, 414, 501.  (Section 6)
    5192 
    5193    The 201 (Created) status description has been changed to allow for
    51945191   the possibility that more than one resource has been created.
    51955192   (Section 6.3.2)
     
    52385235   A Method Registry has been defined.  (Section 8.1)
    52395236
    5240 
    5241 
    5242 Fielding & Reschke      Expires November 7, 2014               [Page 92]
    5243 
    5244 
    5245 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5246 
    5247 
    52485237   The Status Code Registry has been redefined by this specification;
    52495238   previously, it was defined in Section 7.1 of [RFC2817].
     5239
     5240
     5241
     5242Fielding & Reschke      Expires November 7, 2014               [Page 92]
     5243
     5244
     5245Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5246
     5247
    52505248   (Section 8.2)
    52515249
     
    52945292   Accept-Language = *( "," OWS ) ( language-range [ weight ] ) *( OWS
    52955293    "," [ OWS ( language-range [ weight ] ) ] )
     5294   Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
     5295
    52965296
    52975297
     
    53025302Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    53035303
    5304 
    5305    Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    53065304
    53075305   BWS = <BWS, defined in [RFC7230], Section 3.2.3>
     
    53515349   charset = token
    53525350   codings = content-coding / "identity" / "*"
    5353 
    5354 
    5355 
    5356 Fielding & Reschke      Expires November 7, 2014               [Page 94]
    5357 
    5358 
    5359 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5360 
    5361 
    53625351   comment = <comment, defined in [RFC7230], Section 3.2.6>
    53635352   content-coding = token
     5353
     5354
     5355
     5356Fielding & Reschke      Expires November 7, 2014               [Page 94]
     5357
     5358
     5359Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5360
    53645361
    53655362   date1 = day SP month SP year
     
    54095406    / %x44.65.63 ; Dec
    54105407
     5408   obs-date = rfc850-date / asctime-date
     5409
     5410
    54115411
    54125412
     
    54165416Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    54175417
    5418 
    5419    obs-date = rfc850-date / asctime-date
    54205418
    54215419   parameter = token "=" ( token / quoted-string )
     
    54655463      200 OK (status code)  51
    54665464      201 Created (status code)  52
    5467 
    5468 
    5469 
    5470 Fielding & Reschke      Expires November 7, 2014               [Page 96]
    5471 
    5472 
    5473 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5474 
    5475 
    54765465      202 Accepted (status code)  52
    54775466      203 Non-Authoritative Information (status code)  52
     5467
     5468
     5469
     5470Fielding & Reschke      Expires November 7, 2014               [Page 96]
     5471
     5472
     5473Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5474
     5475
    54785476      204 No Content (status code)  53
    54795477      205 Reset Content (status code)  53
     
    55225520   C
    55235521      cacheable  24
    5524 
    5525 
    5526 
    5527 Fielding & Reschke      Expires November 7, 2014               [Page 97]
    5528 
    5529 
    5530 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5531 
    5532 
    55335522      compress (content coding)  11
    55345523      conditional request  36
     5524
     5525
     5526
     5527Fielding & Reschke      Expires November 7, 2014               [Page 97]
     5528
     5529
     5530Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5531
     5532
    55355533      CONNECT method  30
    55365534      content coding  11
     
    55795577         Expect  34
    55805578         From  44
    5581 
    5582 
    5583 
    5584 Fielding & Reschke      Expires November 7, 2014               [Page 98]
    5585 
    5586 
    5587 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5588 
    5589 
    55905579         GMT  66
    55915580         hour  66
     5581
     5582
     5583
     5584Fielding & Reschke      Expires November 7, 2014               [Page 98]
     5585
     5586
     5587Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5588
     5589
    55925590         HTTP-date  64
    55935591         IMF-fixdate  66
     
    56365634      OPTIONS method  31
    56375635
    5638 
    5639 
    5640 
    5641 Fielding & Reschke      Expires November 7, 2014               [Page 99]
    5642 
    5643 
    5644 Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
    5645 
    5646 
    56475636   P
    56485637      payload  17
     5638
     5639
     5640
     5641Fielding & Reschke      Expires November 7, 2014               [Page 99]
     5642
     5643
     5644Internet-Draft       HTTP/1.1 Semantics and Content             May 2014
     5645
     5646
    56495647      POST method  25
    56505648      PUT method  26
     
    56965694
    56975695
     5696
     5697
    56985698Fielding & Reschke      Expires November 7, 2014              [Page 100]
    56995699
  • draft-ietf-httpbis/latest/auth48/rfc7231.abdiff.txt

    r2633 r2635  
    235235      A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89
    236236      A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89
    237       A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 90
     237      A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89
    238238      A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90
    239239      A.6.  MHTML and Line Length Limitations  . . . . . . . . . . . . 90
     
    15391539       does not allow changing the request method from POST to GET.  This
    15401540       specification defines no equivalent counterpart for 301 (Moved
    1541        Permanently) ([status-308], however, defines the status code 308
     1541       Permanently) ([RFC7238], however, defines the status code 308
    15421542       (Permanent Redirect) for this purpose).
    15431543
     
    21322132
    21332133
    2134 Section 11.1., paragraph 1:
    2135 OLD:
    2136 
    2137     [RFC2045]     Freed, N. and N. Borenstein, "Multipurpose Internet
    2138                   Mail Extensions (MIME) Part One: Format of Internet
    2139                   Message Bodies", RFC 2045, November 1996.
    2140 
    2141 NEW:
    2142 
    2143     [RFC2045]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
    2144                Extensions (MIME) Part One: Format of Internet Message
    2145                Bodies", RFC 2045, November 1996.
    2146 
    2147 
    2148 Section 11.1., paragraph 2:
    2149 OLD:
    2150 
    2151     [RFC2046]     Freed, N. and N. Borenstein, "Multipurpose Internet
    2152                   Mail Extensions (MIME) Part Two: Media Types",
    2153                   RFC 2046, November 1996.
    2154 
    2155 NEW:
    2156 
    2157     [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
    2158                Extensions (MIME) Part Two: Media Types", RFC 2046,
    2159                November 1996.
    2160 
    2161 
    2162 Section 11.1., paragraph 4:
    2163 OLD:
    2164 
    2165     [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,
    2166                   "Uniform Resource Identifier (URI): Generic Syntax",
    2167                   STD 66, RFC 3986, January 2005.
    2168 
    2169 NEW:
    2170 
    2171     [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
    2172                Resource Identifier (URI): Generic Syntax", STD 66,
    2173                RFC 3986, January 2005.
    2174 
    2175 
    2176 Section 11.1., paragraph 5:
    2177 OLD:
    2178 
    2179     [RFC4647]     Phillips, A., Ed. and M. Davis, Ed., "Matching of
    2180                   Language Tags", BCP 47, RFC 4647, September 2006.
    2181 
    2182 NEW:
    2183 
    2184     [RFC4647]  Phillips, A., Ed. and M. Davis, Ed., "Matching of Language
    2185                Tags", BCP 47, RFC 4647, September 2006.
    2186 
    2187 
    2188 Section 11.1., paragraph 6:
    2189 OLD:
    2190 
    2191     [RFC5234]     Crocker, D., Ed. and P. Overell, "Augmented BNF for
    2192                   Syntax Specifications: ABNF", STD 68, RFC 5234,
    2193                   January 2008.
    2194 
    2195 NEW:
    2196 
    2197     [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
    2198                Specifications: ABNF", STD 68, RFC 5234, January 2008.
    2199 
    2200 
    2201 Section 11.1., paragraph 7:
    2202 OLD:
    2203 
    2204     [RFC5646]     Phillips, A., Ed. and M. Davis, Ed., "Tags for
    2205                   Identifying Languages", BCP 47, RFC 5646,
    2206                   September 2009.
    2207 
    2208 NEW:
    2209 
    2210     [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
    2211                Languages", BCP 47, RFC 5646, September 2009.
    2212 
    2213 
    22142134Section 11.1., paragraph 9:
    22152135OLD:
    22162136
    2217     [RFC7230]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    2218                   Transfer Protocol (HTTP/1.1): Message Syntax and
    2219                   Routing", draft-ietf-httpbis-p1-messaging-latest (work
    2220                   in progress), May 2014.
     2137    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     2138               Protocol (HTTP/1.1): Message Syntax and Routing",
     2139               draft-ietf-httpbis-p1-messaging-latest (work in progress),
     2140               May 2014.
    22212141
    22222142NEW:
     
    22302150OLD:
    22312151
    2232     [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    2233                   Transfer Protocol (HTTP/1.1): Conditional Requests",
    2234                   draft-ietf-httpbis-p4-conditional-latest (work in
    2235                   progress), May 2014.
     2152    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     2153               Protocol (HTTP/1.1): Conditional Requests",
     2154               draft-ietf-httpbis-p4-conditional-latest (work in
     2155               progress), May 2014.
    22362156
    22372157NEW:
     
    22452165OLD:
    22462166
    2247     [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
    2248                   "Hypertext Transfer Protocol (HTTP/1.1): Range
    2249                   Requests", draft-ietf-httpbis-p5-range-latest (work in
    2250                   progress), May 2014.
    2251 
    2252 NEW:
    2253 
    2254     [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
     2167    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
     2168               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
     2169               draft-ietf-httpbis-p5-range-latest (work in progress),
     2170               May 2014.
     2171
     2172NEW:
     2173
     2174    [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
    22552175               "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
    22562176               RFC 7233, May 2014.
     
    22602180OLD:
    22612181
    2262     [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
    2263                   Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
    2264                   draft-ietf-httpbis-p6-cache-latest (work in progress),
    2265                   May 2014.
    2266 
    2267 NEW:
    2268 
    2269     [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
    2270                   Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
     2182    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
     2183               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
     2184               draft-ietf-httpbis-p6-cache-latest (work in progress),
     2185               May 2014.
     2186
     2187NEW:
     2188
     2189    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
     2190               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
    22712191               RFC 7234, May 2014.
    22722192
     
    22752195OLD:
    22762196
    2277     [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext
    2278                   Transfer Protocol (HTTP/1.1): Authentication",
    2279                   draft-ietf-httpbis-p7-auth-latest (work in progress),
    2280                   May 2014.
     2197    [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
     2198               Protocol (HTTP/1.1): Authentication",
     2199               draft-ietf-httpbis-p7-auth-latest (work in progress),
     2200               May 2014.
    22812201
    22822202NEW:
     
    22862206
    22872207
    2288 Section 11.2., paragraph 3:
    2289 OLD:
    2290 
    2291     [BCP90]       Klyne, G., Nottingham, M., and J. Mogul, "Registration
    2292                   Procedures for Message Header Fields", BCP 90,
    2293                   RFC 3864, September 2004.
    2294 
    2295 NEW:
    2296 
    2297     [BCP90]       Klyne, G., Nottingham, M., and J. Mogul, "Registration
    2298                Procedures for Message Header Fields", BCP 90, RFC 3864,
    2299                September 2004.
    2300 
    2301 
    2302 Section 11.2., paragraph 4:
    2303 OLD:
    2304 
    2305     [OWASP]       van der Stock, A., Ed., "A Guide to Building Secure Web
    2306                   Applications and Web Services", The Open Web
    2307                   Application Security Project (OWASP) 2.0.1, July 2005,
    2308                   <https://www.owasp.org/>.
    2309 
    2310 NEW:
    2311 
    2312     [OWASP]       van der Stock, A., Ed., "A Guide to Building Secure Web
    2313                Applications and Web Services", The Open Web Application
    2314                Security Project (OWASP) 2.0.1, July 2005,
    2315                   <https://www.owasp.org/>.
    2316 
    2317 
    2318 Section 11.2., paragraph 5:
    2319 OLD:
    2320 
    2321     [REST]        Fielding, R., "Architectural Styles and the Design of
    2322                   Network-based Software Architectures",
    2323                   Doctoral Dissertation, University of California,
    2324                   Irvine, September 2000,
    2325                   <http://roy.gbiv.com/pubs/dissertation/top.htm>.
    2326 
    2327 NEW:
    2328 
    2329     [REST]        Fielding, R., "Architectural Styles and the Design of
    2330                   Network-based Software Architectures",
    2331                Doctoral Dissertation, University of California, Irvine,
    2332                September 2000,
    2333                   <http://roy.gbiv.com/pubs/dissertation/top.htm>.
    2334 
    2335 
    2336 Section 11.2., paragraph 6:
    2337 OLD:
    2338 
    2339     [RFC1945]     Berners-Lee, T., Fielding, R., and H. Nielsen,
    2340                   "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945,
    2341                   May 1996.
    2342 
    2343 NEW:
    2344 
    2345     [RFC1945]  Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext
    2346                Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.
    2347 
    2348 
    2349 Section 11.2., paragraph 7:
    2350 OLD:
    2351 
    2352     [RFC2049]     Freed, N. and N. Borenstein, "Multipurpose Internet
    2353                   Mail Extensions (MIME) Part Five: Conformance Criteria
    2354                   and Examples", RFC 2049, November 1996.
    2355 
    2356 NEW:
    2357 
    2358     [RFC2049]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
    2359                Extensions (MIME) Part Five: Conformance Criteria and
    2360                Examples", RFC 2049, November 1996.
    2361 
    2362 
    2363 Section 11.2., paragraph 8:
    2364 OLD:
    2365 
    2366     [RFC2068]     Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and
    2367                   T. Berners-Lee, "Hypertext Transfer Protocol --
    2368                   HTTP/1.1", RFC 2068, January 1997.
    2369 
    2370 NEW:
    2371 
    2372     [RFC2068]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
    2373                Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
    2374                RFC 2068, January 1997.
    2375 
    2376 
    2377 Section 11.2., paragraph 9:
    2378 OLD:
    2379 
    2380     [RFC2295]     Holtman, K. and A. Mutz, "Transparent Content
    2381                   Negotiation in HTTP", RFC 2295, March 1998.
    2382 
    2383 NEW:
    2384 
    2385     [RFC2295]  Holtman, K. and A. Mutz, "Transparent Content Negotiation
    2386                in HTTP", RFC 2295, March 1998.
    2387 
    2388 
    2389 Section 11.2., paragraph 11:
    2390 OLD:
    2391 
    2392     [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,
    2393                   "MIME Encapsulation of Aggregate Documents, such as
    2394                   HTML (MHTML)", RFC 2557, March 1999.
    2395 
    2396 NEW:
    2397 
    2398     [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,
    2399                "MIME Encapsulation of Aggregate Documents, such as HTML
    2400                (MHTML)", RFC 2557, March 1999.
    2401 
    2402 
    2403 Section 11.2., paragraph 16:
    2404 OLD:
    2405 
    2406     [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing
    2407                   an IANA Considerations Section in RFCs", BCP 26,
    2408                   RFC 5226, May 2008.
    2409 
    2410 NEW:
    2411 
    2412     [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
    2413                IANA Considerations Section in RFCs", BCP 26, RFC 5226,
    2414                May 2008.
    2415 
    2416 
    2417 Section 11.2., paragraph 17:
    2418 OLD:
    2419 
    2420     [RFC5246]     Dierks, T. and E. Rescorla, "The Transport Layer
    2421                   Security (TLS) Protocol Version 1.2", RFC 5246,
    2422                   August 2008.
    2423 
    2424 NEW:
    2425 
    2426     [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
    2427                (TLS) Protocol Version 1.2", RFC 5246, August 2008.
    2428 
    2429 
    2430 Section 11.2., paragraph 20:
    2431 OLD:
    2432 
    2433     [RFC5905]     Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
    2434                   "Network Time Protocol Version 4: Protocol and
    2435                   Algorithms Specification", RFC 5905, June 2010.
    2436 
    2437 NEW:
    2438 
    2439     [RFC5905]     Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
    2440                "Network Time Protocol Version 4: Protocol and Algorithms
    2441                Specification", RFC 5905, June 2010.
    2442 
    2443 
    2444 Section 11.2., paragraph 24:
    2445 OLD:
    2446 
    2447     [RFC6266]     Reschke, J., "Use of the Content-Disposition Header
    2448                   Field in the Hypertext Transfer Protocol (HTTP)",
    2449                   RFC 6266, June 2011.
    2450 
    2451 NEW:
    2452 
    2453     [RFC6266]  Reschke, J., "Use of the Content-Disposition Header Field
    2454                in the Hypertext Transfer Protocol (HTTP)", RFC 6266,
    2455                June 2011.
    2456 
    2457 
    24582208Section 11.2., paragraph 25:
    24592209OLD:
    24602210
    2461     [status-308]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
    2462                   Status Code 308 (Permanent Redirect)",
    2463                   draft-reschke-http-status-308-07 (work in progress),
    2464                   March 2012.
     2211    [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)
     2212               Status Code 308 (Permanent Redirect)",
     2213               draft-reschke-http-status-308-07 (work in progress),
     2214               March 2012.
    24652215
    24662216NEW:
     
    28622612    content of Allow have been relaxed; correspondingly, clients are not
    28632613    required to always trust its value (Section 7.4.1).
    2864  
     2614
     2615
     2616Appendix B., paragraph 25:
     2617OLD:
     2618
     2619    A Method Registry has been defined.  (Section 8.1)
     2620
     2621NEW:
     2622
    28652623    A Method Registry has been defined (Section 8.1).
    28662624
    28672625
    2868 Appendix B., paragraph 25:
    2869 OLD:
    2870 
    2871     A Method Registry has been defined.  (Section 8.1)
     2626Appendix B., paragraph 26:
     2627OLD:
     2628
    28722629    The Status Code Registry has been redefined by this specification;
    28732630    previously, it was defined in Section 7.1 of [RFC2817].
     2631 
    28742632    (Section 8.2)
    28752633
     
    28802638
    28812639
    2882 Appendix B., paragraph 26:
     2640Appendix B., paragraph 27:
    28832641OLD:
    28842642
     
    28942652Section 1.2, paragraph 1:
    28952653OLD:
    2896 
    2897     Accept = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
    2898      OWS ( media-range [ accept-params ] ) ] ) ]
    2899     Accept-Charset = *( "," OWS ) ( ( charset / "*" ) [ weight ] ) *( OWS
    2900      "," [ OWS ( ( charset / "*" ) [ weight ] ) ] )
    2901     Accept-Encoding = [ ( "," / ( codings [ weight ] ) ) *( OWS "," [ OWS
    2902      ( codings [ weight ] ) ] ) ]
    2903     Accept-Language = *( "," OWS ) ( language-range [ weight ] ) *( OWS
    2904      "," [ OWS ( language-range [ weight ] ) ] )
    2905  
    2906     Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    2907 
    2908 NEW:
    29092654
    29102655    Accept = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     
    29172662     "," [ OWS ( language-range [ weight ] ) ] )
    29182663    Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    2919 
    2920 
    2921 Section 1.2, paragraph 3:
     2664    BWS = <BWS, defined in [RFC7230], Section 3.2.3>
     2665
     2666NEW:
     2667
     2668    Accept = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     2669     OWS ( media-range [ accept-params ] ) ] ) ]
     2670    Accept-Charset = *( "," OWS ) ( ( charset / "*" ) [ weight ] ) *( OWS
     2671     "," [ OWS ( ( charset / "*" ) [ weight ] ) ] )
     2672    Accept-Encoding = [ ( "," / ( codings [ weight ] ) ) *( OWS "," [ OWS
     2673     ( codings [ weight ] ) ] ) ]
     2674    Accept-Language = *( "," OWS ) ( language-range [ weight ] ) *( OWS
     2675     "," [ OWS ( language-range [ weight ] ) ] )
     2676    Allow = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
     2677 
     2678    BWS = <BWS, defined in [RFC7230], Section 3.2.3>
     2679
     2680
     2681Section 1.2, paragraph 2:
    29222682OLD:
    29232683
     
    29422702
    29432703
    2944 Section 1.2, paragraph 24:
    2945 OLD:
    2946 
     2704Section 1.2, paragraph 16:
     2705OLD:
     2706
     2707    charset = token
     2708    codings = content-coding / "identity" / "*"
     2709    comment = <comment, defined in [RFC7230], Section 3.2.6>
     2710    content-coding = token
     2711    date1 = day SP month SP year
     2712    date2 = day "-" month "-" 2DIGIT
     2713    date3 = month SP ( 2DIGIT / ( SP DIGIT ) )
     2714    day = 2DIGIT
     2715    day-name = %x4D.6F.6E ; Mon
     2716     / %x54.75.65 ; Tue
     2717     / %x57.65.64 ; Wed
     2718     / %x54.68.75 ; Thu
     2719     / %x46.72.69 ; Fri
     2720     / %x53.61.74 ; Sat
     2721     / %x53.75.6E ; Sun
     2722    day-name-l = %x4D.6F.6E.64.61.79 ; Monday
     2723     / %x54.75.65.73.64.61.79 ; Tuesday
     2724     / %x57.65.64.6E.65.73.64.61.79 ; Wednesday
     2725     / %x54.68.75.72.73.64.61.79 ; Thursday
     2726     / %x46.72.69.64.61.79 ; Friday
     2727     / %x53.61.74.75.72.64.61.79 ; Saturday
     2728     / %x53.75.6E.64.61.79 ; Sunday
     2729    delay-seconds = 1*DIGIT
     2730
     2731NEW:
     2732
     2733    charset = token
     2734    codings = content-coding / "identity" / "*"
     2735    comment = <comment, defined in [RFC7230], Section 3.2.6>
     2736    content-coding = token
     2737 
     2738    date1 = day SP month SP year
     2739    date2 = day "-" month "-" 2DIGIT
     2740    date3 = month SP ( 2DIGIT / ( SP DIGIT ) )
     2741    day = 2DIGIT
     2742    day-name = %x4D.6F.6E ; Mon
     2743     / %x54.75.65 ; Tue
     2744     / %x57.65.64 ; Wed
     2745     / %x54.68.75 ; Thu
     2746     / %x46.72.69 ; Fri
     2747     / %x53.61.74 ; Sat
     2748     / %x53.75.6E ; Sun
     2749    day-name-l = %x4D.6F.6E.64.61.79 ; Monday
     2750     / %x54.75.65.73.64.61.79 ; Tuesday
     2751     / %x57.65.64.6E.65.73.64.61.79 ; Wednesday
     2752     / %x54.68.75.72.73.64.61.79 ; Thursday
     2753     / %x46.72.69.64.61.79 ; Friday
     2754     / %x53.61.74.75.72.64.61.79 ; Saturday
     2755     / %x53.75.6E.64.61.79 ; Sunday
     2756    delay-seconds = 1*DIGIT
     2757
     2758
     2759Section 1.2, paragraph 21:
     2760OLD:
     2761
     2762    obs-date = rfc850-date / asctime-date
    29472763    parameter = token "=" ( token / quoted-string )
    29482764    partial-URI = <partial-URI, defined in [RFC7230], Section 2.7>
     
    29552771NEW:
    29562772
     2773    obs-date = rfc850-date / asctime-date
     2774 
    29572775    parameter = token "=" ( token / quoted-string )
    29582776    partial-URI = <partial-URI, defined in [RFC7230], Section 2.7>
     
    29632781
    29642782
    2965 Section 1.2, paragraph 50:
     2783Section 1.2, paragraph 47:
    29662784OLD:
    29672785
  • draft-ietf-httpbis/latest/auth48/rfc7231.diff.html

    r2633 r2635  
    123123      <tr><td class="lineno" valign="top"></td><td class="left">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89</td><td> </td><td class="right">     A.2.  Conversion to Canonical Form . . . . . . . . . . . . . . . 89</td><td class="lineno" valign="top"></td></tr>
    124124      <tr><td class="lineno" valign="top"></td><td class="left">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89</td><td> </td><td class="right">     A.3.  Conversion of Date Formats . . . . . . . . . . . . . . . . 89</td><td class="lineno" valign="top"></td></tr>
     125      <tr><td class="lineno" valign="top"></td><td class="left">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89</td><td> </td><td class="right">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . 89</td><td class="lineno" valign="top"></td></tr>
     126      <tr><td class="lineno" valign="top"></td><td class="left">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td> </td><td class="right">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    125127      <tr><td><a name="diff0008" /></td></tr>
    126       <tr><td class="lineno" valign="top"></td><td class="lblock">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . <span class="delete">90</span></td><td> </td><td class="rblock">     A.4.  Conversion of Content-Encoding . . . . . . . . . . . . . . <span class="insert">89</span></td><td class="lineno" valign="top"></td></tr>
    127       <tr><td class="lineno" valign="top"></td><td class="left">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td> </td><td class="right">     A.5.  Conversion of Content-Transfer-Encoding  . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    128       <tr><td><a name="diff0009" /></td></tr>
    129128      <tr><td class="lineno" valign="top"></td><td class="lblock">     A.6.  MHTML and Line<span class="delete"> </span>Length Limitations  . . . . . . . . . . . . 90</td><td> </td><td class="rblock">     A.6.  MHTML and Line<span class="insert">-</span>Length Limitations  . . . . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
    130129      <tr><td class="lineno" valign="top"></td><td class="left">   Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90</td><td> </td><td class="right">   Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 90</td><td class="lineno" valign="top"></td></tr>
     
    140139      <tr><td class="lineno" valign="top"></td><td class="left">   relation to the identified request target, and responds to that</td><td> </td><td class="right">   relation to the identified request target, and responds to that</td><td class="lineno" valign="top"></td></tr>
    141140      <tr><td class="lineno" valign="top"></td><td class="left">   request with one or more response messages.  A client constructs</td><td> </td><td class="right">   request with one or more response messages.  A client constructs</td><td class="lineno" valign="top"></td></tr>
    142       <tr><td><a name="diff0010" /></td></tr>
     141      <tr><td><a name="diff0009" /></td></tr>
    143142      <tr><td class="lineno" valign="top"></td><td class="lblock">   request messages to communicate specific intentions, <span class="delete">and</span> examines</td><td> </td><td class="rblock">   request messages to communicate specific intentions, examines</td><td class="lineno" valign="top"></td></tr>
    144143      <tr><td class="lineno" valign="top"></td><td class="lblock">   received responses to see if the intentions were carried <span class="delete">out</span> and</td><td> </td><td class="rblock">   received responses to see if the intentions were carried <span class="insert">out,</span> and</td><td class="lineno" valign="top"></td></tr>
     
    166165      <tr><td class="lineno" valign="top"></td><td class="left">2.  Resources</td><td> </td><td class="right">2.  Resources</td><td class="lineno" valign="top"></td></tr>
    167166      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    168       <tr><td><a name="diff0011" /></td></tr>
     167      <tr><td><a name="diff0010" /></td></tr>
    169168      <tr><td class="lineno" valign="top"></td><td class="lblock">   The target of an HTTP request is called a <span class="delete">resource</span>.  HTTP does not</td><td> </td><td class="rblock">   The target of an HTTP request is called a <span class="insert">"resource"</span>.  HTTP does not</td><td class="lineno" valign="top"></td></tr>
    170169      <tr><td class="lineno" valign="top"></td><td class="left">   limit the nature of a resource; it merely defines an interface that</td><td> </td><td class="right">   limit the nature of a resource; it merely defines an interface that</td><td class="lineno" valign="top"></td></tr>
     
    190189      <tr><td class="lineno" valign="top"></td><td class="left">   potentially unbounded stream of representation data.</td><td> </td><td class="right">   potentially unbounded stream of representation data.</td><td class="lineno" valign="top"></td></tr>
    191190      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    192       <tr><td><a name="diff0012" /></td></tr>
     191      <tr><td><a name="diff0011" /></td></tr>
    193192      <tr><td class="lineno" valign="top"></td><td class="lblock">   An origin server might be provided with, or capable of generating,</td><td> </td><td class="rblock">   An origin server might be provided with, or <span class="insert">be </span>capable of generating,</td><td class="lineno" valign="top"></td></tr>
    194193      <tr><td class="lineno" valign="top"></td><td class="left">   multiple representations that are each intended to reflect the</td><td> </td><td class="right">   multiple representations that are each intended to reflect the</td><td class="lineno" valign="top"></td></tr>
     
    214213      <tr><td class="lineno" valign="top"></td><td class="left">3.1.1.1.  Media Type</td><td> </td><td class="right">3.1.1.1.  Media Type</td><td class="lineno" valign="top"></td></tr>
    215214      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    216       <tr><td><a name="diff0013" /></td></tr>
     215      <tr><td><a name="diff0012" /></td></tr>
    217216      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP uses Internet <span class="delete">Media T</span>ypes [RFC2046] in the Content-Type</td><td> </td><td class="rblock">   HTTP uses Internet <span class="insert">media t</span>ypes [RFC2046] in the Content-Type</td><td class="lineno" valign="top"></td></tr>
    218217      <tr><td class="lineno" valign="top"></td><td class="left">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td> </td><td class="right">   (Section 3.1.1.5) and Accept (Section 5.3.2) header fields in order</td><td class="lineno" valign="top"></td></tr>
     
    231230      <tr><td class="lineno" valign="top"></td><td class="left">     parameter      = token "=" ( token / quoted-string )</td><td> </td><td class="right">     parameter      = token "=" ( token / quoted-string )</td><td class="lineno" valign="top"></td></tr>
    232231      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    233       <tr><td><a name="diff0014" /></td></tr>
     232      <tr><td><a name="diff0013" /></td></tr>
    234233      <tr><td class="lineno" valign="top"></td><td class="lblock">   The type, subtype, and parameter name tokens are <span class="delete">case-insensitive.</span></td><td> </td><td class="rblock">   The type, subtype, and parameter name tokens are <span class="insert">case insensitive.</span></td><td class="lineno" valign="top"></td></tr>
    235234      <tr><td class="lineno" valign="top"></td><td class="lblock">   Parameter values might or might not be <span class="delete">case-sensitive,</span> depending on</td><td> </td><td class="rblock">   Parameter values might or might not be <span class="insert">case sensitive,</span> depending on</td><td class="lineno" valign="top"></td></tr>
     
    239238      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    240239      <tr><td class="lineno" valign="top"></td><td class="left">   A parameter value that matches the token production can be</td><td> </td><td class="right">   A parameter value that matches the token production can be</td><td class="lineno" valign="top"></td></tr>
    241       <tr><td><a name="diff0015" /></td></tr>
     240      <tr><td><a name="diff0014" /></td></tr>
    242241      <tr><td class="lineno" valign="top"></td><td class="lblock">   transmitted <span class="delete">as either</span> a token or within a quoted-string.  The quoted</td><td> </td><td class="rblock">   transmitted <span class="insert">either as</span> a token or within a quoted-string.  The quoted</td><td class="lineno" valign="top"></td></tr>
    243242      <tr><td class="lineno" valign="top"></td><td class="left">   and unquoted values are equivalent.  For example, the following</td><td> </td><td class="right">   and unquoted values are equivalent.  For example, the following</td><td class="lineno" valign="top"></td></tr>
     
    263262      <tr><td class="lineno" valign="top"></td><td class="left">     charset = token</td><td> </td><td class="right">     charset = token</td><td class="lineno" valign="top"></td></tr>
    264263      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    265       <tr><td><a name="diff0016" /></td></tr>
     264      <tr><td><a name="diff0015" /></td></tr>
    266265      <tr><td class="lineno" valign="top"></td><td class="lblock">   Charset names ought to be registered in IANA <span class="delete">Character Set</span> registry</td><td> </td><td class="rblock">   Charset names ought to be registered in <span class="insert">the</span> IANA <span class="insert">"Character Sets"</span></td><td class="lineno" valign="top"></td></tr>
    267266      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">(&lt;http://www.iana.org/assignments/character-sets&gt;)</span> according to the</td><td> </td><td class="rblock">   registry <span class="insert">&lt;http://www.iana.org/assignments/character-sets&gt;</span> according</td><td class="lineno" valign="top"></td></tr>
     
    283282      <tr><td class="lineno" valign="top"></td><td class="left">   MIME's canonical form requires that media subtypes of the "text" type</td><td> </td><td class="right">   MIME's canonical form requires that media subtypes of the "text" type</td><td class="lineno" valign="top"></td></tr>
    284283      <tr><td class="lineno" valign="top"></td><td class="left">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td> </td><td class="right">   use CRLF as the text line break.  HTTP allows the transfer of text</td><td class="lineno" valign="top"></td></tr>
    285       <tr><td><a name="diff0017" /></td></tr>
     284      <tr><td><a name="diff0016" /></td></tr>
    286285      <tr><td class="lineno" valign="top"></td><td class="lblock">   media with plain <span class="delete">CR</span> or <span class="delete">LF</span> alone representing a line break, when such</td><td> </td><td class="rblock">   media with plain <span class="insert">carriage return (CR)</span> or <span class="insert">line feed (LF)</span> alone</td><td class="lineno" valign="top"></td></tr>
    287286      <tr><td class="lineno" valign="top"></td><td class="lblock">   line breaks are consistent for an entire representation.  An HTTP</td><td> </td><td class="rblock">   representing a line break, when such line breaks are consistent for</td><td class="lineno" valign="top"></td></tr>
     
    316315      <tr><td class="lineno" valign="top"></td><td class="left">     content-coding   = token</td><td> </td><td class="right">     content-coding   = token</td><td class="lineno" valign="top"></td></tr>
    317316      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    318       <tr><td><a name="diff0018" /></td></tr>
     317      <tr><td><a name="diff0017" /></td></tr>
    319318      <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>
    320319      <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>
     
    341340      <tr><td class="lineno" valign="top"></td><td class="left">   each separated by a hyphen character ("-", %x2D).  In most cases, a</td><td> </td><td class="right">   each separated by a hyphen character ("-", %x2D).  In most cases, a</td><td class="lineno" valign="top"></td></tr>
    342341      <tr><td class="lineno" valign="top"></td><td class="left">   language tag consists of a primary language subtag that identifies a</td><td> </td><td class="right">   language tag consists of a primary language subtag that identifies a</td><td class="lineno" valign="top"></td></tr>
    343       <tr><td><a name="diff0019" /></td></tr>
     342      <tr><td><a name="diff0018" /></td></tr>
    344343      <tr><td class="lineno" valign="top"></td><td class="lblock">   broad family of related languages (e.g., "en" = English) which is</td><td> </td><td class="rblock">   broad family of related languages (e.g., "en" = English)<span class="insert">,</span> which is</td><td class="lineno" valign="top"></td></tr>
    345344      <tr><td class="lineno" valign="top"></td><td class="left">   optionally followed by a series of subtags that refine or narrow that</td><td> </td><td class="right">   optionally followed by a series of subtags that refine or narrow that</td><td class="lineno" valign="top"></td></tr>
     
    365364      <tr><td class="lineno" valign="top"></td><td class="left">   is intended for all language audiences.  This might mean that the</td><td> </td><td class="right">   is intended for all language audiences.  This might mean that the</td><td class="lineno" valign="top"></td></tr>
    366365      <tr><td class="lineno" valign="top"></td><td class="left">   sender does not consider it to be specific to any natural language,</td><td> </td><td class="right">   sender does not consider it to be specific to any natural language,</td><td class="lineno" valign="top"></td></tr>
    367       <tr><td><a name="diff0020" /></td></tr>
     366      <tr><td><a name="diff0019" /></td></tr>
    368367      <tr><td class="lineno" valign="top"></td><td class="lblock">   or that the sender does not know <span class="delete">for which language it is intend</span>ed.</td><td> </td><td class="rblock">   or that the sender does not know <span class="insert">which language is being us</span>ed.</td><td class="lineno" valign="top"></td></tr>
    369368      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    389388      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    390389      <tr><td class="lineno" valign="top"></td><td class="left">   Reactive negotiation is advantageous when the response would vary</td><td> </td><td class="right">   Reactive negotiation is advantageous when the response would vary</td><td class="lineno" valign="top"></td></tr>
    391       <tr><td><a name="diff0021" /></td></tr>
     390      <tr><td><a name="diff0020" /></td></tr>
    392391      <tr><td class="lineno" valign="top"></td><td class="lblock">   over commonly<span class="delete">-</span>used dimensions (such as type, language, or encoding),</td><td> </td><td class="rblock">   over commonly<span class="insert"> </span>used dimensions (such as type, language, or encoding),</td><td class="lineno" valign="top"></td></tr>
    393392      <tr><td class="lineno" valign="top"></td><td class="left">   when the origin server is unable to determine a user agent's</td><td> </td><td class="right">   when the origin server is unable to determine a user agent's</td><td class="lineno" valign="top"></td></tr>
     
    413412      <tr><td class="lineno" valign="top"></td><td class="left">   applying semantics to a target resource in much the same way as</td><td> </td><td class="right">   applying semantics to a target resource in much the same way as</td><td class="lineno" valign="top"></td></tr>
    414413      <tr><td class="lineno" valign="top"></td><td class="left">   invoking a defined method on an identified object would apply</td><td> </td><td class="right">   invoking a defined method on an identified object would apply</td><td class="lineno" valign="top"></td></tr>
    415       <tr><td><a name="diff0022" /></td></tr>
     414      <tr><td><a name="diff0021" /></td></tr>
    416415      <tr><td class="lineno" valign="top"></td><td class="lblock">   semantics.  The method token is case<span class="delete">-</span>sensitive because it might be</td><td> </td><td class="rblock">   semantics.  The method token is case<span class="insert"> </span>sensitive because it might be</td><td class="lineno" valign="top"></td></tr>
    417416      <tr><td class="lineno" valign="top"></td><td class="left">   used as a gateway to object-based systems with case-sensitive method</td><td> </td><td class="right">   used as a gateway to object-based systems with case-sensitive method</td><td class="lineno" valign="top"></td></tr>
     
    419418      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    420419      <tr><td class="lineno" valign="top"></td><td class="left">   Unlike distributed objects, the standardized request methods in HTTP</td><td> </td><td class="right">   Unlike distributed objects, the standardized request methods in HTTP</td><td class="lineno" valign="top"></td></tr>
    421       <tr><td><a name="diff0023" /></td></tr>
     420      <tr><td><a name="diff0022" /></td></tr>
    422421      <tr><td class="lineno" valign="top"></td><td class="lblock">   are not resource<span class="delete">-</span>specific, since uniform interfaces provide for</td><td> </td><td class="rblock">   are not resource<span class="insert"> </span>specific, since uniform interfaces provide for</td><td class="lineno" valign="top"></td></tr>
    423422      <tr><td class="lineno" valign="top"></td><td class="left">   better visibility and reuse in network-based systems [REST].  Once</td><td> </td><td class="right">   better visibility and reuse in network-based systems [REST].  Once</td><td class="lineno" valign="top"></td></tr>
     
    443442      <tr><td class="lineno" valign="top"></td><td class="left">   Additional methods, outside the scope of this specification, have</td><td> </td><td class="right">   Additional methods, outside the scope of this specification, have</td><td class="lineno" valign="top"></td></tr>
    444443      <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>
    445       <tr><td><a name="diff0024" /></td></tr>
     444      <tr><td><a name="diff0023" /></td></tr>
    446445      <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>
    447446      <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>
     
    468467      <tr><td class="lineno" valign="top"></td><td class="left">   property, or unusual burden on the origin server.</td><td> </td><td class="right">   property, or unusual burden on the origin server.</td><td class="lineno" valign="top"></td></tr>
    469468      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    470       <tr><td><a name="diff0025" /></td></tr>
     469      <tr><td><a name="diff0024" /></td></tr>
    471470      <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>
    472471      <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>
     
    502501      <tr><td class="lineno" valign="top"></td><td class="left">   resource is to perform an unsafe action, then the resource owner MUST</td><td> </td><td class="right">   resource is to perform an unsafe action, then the resource owner MUST</td><td class="lineno" valign="top"></td></tr>
    503502      <tr><td class="lineno" valign="top"></td><td class="left">   disable or disallow that action when it is accessed using a safe</td><td> </td><td class="right">   disable or disallow that action when it is accessed using a safe</td><td class="lineno" valign="top"></td></tr>
    504       <tr><td><a name="diff0026" /></td></tr>
     503      <tr><td><a name="diff0025" /></td></tr>
    505504      <tr><td class="lineno" valign="top"></td><td class="lblock">   request method.  Failure to do so will result in unfortunate side<span class="delete">-</span></td><td> </td><td class="rblock">   request method.  Failure to do so will result in unfortunate side</td><td class="lineno" valign="top"></td></tr>
    506505      <tr><td class="lineno" valign="top"></td><td class="left">   effects when automated processes perform a GET on every URI reference</td><td> </td><td class="right">   effects when automated processes perform a GET on every URI reference</td><td class="lineno" valign="top"></td></tr>
     
    519518      <tr><td class="lineno" valign="top"></td><td class="left">   what has been requested by the user; a server is free to log each</td><td> </td><td class="right">   what has been requested by the user; a server is free to log each</td><td class="lineno" valign="top"></td></tr>
    520519      <tr><td class="lineno" valign="top"></td><td class="left">   request separately, retain a revision control history, or implement</td><td> </td><td class="right">   request separately, retain a revision control history, or implement</td><td class="lineno" valign="top"></td></tr>
    521       <tr><td><a name="diff0027" /></td></tr>
     520      <tr><td><a name="diff0026" /></td></tr>
    522521      <tr><td class="lineno" valign="top"></td><td class="lblock">   other non-idempotent side<span class="delete">-</span>effects for each idempotent request.</td><td> </td><td class="rblock">   other non-idempotent side<span class="insert"> </span>effects for each idempotent request.</td><td class="lineno" valign="top"></td></tr>
    523522      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    537536      <tr><td class="lineno" valign="top"></td><td class="left">   specific requirements see [RFC7234].  In general, safe methods that</td><td> </td><td class="right">   specific requirements see [RFC7234].  In general, safe methods that</td><td class="lineno" valign="top"></td></tr>
    538537      <tr><td class="lineno" valign="top"></td><td class="left">   do not depend on a current or authoritative response are defined as</td><td> </td><td class="right">   do not depend on a current or authoritative response are defined as</td><td class="lineno" valign="top"></td></tr>
    539       <tr><td><a name="diff0028" /></td></tr>
     538      <tr><td><a name="diff0027" /></td></tr>
    540539      <tr><td class="lineno" valign="top"></td><td class="lblock">   cacheable; this specification defines GET, HEAD and POST as</td><td> </td><td class="rblock">   cacheable; this specification defines GET, HEAD<span class="insert">,</span> and POST as</td><td class="lineno" valign="top"></td></tr>
    541540      <tr><td class="lineno" valign="top"></td><td class="left">   cacheable, although the overwhelming majority of cache</td><td> </td><td class="right">   cacheable, although the overwhelming majority of cache</td><td class="lineno" valign="top"></td></tr>
     
    553552      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    554553      <tr><td class="lineno" valign="top"></td><td class="left">   It is tempting to think of resource identifiers as remote file system</td><td> </td><td class="right">   It is tempting to think of resource identifiers as remote file system</td><td class="lineno" valign="top"></td></tr>
    555       <tr><td><a name="diff0029" /></td></tr>
     554      <tr><td><a name="diff0028" /></td></tr>
    556555      <tr><td class="lineno" valign="top"></td><td class="lblock">   pathnames<span class="delete">,</span> and of representations as being a copy of the contents of</td><td> </td><td class="rblock">   pathnames and of representations as being a copy of the contents of</td><td class="lineno" valign="top"></td></tr>
    557556      <tr><td class="lineno" valign="top"></td><td class="left">   such files.  In fact, that is how many resources are implemented (see</td><td> </td><td class="right">   such files.  In fact, that is how many resources are implemented (see</td><td class="lineno" valign="top"></td></tr>
     
    563562      <tr><td class="lineno" valign="top"></td><td class="left">   a file system, an origin server might be configured to execute the</td><td> </td><td class="right">   a file system, an origin server might be configured to execute the</td><td class="lineno" valign="top"></td></tr>
    564563      <tr><td class="lineno" valign="top"></td><td class="left">   files with the request as input and send the output as the</td><td> </td><td class="right">   files with the request as input and send the output as the</td><td class="lineno" valign="top"></td></tr>
    565       <tr><td><a name="diff0030" /></td></tr>
     564      <tr><td><a name="diff0029" /></td></tr>
    566565      <tr><td class="lineno" valign="top"></td><td class="lblock">   representation<span class="delete">,</span> rather than transfer the files directly.  Regardless,</td><td> </td><td class="rblock">   representation rather than transfer the files directly.  Regardless,</td><td class="lineno" valign="top"></td></tr>
    567566      <tr><td class="lineno" valign="top"></td><td class="left">   only the origin server needs to know how each of its resource</td><td> </td><td class="right">   only the origin server needs to know how each of its resource</td><td class="lineno" valign="top"></td></tr>
    568       <tr><td><a name="diff0031" /></td></tr>
     567      <tr><td><a name="diff0030" /></td></tr>
    569568      <tr><td class="lineno" valign="top"></td><td class="lblock">   identifiers corresponds to an implementation<span class="delete">,</span> and how each</td><td> </td><td class="rblock">   identifiers corresponds to an implementation and how each</td><td class="lineno" valign="top"></td></tr>
    570569      <tr><td class="lineno" valign="top"></td><td class="left">   implementation manages to select and send a current representation of</td><td> </td><td class="right">   implementation manages to select and send a current representation of</td><td class="lineno" valign="top"></td></tr>
     
    590589      <tr><td class="lineno" valign="top"></td><td class="left">   POST request; almost all of the status codes defined by this</td><td> </td><td class="right">   POST request; almost all of the status codes defined by this</td><td class="lineno" valign="top"></td></tr>
    591590      <tr><td class="lineno" valign="top"></td><td class="left">   specification might be received in a response to POST (the exceptions</td><td> </td><td class="right">   specification might be received in a response to POST (the exceptions</td><td class="lineno" valign="top"></td></tr>
    592       <tr><td><a name="diff0032" /></td></tr>
     591      <tr><td><a name="diff0031" /></td></tr>
    593592      <tr><td class="lineno" valign="top"></td><td class="lblock">   being <span class="delete">206, 304,</span> and <span class="delete">416).</span></td><td> </td><td class="rblock">   being <span class="insert">206 (Partial Content), 304 (Not Modified),</span> and <span class="insert">416 (Range Not</span></td><td class="lineno" valign="top"></td></tr>
    594593      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Satisfiable)).</span></td><td class="lineno" valign="top"></td></tr>
     
    615614      <tr><td class="lineno" valign="top"></td><td class="left">   reflects the new representation.  This requirement allows a user</td><td> </td><td class="right">   reflects the new representation.  This requirement allows a user</td><td class="lineno" valign="top"></td></tr>
    616615      <tr><td class="lineno" valign="top"></td><td class="left">   agent to know when the representation body it has in memory remains</td><td> </td><td class="right">   agent to know when the representation body it has in memory remains</td><td class="lineno" valign="top"></td></tr>
    617       <tr><td><a name="diff0033" /></td></tr>
     616      <tr><td><a name="diff0032" /></td></tr>
    618617      <tr><td class="lineno" valign="top"></td><td class="lblock">   current as a result of the PUT, thus not in need of <span class="delete">retrieving</span> again</td><td> </td><td class="rblock">   current as a result of the PUT, thus not in need of <span class="insert">being retrieved</span></td><td class="lineno" valign="top"></td></tr>
    619618      <tr><td class="lineno" valign="top"></td><td class="lblock">   from the origin server, and that the new validator(s) received in the</td><td> </td><td class="rblock">   again from the origin server, and that the new validator(s) received</td><td class="lineno" valign="top"></td></tr>
     
    642641      <tr><td class="lineno" valign="top"></td><td class="left">   regarding whether or not to redirect the request.</td><td> </td><td class="right">   regarding whether or not to redirect the request.</td><td class="lineno" valign="top"></td></tr>
    643642      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    644       <tr><td><a name="diff0034" /></td></tr>
     643      <tr><td><a name="diff0033" /></td></tr>
    645644      <tr><td class="lineno" valign="top"></td><td class="lblock">   A PUT request applied to the target resource can have side<span class="delete">-</span>effects on</td><td> </td><td class="rblock">   A PUT request applied to the target resource can have side<span class="insert"> </span>effects on</td><td class="lineno" valign="top"></td></tr>
    646645      <tr><td class="lineno" valign="top"></td><td class="left">   other resources.  For example, an article might have a URI for</td><td> </td><td class="right">   other resources.  For example, an article might have a URI for</td><td class="lineno" valign="top"></td></tr>
     
    666665      <tr><td class="lineno" valign="top"></td><td class="left">   functionality.  In effect, this method is similar to the rm command</td><td> </td><td class="right">   functionality.  In effect, this method is similar to the rm command</td><td class="lineno" valign="top"></td></tr>
    667666      <tr><td class="lineno" valign="top"></td><td class="left">   in UNIX: it expresses a deletion operation on the URI mapping of the</td><td> </td><td class="right">   in UNIX: it expresses a deletion operation on the URI mapping of the</td><td class="lineno" valign="top"></td></tr>
    668       <tr><td><a name="diff0035" /></td></tr>
     667      <tr><td><a name="diff0034" /></td></tr>
    669668      <tr><td class="lineno" valign="top"></td><td class="lblock">   origin server<span class="delete">,</span> rather than an expectation that the previously</td><td> </td><td class="rblock">   origin server rather than an expectation that the previously</td><td class="lineno" valign="top"></td></tr>
    670669      <tr><td class="lineno" valign="top"></td><td class="left">   associated information be deleted.</td><td> </td><td class="right">   associated information be deleted.</td><td class="lineno" valign="top"></td></tr>
     
    690689      <tr><td class="lineno" valign="top"></td><td class="left">   CONNECT is intended only for use in requests to a proxy.  An origin</td><td> </td><td class="right">   CONNECT is intended only for use in requests to a proxy.  An origin</td><td class="lineno" valign="top"></td></tr>
    691690      <tr><td class="lineno" valign="top"></td><td class="left">   server that receives a CONNECT request for itself MAY respond with a</td><td> </td><td class="right">   server that receives a CONNECT request for itself MAY respond with a</td><td class="lineno" valign="top"></td></tr>
    692       <tr><td><a name="diff0036" /></td></tr>
     691      <tr><td><a name="diff0035" /></td></tr>
    693692      <tr><td class="lineno" valign="top"></td><td class="lblock">   2xx status code to indicate that a connection is established.</td><td> </td><td class="rblock">   2xx <span class="insert">(Successful)</span> status code to indicate that a connection is</td><td class="lineno" valign="top"></td></tr>
    694693      <tr><td class="lineno" valign="top"></td><td class="lblock">   However, most origin servers do not implement CONNECT.</td><td> </td><td class="rblock">   established.  However, most origin servers do not implement CONNECT.</td><td class="lineno" valign="top"></td></tr>
     
    715714      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    716715      <tr><td class="lineno" valign="top"></td><td class="left">   The OPTIONS method requests information about the communication</td><td> </td><td class="right">   The OPTIONS method requests information about the communication</td><td class="lineno" valign="top"></td></tr>
    717       <tr><td><a name="diff0037" /></td></tr>
     716      <tr><td><a name="diff0036" /></td></tr>
    718717      <tr><td class="lineno" valign="top"></td><td class="lblock">   options available for the target resource, <span class="delete">either at</span> the origin</td><td> </td><td class="rblock">   options available for the target resource, <span class="insert">at either</span> the origin</td><td class="lineno" valign="top"></td></tr>
    719718      <tr><td class="lineno" valign="top"></td><td class="left">   server or an intervening intermediary.  This method allows a client</td><td> </td><td class="right">   server or an intervening intermediary.  This method allows a client</td><td class="lineno" valign="top"></td></tr>
     
    739738      <tr><td class="lineno" valign="top"></td><td class="left">     Expect  = "100-continue"</td><td> </td><td class="right">     Expect  = "100-continue"</td><td class="lineno" valign="top"></td></tr>
    740739      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    741       <tr><td><a name="diff0038" /></td></tr>
     740      <tr><td><a name="diff0037" /></td></tr>
    742741      <tr><td class="lineno" valign="top"></td><td class="lblock">   The Expect field-value is case<span class="delete">-</span>insensitive.</td><td> </td><td class="rblock">   The Expect field-value is case<span class="insert"> </span>insensitive.</td><td class="lineno" valign="top"></td></tr>
    743742      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    763762      <tr><td class="lineno" valign="top"></td><td class="left">      Note: The Expect header field was added after the original</td><td> </td><td class="right">      Note: The Expect header field was added after the original</td><td class="lineno" valign="top"></td></tr>
    764763      <tr><td class="lineno" valign="top"></td><td class="left">      publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td> </td><td class="right">      publication of HTTP/1.1 [RFC2068] as both the means to request an</td><td class="lineno" valign="top"></td></tr>
    765       <tr><td><a name="diff0039" /></td></tr>
     764      <tr><td><a name="diff0038" /></td></tr>
    766765      <tr><td class="lineno" valign="top"></td><td class="lblock">      interim 100 response and the general mechanism for indicating</td><td> </td><td class="rblock">      interim 100 <span class="insert">(Continue)</span> response and the general mechanism for</td><td class="lineno" valign="top"></td></tr>
    767766      <tr><td class="lineno" valign="top"></td><td class="lblock">      must-understand extensions.  However, the extension mechanism has</td><td> </td><td class="rblock">      indicating must-understand extensions.  However, the extension</td><td class="lineno" valign="top"></td></tr>
     
    793792      <tr><td class="lineno" valign="top"></td><td class="left">   value is greater than zero, the intermediary MUST generate an updated</td><td> </td><td class="right">   value is greater than zero, the intermediary MUST generate an updated</td><td class="lineno" valign="top"></td></tr>
    794793      <tr><td class="lineno" valign="top"></td><td class="left">   Max-Forwards field in the forwarded message with a field-value that</td><td> </td><td class="right">   Max-Forwards field in the forwarded message with a field-value that</td><td class="lineno" valign="top"></td></tr>
    795       <tr><td><a name="diff0040" /></td></tr>
     794      <tr><td><a name="diff0039" /></td></tr>
    796795      <tr><td class="lineno" valign="top"></td><td class="lblock">   is the lesser of<span class="delete">: a) the received value decremented by one (1),</span> or b)</td><td> </td><td class="rblock">   is the lesser of<span class="insert"> a) the received value decremented by one (1)</span> or b)</td><td class="lineno" valign="top"></td></tr>
    797796      <tr><td class="lineno" valign="top"></td><td class="left">   the recipient's maximum supported value for Max-Forwards.</td><td> </td><td class="right">   the recipient's maximum supported value for Max-Forwards.</td><td class="lineno" valign="top"></td></tr>
     
    817816      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    818817      <tr><td class="lineno" valign="top"></td><td class="left">   is interpreted as "I prefer audio/basic, but send me any audio type</td><td> </td><td class="right">   is interpreted as "I prefer audio/basic, but send me any audio type</td><td class="lineno" valign="top"></td></tr>
    819       <tr><td><a name="diff0041" /></td></tr>
     818      <tr><td><a name="diff0040" /></td></tr>
    820819      <tr><td class="lineno" valign="top"></td><td class="lblock">   if it is the best available after an 80% mark<span class="delete">-</span>down in quality".</td><td> </td><td class="rblock">   if it is the best available after an 80% markdown in quality".</td><td class="lineno" valign="top"></td></tr>
    821820      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    841840      <tr><td class="lineno" valign="top"></td><td class="left">   the response have a matching language tag, the origin server can</td><td> </td><td class="right">   the response have a matching language tag, the origin server can</td><td class="lineno" valign="top"></td></tr>
    842841      <tr><td class="lineno" valign="top"></td><td class="left">   either disregard the header field by treating the response as if it</td><td> </td><td class="right">   either disregard the header field by treating the response as if it</td><td class="lineno" valign="top"></td></tr>
    843       <tr><td><a name="diff0042" /></td></tr>
     842      <tr><td><a name="diff0041" /></td></tr>
    844843      <tr><td class="lineno" valign="top"></td><td class="lblock">   is not subject to content negotiation<span class="delete">,</span> or honor the header field by</td><td> </td><td class="rblock">   is not subject to content negotiation or honor the header field by</td><td class="lineno" valign="top"></td></tr>
    845844      <tr><td class="lineno" valign="top"></td><td class="left">   sending a 406 (Not Acceptable) response.  However, the latter is not</td><td> </td><td class="right">   sending a 406 (Not Acceptable) response.  However, the latter is not</td><td class="lineno" valign="top"></td></tr>
     
    865864      <tr><td class="lineno" valign="top"></td><td class="left">   Since intelligibility is highly dependent on the individual user,</td><td> </td><td class="right">   Since intelligibility is highly dependent on the individual user,</td><td class="lineno" valign="top"></td></tr>
    866865      <tr><td class="lineno" valign="top"></td><td class="left">   user agents need to allow user control over the linguistic preference</td><td> </td><td class="right">   user agents need to allow user control over the linguistic preference</td><td class="lineno" valign="top"></td></tr>
    867       <tr><td><a name="diff0043" /></td></tr>
     866      <tr><td><a name="diff0042" /></td></tr>
    868867      <tr><td class="lineno" valign="top"></td><td class="lblock">   (either through configuration of the user agent itself<span class="delete">,</span> or by</td><td> </td><td class="rblock">   (either through configuration of the user agent itself or by</td><td class="lineno" valign="top"></td></tr>
    869868      <tr><td class="lineno" valign="top"></td><td class="left">   defaulting to a user controllable system setting).  A user agent that</td><td> </td><td class="right">   defaulting to a user controllable system setting).  A user agent that</td><td class="lineno" valign="top"></td></tr>
     
    889888      <tr><td class="lineno" valign="top"></td><td class="left">   The "From" header field contains an Internet email address for a</td><td> </td><td class="right">   The "From" header field contains an Internet email address for a</td><td class="lineno" valign="top"></td></tr>
    890889      <tr><td class="lineno" valign="top"></td><td class="left">   human user who controls the requesting user agent.  The address ought</td><td> </td><td class="right">   human user who controls the requesting user agent.  The address ought</td><td class="lineno" valign="top"></td></tr>
    891       <tr><td><a name="diff0044" /></td></tr>
     890      <tr><td><a name="diff0043" /></td></tr>
    892891      <tr><td class="lineno" valign="top"></td><td class="lblock">   to be machine<span class="delete">-</span>usable, as defined by "mailbox" in Section 3.4 of</td><td> </td><td class="rblock">   to be machine<span class="insert"> </span>usable, as defined by "mailbox" in Section 3.4 of</td><td class="lineno" valign="top"></td></tr>
    893892      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5322]:</td><td> </td><td class="right">   [RFC5322]:</td><td class="lineno" valign="top"></td></tr>
     
    913912      <tr><td class="lineno" valign="top"></td><td class="left">   If the target URI was obtained from a source that does not have its</td><td> </td><td class="right">   If the target URI was obtained from a source that does not have its</td><td class="lineno" valign="top"></td></tr>
    914913      <tr><td class="lineno" valign="top"></td><td class="left">   own URI (e.g., input from the user keyboard, or an entry within the</td><td> </td><td class="right">   own URI (e.g., input from the user keyboard, or an entry within the</td><td class="lineno" valign="top"></td></tr>
    915       <tr><td><a name="diff0045" /></td></tr>
     914      <tr><td><a name="diff0044" /></td></tr>
    916915      <tr><td class="lineno" valign="top"></td><td class="lblock">   user's bookmarks/favorites), the user agent MUST either exclude</td><td> </td><td class="rblock">   user's bookmarks/favorites), the user agent MUST either exclude<span class="insert"> the</span></td><td class="lineno" valign="top"></td></tr>
    917916      <tr><td class="lineno" valign="top"></td><td class="left">   Referer or send it with a value of "about:blank".</td><td> </td><td class="right">   Referer or send it with a value of "about:blank".</td><td class="lineno" valign="top"></td></tr>
     
    931930      <tr><td class="lineno" valign="top"></td><td class="left">   Some intermediaries have been known to indiscriminately remove</td><td> </td><td class="right">   Some intermediaries have been known to indiscriminately remove</td><td class="lineno" valign="top"></td></tr>
    932931      <tr><td class="lineno" valign="top"></td><td class="left">   Referer header fields from outgoing requests.  This has the</td><td> </td><td class="right">   Referer header fields from outgoing requests.  This has the</td><td class="lineno" valign="top"></td></tr>
    933       <tr><td><a name="diff0046" /></td></tr>
     932      <tr><td><a name="diff0045" /></td></tr>
    934933      <tr><td class="lineno" valign="top"></td><td class="lblock">   unfortunate side<span class="delete">-</span>effect of interfering with protection against CSRF</td><td> </td><td class="rblock">   unfortunate side<span class="insert"> </span>effect of interfering with protection against CSRF</td><td class="lineno" valign="top"></td></tr>
    935934      <tr><td class="lineno" valign="top"></td><td class="left">   attacks, which can be far more harmful to their users.</td><td> </td><td class="right">   attacks, which can be far more harmful to their users.</td><td class="lineno" valign="top"></td></tr>
     
    947946      <tr><td class="lineno" valign="top"></td><td class="left">   agent originating the request, which is often used by servers to help</td><td> </td><td class="right">   agent originating the request, which is often used by servers to help</td><td class="lineno" valign="top"></td></tr>
    948947      <tr><td class="lineno" valign="top"></td><td class="left">   identify the scope of reported interoperability problems, to work</td><td> </td><td class="right">   identify the scope of reported interoperability problems, to work</td><td class="lineno" valign="top"></td></tr>
    949       <tr><td><a name="diff0047" /></td></tr>
     948      <tr><td><a name="diff0046" /></td></tr>
    950949      <tr><td class="lineno" valign="top"></td><td class="lblock">   around or tailor responses to avoid particular user<span class="delete"> </span>agent</td><td> </td><td class="rblock">   around or tailor responses to avoid particular user<span class="insert">-</span>agent</td><td class="lineno" valign="top"></td></tr>
    951950      <tr><td class="lineno" valign="top"></td><td class="left">   limitations, and for analytics regarding browser or operating system</td><td> </td><td class="right">   limitations, and for analytics regarding browser or operating system</td><td class="lineno" valign="top"></td></tr>
     
    957956      <tr><td class="lineno" valign="top"></td><td class="left">   The User-Agent field-value consists of one or more product</td><td> </td><td class="right">   The User-Agent field-value consists of one or more product</td><td class="lineno" valign="top"></td></tr>
    958957      <tr><td class="lineno" valign="top"></td><td class="left">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td> </td><td class="right">   identifiers, each followed by zero or more comments (Section 3.2 of</td><td class="lineno" valign="top"></td></tr>
    959       <tr><td><a name="diff0048" /></td></tr>
     958      <tr><td><a name="diff0047" /></td></tr>
    960959      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230]), which together identify the user<span class="delete"> </span>agent software and its</td><td> </td><td class="rblock">   [RFC7230]), which together identify the user<span class="insert">-</span>agent software and its</td><td class="lineno" valign="top"></td></tr>
    961960      <tr><td class="lineno" valign="top"></td><td class="left">   significant subproducts.  By convention, the product identifiers are</td><td> </td><td class="right">   significant subproducts.  By convention, the product identifiers are</td><td class="lineno" valign="top"></td></tr>
    962961      <tr><td class="lineno" valign="top"></td><td class="left">   listed in decreasing order of their significance for identifying the</td><td> </td><td class="right">   listed in decreasing order of their significance for identifying the</td><td class="lineno" valign="top"></td></tr>
    963       <tr><td><a name="diff0049" /></td></tr>
     962      <tr><td><a name="diff0048" /></td></tr>
    964963      <tr><td class="lineno" valign="top"></td><td class="lblock">   user<span class="delete"> </span>agent software.  Each product identifier consists of a name and</td><td> </td><td class="rblock">   user<span class="insert">-</span>agent software.  Each product identifier consists of a name and</td><td class="lineno" valign="top"></td></tr>
    965964      <tr><td class="lineno" valign="top"></td><td class="left">   optional version.</td><td> </td><td class="right">   optional version.</td><td class="lineno" valign="top"></td></tr>
     
    970969      <tr><td class="lineno" valign="top"></td><td class="left">   A sender SHOULD limit generated product identifiers to what is</td><td> </td><td class="right">   A sender SHOULD limit generated product identifiers to what is</td><td class="lineno" valign="top"></td></tr>
    971970      <tr><td class="lineno" valign="top"></td><td class="left">   necessary to identify the product; a sender MUST NOT generate</td><td> </td><td class="right">   necessary to identify the product; a sender MUST NOT generate</td><td class="lineno" valign="top"></td></tr>
    972       <tr><td><a name="diff0050" /></td></tr>
     971      <tr><td><a name="diff0049" /></td></tr>
    973972      <tr><td class="lineno" valign="top"></td><td class="lblock">   advertising or other non<span class="delete">-</span>essential information within the product</td><td> </td><td class="rblock">   advertising or other nonessential information within the product</td><td class="lineno" valign="top"></td></tr>
    974973      <tr><td class="lineno" valign="top"></td><td class="left">   identifier.  A sender SHOULD NOT generate information in product-</td><td> </td><td class="right">   identifier.  A sender SHOULD NOT generate information in product-</td><td class="lineno" valign="top"></td></tr>
    975974      <tr><td class="lineno" valign="top"></td><td class="left">   version that is not a version identifier (i.e., successive versions</td><td> </td><td class="right">   version that is not a version identifier (i.e., successive versions</td><td class="lineno" valign="top"></td></tr>
    976       <tr><td><a name="diff0051" /></td></tr>
     975      <tr><td><a name="diff0050" /></td></tr>
    977976      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the same product name ought <span class="delete">to only</span> differ in the product-version</td><td> </td><td class="rblock">   of the same product name ought <span class="insert">only to</span> differ in the product-version</td><td class="lineno" valign="top"></td></tr>
    978977      <tr><td class="lineno" valign="top"></td><td class="left">   portion of the product identifier).</td><td> </td><td class="right">   portion of the product identifier).</td><td class="lineno" valign="top"></td></tr>
     
    994993      <tr><td class="lineno" valign="top"></td><td class="left">   that the user intentionally desires to see responses tailored for</td><td> </td><td class="right">   that the user intentionally desires to see responses tailored for</td><td class="lineno" valign="top"></td></tr>
    995994      <tr><td class="lineno" valign="top"></td><td class="left">   that identified user agent, even if they might not work as well for</td><td> </td><td class="right">   that identified user agent, even if they might not work as well for</td><td class="lineno" valign="top"></td></tr>
     995      <tr><td><a name="diff0051" /></td></tr>
     996      <tr><td class="lineno" valign="top"></td><td class="lblock">   the actual user agent being <span class="delete">us</span>ed.</td><td> </td><td class="rblock">   the actual user agent being <span class="insert">implement</span>ed.</td><td class="lineno" valign="top"></td></tr>
     997      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     998      <tr><td class="lineno" valign="top"></td><td class="left">6.  Response Status Codes</td><td> </td><td class="right">6.  Response Status Codes</td><td class="lineno" valign="top"></td></tr>
     999      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9961000      <tr><td><a name="diff0052" /></td></tr>
    997       <tr><td class="lineno" valign="top"></td><td class="lblock">   the actual user agent being <span class="delete">us</span>ed.</td><td> </td><td class="rblock">   the actual user agent being <span class="insert">implement</span>ed.</td><td class="lineno" valign="top"></td></tr>
    998       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    999       <tr><td class="lineno" valign="top"></td><td class="left">6.  Response Status Codes</td><td> </td><td class="right">6.  Response Status Codes</td><td class="lineno" valign="top"></td></tr>
    1000       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1001       <tr><td><a name="diff0053" /></td></tr>
    10021001      <tr><td class="lineno" valign="top"></td><td class="lblock">   The status-code element is a <span class="delete">3-digit</span> integer code giving the result</td><td> </td><td class="rblock">   The status-code element is a <span class="insert">three-digit</span> integer code giving the</td><td class="lineno" valign="top"></td></tr>
    10031002      <tr><td class="lineno" valign="top"></td><td class="lblock">   of the attempt to understand and satisfy the request.</td><td> </td><td class="rblock">   result of the attempt to understand and satisfy the request.</td><td class="lineno" valign="top"></td></tr>
     
    10131012      <tr><td class="lineno" valign="top"></td><td class="left">   For example, if an unrecognized status code of 471 is received by a</td><td> </td><td class="right">   For example, if an unrecognized status code of 471 is received by a</td><td class="lineno" valign="top"></td></tr>
    10141013      <tr><td class="lineno" valign="top"></td><td class="left">   client, the client can assume that there was something wrong with its</td><td> </td><td class="right">   client, the client can assume that there was something wrong with its</td><td class="lineno" valign="top"></td></tr>
    1015       <tr><td><a name="diff0054" /></td></tr>
     1014      <tr><td><a name="diff0053" /></td></tr>
    10161015      <tr><td class="lineno" valign="top"></td><td class="lblock">   request and treat the response as if it had received a 400 status</td><td> </td><td class="rblock">   request and treat the response as if it had received a 400 <span class="insert">(Bad</span></td><td class="lineno" valign="top"></td></tr>
    10171016      <tr><td class="lineno" valign="top"></td><td class="lblock">   code.  The response message will usually contain a representation</td><td> </td><td class="rblock"><span class="insert">   Request)</span> status code.  The response message will usually contain a</td><td class="lineno" valign="top"></td></tr>
     
    10191018      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10201019      <tr><td class="lineno" valign="top"></td><td class="left">   The first digit of the status-code defines the class of response.</td><td> </td><td class="right">   The first digit of the status-code defines the class of response.</td><td class="lineno" valign="top"></td></tr>
    1021       <tr><td><a name="diff0055" /></td></tr>
     1020      <tr><td><a name="diff0054" /></td></tr>
    10221021      <tr><td class="lineno" valign="top"></td><td class="lblock">   The last two digits do not have any categorization role.  There are <span class="delete">5</span></td><td> </td><td class="rblock">   The last two digits do not have any categorization role.  There are</td><td class="lineno" valign="top"></td></tr>
    10231022      <tr><td class="lineno" valign="top"></td><td class="lblock">   values for the first digit:</td><td> </td><td class="rblock">   <span class="insert">five</span> values for the first digit:</td><td class="lineno" valign="top"></td></tr>
     
    10441043      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10451044      <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>
    1046       <tr><td><a name="diff0056" /></td></tr>
     1045      <tr><td><a name="diff0055" /></td></tr>
    10471046      <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>
    10481047      <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>
     
    10521051      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    10531052      <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
    1054       <tr><td><a name="diff0057" /></td></tr>
     1053      <tr><td><a name="diff0056" /></td></tr>
    10551054      <tr><td class="lineno" valign="top"></td><td class="lblock">   | <span class="delete">code | reason-p</span>hrase                 | Defined in...            |</td><td> </td><td class="rblock">   | <span class="insert">Code | Reason-P</span>hrase                 | Defined in...            |</td><td class="lineno" valign="top"></td></tr>
    10561055      <tr><td class="lineno" valign="top"></td><td class="left">   +------+-------------------------------+--------------------------+</td><td> </td><td class="right">   +------+-------------------------------+--------------------------+</td><td class="lineno" valign="top"></td></tr>
     
    10761075      <tr><td class="lineno" valign="top"></td><td class="left">   prior to completing the requested action and sending a final</td><td> </td><td class="right">   prior to completing the requested action and sending a final</td><td class="lineno" valign="top"></td></tr>
    10771076      <tr><td class="lineno" valign="top"></td><td class="left">   response.  All 1xx responses consist of only the status-line and</td><td> </td><td class="right">   response.  All 1xx responses consist of only the status-line and</td><td class="lineno" valign="top"></td></tr>
    1078       <tr><td><a name="diff0058" /></td></tr>
     1077      <tr><td><a name="diff0057" /></td></tr>
    10791078      <tr><td class="lineno" valign="top"></td><td class="lblock">   optional header fields<span class="delete">, and thus</span> are terminated by the empty line at</td><td> </td><td class="rblock">   optional header fields<span class="insert"> and, thus,</span> are terminated by the empty line at</td><td class="lineno" valign="top"></td></tr>
    10801079      <tr><td class="lineno" valign="top"></td><td class="left">   the end of the header section.  Since HTTP/1.0 did not define any 1xx</td><td> </td><td class="right">   the end of the header section.  Since HTTP/1.0 did not define any 1xx</td><td class="lineno" valign="top"></td></tr>
     
    11001099      <tr><td class="lineno" valign="top"></td><td class="left">   operation.</td><td> </td><td class="right">   operation.</td><td class="lineno" valign="top"></td></tr>
    11011100      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1102       <tr><td><a name="diff0059" /></td></tr>
     1101      <tr><td><a name="diff0058" /></td></tr>
    11031102      <tr><td class="lineno" valign="top"></td><td class="lblock">   The 202 response is intentionally non<span class="delete">-</span>committal.  Its purpose is to</td><td> </td><td class="rblock">   The 202 response is intentionally noncommittal.  Its purpose is to</td><td class="lineno" valign="top"></td></tr>
    11041103      <tr><td class="lineno" valign="top"></td><td class="left">   allow a server to accept a request for some other process (perhaps a</td><td> </td><td class="right">   allow a server to accept a request for some other process (perhaps a</td><td class="lineno" valign="top"></td></tr>
     
    11241123      <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>
    11251124      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1126       <tr><td><a name="diff0060" /></td></tr>
     1125      <tr><td><a name="diff0059" /></td></tr>
    11271126      <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>
    11281127      <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>
     
    11401139      <tr><td class="lineno" valign="top"></td><td class="left">   resource has been assigned a new permanent URI and any future</td><td> </td><td class="right">   resource has been assigned a new permanent URI and any future</td><td class="lineno" valign="top"></td></tr>
    11411140      <tr><td class="lineno" valign="top"></td><td class="left">   references to this resource ought to use one of the enclosed URIs.</td><td> </td><td class="right">   references to this resource ought to use one of the enclosed URIs.</td><td class="lineno" valign="top"></td></tr>
    1142       <tr><td><a name="diff0061" /></td></tr>
     1141      <tr><td><a name="diff0060" /></td></tr>
    11431142      <tr><td class="lineno" valign="top"></td><td class="lblock">   Clients with link<span class="delete"> </span>editing capabilities ought to automatically re-link</td><td> </td><td class="rblock">   Clients with link<span class="insert">-</span>editing capabilities ought to automatically re-link</td><td class="lineno" valign="top"></td></tr>
    11441143      <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>
     
    11641163      <tr><td class="lineno" valign="top"></td><td class="left">   to a selected resource, since doing so provides the information</td><td> </td><td class="right">   to a selected resource, since doing so provides the information</td><td class="lineno" valign="top"></td></tr>
    11651164      <tr><td class="lineno" valign="top"></td><td class="left">   corresponding to the POST response in a form that can be separately</td><td> </td><td class="right">   corresponding to the POST response in a form that can be separately</td><td class="lineno" valign="top"></td></tr>
    1166       <tr><td><a name="diff0062" /></td></tr>
     1165      <tr><td><a name="diff0061" /></td></tr>
    11671166      <tr><td class="lineno" valign="top"></td><td class="lblock">   identified, bookmarked, and cached independent of the original</td><td> </td><td class="rblock">   identified, bookmarked, and cached<span class="insert">,</span> independent of the original</td><td class="lineno" valign="top"></td></tr>
    11681167      <tr><td class="lineno" valign="top"></td><td class="left">   request.</td><td> </td><td class="right">   request.</td><td class="lineno" valign="top"></td></tr>
     
    11881187      <tr><td class="lineno" valign="top"></td><td class="left">      does not allow changing the request method from POST to GET.  This</td><td> </td><td class="right">      does not allow changing the request method from POST to GET.  This</td><td class="lineno" valign="top"></td></tr>
    11891188      <tr><td class="lineno" valign="top"></td><td class="left">      specification defines no equivalent counterpart for 301 (Moved</td><td> </td><td class="right">      specification defines no equivalent counterpart for 301 (Moved</td><td class="lineno" valign="top"></td></tr>
    1190       <tr><td><a name="diff0063" /></td></tr>
    1191       <tr><td class="lineno" valign="top"></td><td class="lblock">      Permanently) ([<span class="delete">status-308], however,</span> defines the status code 308</td><td> </td><td class="rblock">      Permanently) ([<span class="insert">RFC7238]; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr>
     1189      <tr><td><a name="diff0062" /></td></tr>
     1190      <tr><td class="lineno" valign="top"></td><td class="lblock">      Permanently) ([RFC7238]<span class="delete">, however,</span> defines the status code 308</td><td> </td><td class="rblock">      Permanently) ([RFC7238]<span class="insert">; however, it</span> defines the status code 308</td><td class="lineno" valign="top"></td></tr>
    11921191      <tr><td class="lineno" valign="top"></td><td class="left">      (Permanent Redirect) for this purpose).</td><td> </td><td class="right">      (Permanent Redirect) for this purpose).</td><td class="lineno" valign="top"></td></tr>
    11931192      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12041203      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12051204      <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code indicates that the server cannot or</td><td> </td><td class="right">   The 400 (Bad Request) status code indicates that the server cannot or</td><td class="lineno" valign="top"></td></tr>
    1206       <tr><td><a name="diff0064" /></td></tr>
     1205      <tr><td><a name="diff0063" /></td></tr>
    12071206      <tr><td class="lineno" valign="top"></td><td class="lblock">   will not process the request due to something <span class="delete">which</span> is perceived to</td><td> </td><td class="rblock">   will not process the request due to something <span class="insert">that</span> is perceived to be</td><td class="lineno" valign="top"></td></tr>
    12081207      <tr><td class="lineno" valign="top"></td><td class="lblock">   be a client error (e.g., malformed request syntax, invalid request</td><td> </td><td class="rblock">   a client error (e.g., malformed request syntax, invalid request</td><td class="lineno" valign="top"></td></tr>
     
    12291228      <tr><td class="lineno" valign="top"></td><td class="left">   information, when the client has descended into a "black hole" of</td><td> </td><td class="right">   information, when the client has descended into a "black hole" of</td><td class="lineno" valign="top"></td></tr>
    12301229      <tr><td class="lineno" valign="top"></td><td class="left">   redirection (e.g., a redirected URI prefix that points to a suffix of</td><td> </td><td class="right">   redirection (e.g., a redirected URI prefix that points to a suffix of</td><td class="lineno" valign="top"></td></tr>
    1231       <tr><td><a name="diff0065" /></td></tr>
     1230      <tr><td><a name="diff0064" /></td></tr>
    12321231      <tr><td class="lineno" valign="top"></td><td class="lblock">   itself)<span class="delete">,</span> or when the server is under attack by a client attempting to</td><td> </td><td class="rblock">   itself) or when the server is under attack by a client attempting to</td><td class="lineno" valign="top"></td></tr>
    12331232      <tr><td class="lineno" valign="top"></td><td class="left">   exploit potential security holes.</td><td> </td><td class="right">   exploit potential security holes.</td><td class="lineno" valign="top"></td></tr>
     
    12531252      <tr><td class="lineno" valign="top"></td><td class="left">     ; defined in Section 3.3 of [RFC5322]</td><td> </td><td class="right">     ; defined in Section 3.3 of [RFC5322]</td><td class="lineno" valign="top"></td></tr>
    12541253      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1255       <tr><td><a name="diff0066" /></td></tr>
     1254      <tr><td><a name="diff0065" /></td></tr>
    12561255      <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name     = %x4D.6F.6E ; "Mon", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    12571256      <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x54.75.65 ; "Tue", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x54.75.65 ; "Tue", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    12661265      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    12671266      <tr><td class="lineno" valign="top"></td><td class="left">     day          = 2DIGIT</td><td> </td><td class="right">     day          = 2DIGIT</td><td class="lineno" valign="top"></td></tr>
    1268       <tr><td><a name="diff0067" /></td></tr>
     1267      <tr><td><a name="diff0066" /></td></tr>
    12691268      <tr><td class="lineno" valign="top"></td><td class="lblock">     month        = %x4A.61.6E ; "Jan", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     month        = %x4A.61.6E ; "Jan", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    12701269      <tr><td class="lineno" valign="top"></td><td class="lblock">                  / %x46.65.62 ; "Feb", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">                  / %x46.65.62 ; "Feb", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    12811280      <tr><td class="lineno" valign="top"></td><td class="left">     year         = 4DIGIT</td><td> </td><td class="right">     year         = 4DIGIT</td><td class="lineno" valign="top"></td></tr>
    12821281      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1283       <tr><td><a name="diff0068" /></td></tr>
     1282      <tr><td><a name="diff0067" /></td></tr>
    12841283      <tr><td class="lineno" valign="top"></td><td class="lblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="delete">-</span>sensitive</td><td> </td><td class="rblock">     GMT          = %x47.4D.54 ; "GMT", case<span class="insert"> </span>sensitive</td><td class="lineno" valign="top"></td></tr>
    12851284      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    12981297      <tr><td class="lineno" valign="top"></td><td class="left">                  ; e.g., 02-Jun-82</td><td> </td><td class="right">                  ; e.g., 02-Jun-82</td><td class="lineno" valign="top"></td></tr>
    12991298      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1300       <tr><td><a name="diff0069" /></td></tr>
     1299      <tr><td><a name="diff0068" /></td></tr>
    13011300      <tr><td class="lineno" valign="top"></td><td class="lblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">     day-name-l   = %x4D.6F.6E.64.61.79    ; "Monday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
    13021301      <tr><td class="lineno" valign="top"></td><td class="lblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="delete">case-sensitive</span></td><td> </td><td class="rblock">            / %x54.75.65.73.64.61.79       ; "Tuesday", <span class="insert">case sensitive</span></td><td class="lineno" valign="top"></td></tr>
     
    13281327      <tr><td class="lineno" valign="top"></td><td class="left">   automatically redirecting the request.</td><td> </td><td class="right">   automatically redirecting the request.</td><td class="lineno" valign="top"></td></tr>
    13291328      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1330       <tr><td><a name="diff0070" /></td></tr>
     1329      <tr><td><a name="diff0069" /></td></tr>
    13311330      <tr><td class="lineno" valign="top"></td><td class="lblock">   If the Location value provided in a 3xx (Redirection) does not have a</td><td> </td><td class="rblock">   If the Location value provided in a 3xx (Redirection) <span class="insert">response</span> does</td><td class="lineno" valign="top"></td></tr>
    13321331      <tr><td class="lineno" valign="top"></td><td class="lblock">   fragment component, a user agent MUST process the redirection as if</td><td> </td><td class="rblock">   not have a fragment component, a user agent MUST process the</td><td class="lineno" valign="top"></td></tr>
     
    13561355      <tr><td class="lineno" valign="top"></td><td class="left">   request target, might influence the origin server's process for</td><td> </td><td class="right">   request target, might influence the origin server's process for</td><td class="lineno" valign="top"></td></tr>
    13571356      <tr><td class="lineno" valign="top"></td><td class="left">   selecting and representing this response.  The value consists of</td><td> </td><td class="right">   selecting and representing this response.  The value consists of</td><td class="lineno" valign="top"></td></tr>
    1358       <tr><td><a name="diff0071" /></td></tr>
     1357      <tr><td><a name="diff0070" /></td></tr>
    13591358      <tr><td class="lineno" valign="top"></td><td class="lblock">   either a single asterisk ("*") or a list of header field names (case<span class="delete">-</span></td><td> </td><td class="rblock">   either a single asterisk ("*") or a list of header field names (case</td><td class="lineno" valign="top"></td></tr>
    13601359      <tr><td class="lineno" valign="top"></td><td class="left">   insensitive).</td><td> </td><td class="right">   insensitive).</td><td class="lineno" valign="top"></td></tr>
     
    13801379      <tr><td class="lineno" valign="top"></td><td class="left">       required to match a new request to the stored cache entry.</td><td> </td><td class="right">       required to match a new request to the stored cache entry.</td><td class="lineno" valign="top"></td></tr>
    13811380      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1382       <tr><td><a name="diff0072" /></td></tr>
     1381      <tr><td><a name="diff0071" /></td></tr>
    13831382      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  To inform user<span class="delete"> </span>agent recipients that this response is subject to</td><td> </td><td class="rblock">   2.  To inform user<span class="insert">-</span>agent recipients that this response is subject to</td><td class="lineno" valign="top"></td></tr>
    13841383      <tr><td class="lineno" valign="top"></td><td class="left">       content negotiation (Section 5.3) and that a different</td><td> </td><td class="right">       content negotiation (Section 5.3) and that a different</td><td class="lineno" valign="top"></td></tr>
     
    14041403      <tr><td class="lineno" valign="top"></td><td class="left">   selected representation as a result of processing the request.</td><td> </td><td class="right">   selected representation as a result of processing the request.</td><td class="lineno" valign="top"></td></tr>
    14051404      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1406       <tr><td><a name="diff0073" /></td></tr>
     1405      <tr><td><a name="diff0072" /></td></tr>
    14071406      <tr><td class="lineno" valign="top"></td><td class="lblock">   For example, an ETag header field in a 201 response communicates the</td><td> </td><td class="rblock">   For example, an ETag header field in a 201 <span class="insert">(Created)</span> response</td><td class="lineno" valign="top"></td></tr>
    14081407      <tr><td class="lineno" valign="top"></td><td class="lblock">   entity-tag of the newly created resource's representation, so that it</td><td> </td><td class="rblock">   communicates the entity-tag of the newly created resource's</td><td class="lineno" valign="top"></td></tr>
     
    14311430      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Method Registry</td><td> </td><td class="right">8.1.  Method Registry</td><td class="lineno" valign="top"></td></tr>
    14321431      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1433       <tr><td><a name="diff0074" /></td></tr>
     1432      <tr><td><a name="diff0073" /></td></tr>
    14341433      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Method <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the request</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry"</span> defines the</td><td class="lineno" valign="top"></td></tr>
    14351434      <tr><td class="lineno" valign="top"></td><td class="lblock">   method token (Section 4).  The <span class="delete">method registry will be</span> created and</td><td> </td><td class="rblock">   <span class="insert">namespace</span> for the request method token (Section 4).  The <span class="insert">"HTTP Method</span></td><td class="lineno" valign="top"></td></tr>
     
    14491448      <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>
    14501449      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1451       <tr><td><a name="diff0075" /></td></tr>
     1450      <tr><td><a name="diff0074" /></td></tr>
    14521451      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this name<span class="delete"> </span>space require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this namespace require IETF Review (see</td><td class="lineno" valign="top"></td></tr>
    14531452      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5226], Section 4.1).</td><td> </td><td class="right">   [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr>
     
    14711470      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    14721471      <tr><td class="lineno" valign="top"></td><td class="left">   A new method definition needs to indicate whether it is safe</td><td> </td><td class="right">   A new method definition needs to indicate whether it is safe</td><td class="lineno" valign="top"></td></tr>
    1473       <tr><td><a name="diff0076" /></td></tr>
     1472      <tr><td><a name="diff0075" /></td></tr>
    14741473      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section 4.2.1), idempotent (Section 4.2.2), cacheable</td><td> </td><td class="rblock">   (Section 4.2.1), idempotent (Section 4.2.2), <span class="insert">or</span> cacheable</td><td class="lineno" valign="top"></td></tr>
    14751474      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.2.3),</span> what semantics are to be associated with the payload</td><td> </td><td class="rblock">   (Section <span class="insert">4.2.3).  It needs to indicate</span> what semantics are to be</td><td class="lineno" valign="top"></td></tr>
     
    14901489      <tr><td class="lineno" valign="top"></td><td class="left">8.1.3.  Registrations</td><td> </td><td class="right">8.1.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    14911490      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1492       <tr><td><a name="diff0077" /></td></tr>
     1491      <tr><td><a name="diff0076" /></td></tr>
    14931492      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Method <span class="delete">Registry shall be</span> populated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Method <span class="insert">Registry" has been</span></td><td class="lineno" valign="top"></td></tr>
    14941493      <tr><td class="lineno" valign="top"></td><td class="lblock">   below:</td><td> </td><td class="rblock">   populated with the registrations below:</td><td class="lineno" valign="top"></td></tr>
     
    15091508      <tr><td class="lineno" valign="top"></td><td class="left">8.2.  Status Code Registry</td><td> </td><td class="right">8.2.  Status Code Registry</td><td class="lineno" valign="top"></td></tr>
    15101509      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1511       <tr><td><a name="diff0078" /></td></tr>
     1510      <tr><td><a name="diff0077" /></td></tr>
    15121511      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Status Code <span class="delete">Registry</span> defines the <span class="delete">name space</span> for the response</td><td> </td><td class="rblock">   The <span class="insert">"Hypertext Transfer Protocol (HTTP)</span> Status Code <span class="insert">Registry"</span> defines</td><td class="lineno" valign="top"></td></tr>
    15131512      <tr><td class="lineno" valign="top"></td><td class="lblock">   status-code token (Section 6).  The <span class="delete">status code</span> registry is</td><td> </td><td class="rblock">   the <span class="insert">namespace</span> for the response status-code token (Section 6).  The</td><td class="lineno" valign="top"></td></tr>
     
    15151514      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   &lt;http://www.iana.org/assignments/http-status-codes&gt;.</td><td class="lineno" valign="top"></td></tr>
    15161515      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1517       <tr><td><a name="diff0079" /></td></tr>
     1516      <tr><td><a name="diff0078" /></td></tr>
    15181517      <tr><td class="lineno" valign="top"></td><td class="lblock">   This <span class="delete">S</span>ection replaces the registration procedure for HTTP Status</td><td> </td><td class="rblock">   This <span class="insert">s</span>ection replaces the registration procedure for HTTP Status</td><td class="lineno" valign="top"></td></tr>
    15191518      <tr><td class="lineno" valign="top"></td><td class="left">   Codes previously defined in Section 7.1 of [RFC2817].</td><td> </td><td class="right">   Codes previously defined in Section 7.1 of [RFC2817].</td><td class="lineno" valign="top"></td></tr>
     
    15291528      <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>
    15301529      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1531       <tr><td><a name="diff0080" /></td></tr>
     1530      <tr><td><a name="diff0079" /></td></tr>
    15321531      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to the HTTP status code name<span class="delete"> </span>space require IETF</td><td> </td><td class="rblock">   Values to be added to the HTTP status code namespace require IETF</td><td class="lineno" valign="top"></td></tr>
    15331532      <tr><td class="lineno" valign="top"></td><td class="left">   Review (see [RFC5226], Section 4.1).</td><td> </td><td class="right">   Review (see [RFC5226], Section 4.1).</td><td class="lineno" valign="top"></td></tr>
     
    15531552      <tr><td class="lineno" valign="top"></td><td class="left">8.2.3.  Registrations</td><td> </td><td class="right">8.2.3.  Registrations</td><td class="lineno" valign="top"></td></tr>
    15541553      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1555       <tr><td><a name="diff0081" /></td></tr>
     1554      <tr><td><a name="diff0080" /></td></tr>
    15561555      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Status <span class="delete">Code Registry shall be</span> updated with the registrations</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Status <span class="insert">Codes" registry has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    15571556      <tr><td class="lineno" valign="top"></td><td class="lblock">   below:</td><td> </td><td class="rblock">   registrations below:</td><td class="lineno" valign="top"></td></tr>
     
    15781577      <tr><td class="lineno" valign="top"></td><td class="left">8.3.  Header Field Registry</td><td> </td><td class="right">8.3.  Header Field Registry</td><td class="lineno" valign="top"></td></tr>
    15791578      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1580       <tr><td><a name="diff0082" /></td></tr>
     1579      <tr><td><a name="diff0081" /></td></tr>
    15811580      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP header fields are registered within the <span class="delete">Message Header Field</span></td><td> </td><td class="rblock">   HTTP header fields are registered within the <span class="insert">"Message Headers"</span></td><td class="lineno" valign="top"></td></tr>
    15821581      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Registry</span> located at <span class="delete">&lt;http://www.iana.org/assignments/message-headers/</span></td><td> </td><td class="rblock"><span class="insert">   registry</span> located at <span class="insert">&lt;http://www.iana.org/assignments/message-headers&gt;</span></td><td class="lineno" valign="top"></td></tr>
     
    15931592      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    15941593      <tr><td class="lineno" valign="top"></td><td class="left">   Authors of specifications defining new fields are advised to keep the</td><td> </td><td class="right">   Authors of specifications defining new fields are advised to keep the</td><td class="lineno" valign="top"></td></tr>
    1595       <tr><td><a name="diff0083" /></td></tr>
     1594      <tr><td><a name="diff0082" /></td></tr>
    15961595      <tr><td class="lineno" valign="top"></td><td class="lblock">   name as short as practical and <span class="delete">to not</span> prefix the name with "X-"</td><td> </td><td class="rblock">   name as short as practical and <span class="insert">not to</span> prefix the name with "X-"</td><td class="lineno" valign="top"></td></tr>
    15971596      <tr><td class="lineno" valign="top"></td><td class="left">   unless the header field will never be used on the Internet.  (The</td><td> </td><td class="right">   unless the header field will never be used on the Internet.  (The</td><td class="lineno" valign="top"></td></tr>
    1598       <tr><td><a name="diff0084" /></td></tr>
     1597      <tr><td><a name="diff0083" /></td></tr>
    15991598      <tr><td class="lineno" valign="top"></td><td class="lblock">   "<span class="delete">x</span>-" prefix idiom has been extensively misused in practice; it was</td><td> </td><td class="rblock">   "<span class="insert">X</span>-" prefix idiom has been extensively misused in practice; it was</td><td class="lineno" valign="top"></td></tr>
    16001599      <tr><td class="lineno" valign="top"></td><td class="left">   intended to only be used as a mechanism for avoiding name collisions</td><td> </td><td class="right">   intended to only be used as a mechanism for avoiding name collisions</td><td class="lineno" valign="top"></td></tr>
    16011600      <tr><td class="lineno" valign="top"></td><td class="left">   inside proprietary software or intranet processing, since the prefix</td><td> </td><td class="right">   inside proprietary software or intranet processing, since the prefix</td><td class="lineno" valign="top"></td></tr>
    16021601      <tr><td class="lineno" valign="top"></td><td class="left">   would ensure that private names never collide with a newly registered</td><td> </td><td class="right">   would ensure that private names never collide with a newly registered</td><td class="lineno" valign="top"></td></tr>
     1602      <tr><td><a name="diff0084" /></td></tr>
     1603      <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet name; see [BCP178] for further information)</td><td> </td><td class="rblock">   Internet name; see [BCP178] for further information)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>
     1604      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1605      <tr><td class="lineno" valign="top"></td><td class="left">   New header field values typically have their syntax defined using</td><td> </td><td class="right">   New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr>
    16031606      <tr><td><a name="diff0085" /></td></tr>
    1604       <tr><td class="lineno" valign="top"></td><td class="lblock">   Internet name; see [BCP178] for further information)</td><td> </td><td class="rblock">   Internet name; see [BCP178] for further information)<span class="insert">.</span></td><td class="lineno" valign="top"></td></tr>
    1605       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1606       <tr><td class="lineno" valign="top"></td><td class="left">   New header field values typically have their syntax defined using</td><td> </td><td class="right">   New header field values typically have their syntax defined using</td><td class="lineno" valign="top"></td></tr>
    1607       <tr><td><a name="diff0086" /></td></tr>
    16081607      <tr><td class="lineno" valign="top"></td><td class="lblock">   ABNF <span class="delete">([RFC5234]), using</span> the extension defined in Section 7 of</td><td> </td><td class="rblock">   ABNF <span class="insert">([RFC5234]) (implementing</span> the extension defined in Section 7 of</td><td class="lineno" valign="top"></td></tr>
    16091608      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230] as <span class="delete">necessary,</span> and are usually constrained to the range of</td><td> </td><td class="rblock">   [RFC7230] as <span class="insert">necessary),</span> and <span class="insert">they</span> are usually constrained to the</td><td class="lineno" valign="top"></td></tr>
     
    16311630      <tr><td class="lineno" valign="top"></td><td class="left">   consider documenting:</td><td> </td><td class="right">   consider documenting:</td><td class="lineno" valign="top"></td></tr>
    16321631      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1633       <tr><td><a name="diff0087" /></td></tr>
     1632      <tr><td><a name="diff0086" /></td></tr>
    16341633      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Whether the field is a single value<span class="delete">,</span> or whether it can be a list</td><td> </td><td class="rblock">   o  Whether the field is a single value or whether it can be a list</td><td class="lineno" valign="top"></td></tr>
    16351634      <tr><td class="lineno" valign="top"></td><td class="left">      (delimited by commas; see Section 3.2 of [RFC7230]).</td><td> </td><td class="right">      (delimited by commas; see Section 3.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
     
    16551654      <tr><td class="lineno" valign="top"></td><td class="left">8.3.2.  Registrations</td><td> </td><td class="right">8.3.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    16561655      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1657       <tr><td><a name="diff0088" /></td></tr>
     1656      <tr><td><a name="diff0087" /></td></tr>
    16581657      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">Message Header Field Registry shall be</span> updated with the following</td><td> </td><td class="rblock">   The <span class="insert">"Message Headers" registry has been</span> updated with the following</td><td class="lineno" valign="top"></td></tr>
    16591658      <tr><td class="lineno" valign="top"></td><td class="left">   permanent registrations:</td><td> </td><td class="right">   permanent registrations:</td><td class="lineno" valign="top"></td></tr>
     
    16751674      <tr><td class="lineno" valign="top"></td><td class="left">   | From              | http     | standard | Section 5.5.1   |</td><td> </td><td class="right">   | From              | http     | standard | Section 5.5.1   |</td><td class="lineno" valign="top"></td></tr>
    16761675      <tr><td class="lineno" valign="top"></td><td class="left">   | Location          | http     | standard | Section 7.1.2   |</td><td> </td><td class="right">   | Location          | http     | standard | Section 7.1.2   |</td><td class="lineno" valign="top"></td></tr>
    1677       <tr><td><a name="diff0089" /></td></tr>
     1676      <tr><td><a name="diff0088" /></td></tr>
    16781677      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   | MIME-Version      | http     | standard | Appendix A.1    |</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    16791678      <tr><td class="lineno" valign="top"></td><td class="left">   | Max-Forwards      | http     | standard | Section 5.1.2   |</td><td> </td><td class="right">   | Max-Forwards      | http     | standard | Section 5.1.2   |</td><td class="lineno" valign="top"></td></tr>
    1680       <tr><td><a name="diff0090" /></td></tr>
     1679      <tr><td><a name="diff0089" /></td></tr>
    16811680      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   | MIME-Version      | http     | standard | Appendix A.1    |</span></td><td class="lineno" valign="top"></td></tr>
    16821681      <tr><td class="lineno" valign="top"></td><td class="left">   | Referer           | http     | standard | Section 5.5.2   |</td><td> </td><td class="right">   | Referer           | http     | standard | Section 5.5.2   |</td><td class="lineno" valign="top"></td></tr>
     
    16921691      <tr><td class="lineno" valign="top"></td><td class="left">8.4.  Content Coding Registry</td><td> </td><td class="right">8.4.  Content Coding Registry</td><td class="lineno" valign="top"></td></tr>
    16931692      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1694       <tr><td><a name="diff0091" /></td></tr>
     1693      <tr><td><a name="diff0090" /></td></tr>
    16951694      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Content Coding <span class="delete">Registry</span> defines the <span class="delete">name space</span> for content</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Content Coding <span class="insert">Registry"</span> defines the <span class="insert">namespace</span> for content</td><td class="lineno" valign="top"></td></tr>
    16961695      <tr><td class="lineno" valign="top"></td><td class="lblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="delete">content coding registry</span></td><td> </td><td class="rblock">   coding names (Section 4.2 of [RFC7230]).  The <span class="insert">"HTTP Content Coding</span></td><td class="lineno" valign="top"></td></tr>
     
    17001699      <tr><td class="lineno" valign="top"></td><td class="left">8.4.1.  Procedure</td><td> </td><td class="right">8.4.1.  Procedure</td><td class="lineno" valign="top"></td></tr>
    17011700      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1702       <tr><td><a name="diff0092" /></td></tr>
     1701      <tr><td><a name="diff0091" /></td></tr>
    17031702      <tr><td class="lineno" valign="top"></td><td class="lblock">   Content <span class="delete">C</span>oding registrations MUST include the following fields:</td><td> </td><td class="rblock">   Content <span class="insert">c</span>oding registrations MUST include the following fields:</td><td class="lineno" valign="top"></td></tr>
    17041703      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    17141713      <tr><td class="lineno" valign="top"></td><td class="left">   Section 4.2 of [RFC7230]).</td><td> </td><td class="right">   Section 4.2 of [RFC7230]).</td><td class="lineno" valign="top"></td></tr>
    17151714      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1716       <tr><td><a name="diff0093" /></td></tr>
     1715      <tr><td><a name="diff0092" /></td></tr>
    17171716      <tr><td class="lineno" valign="top"></td><td class="lblock">   Values to be added to this <span class="delete">name space</span> require IETF Review (see</td><td> </td><td class="rblock">   Values to be added to this <span class="insert">namespace</span> require IETF Review (see Section</td><td class="lineno" valign="top"></td></tr>
    17181717      <tr><td class="lineno" valign="top"></td><td class="lblock">   Section 4.1 of <span class="delete">[RFC5226]),</span> and MUST conform to the purpose of content</td><td> </td><td class="rblock">   4.1 of <span class="insert">[RFC5226])</span> and MUST conform to the purpose of content coding</td><td class="lineno" valign="top"></td></tr>
     
    17211720      <tr><td class="lineno" valign="top"></td><td class="left">8.4.2.  Registrations</td><td> </td><td class="right">8.4.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    17221721      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1723       <tr><td><a name="diff0094" /></td></tr>
     1722      <tr><td><a name="diff0093" /></td></tr>
    17241723      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP Content Codings Registry shall be</span> updated with the</td><td> </td><td class="rblock">   The <span class="insert">"HTTP Content Codings Registry" has been</span> updated with the</td><td class="lineno" valign="top"></td></tr>
    17251724      <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>
     
    17421741      <tr><td class="lineno" valign="top"></td><td class="left">   The list of considerations below is not exhaustive.  Most security</td><td> </td><td class="right">   The list of considerations below is not exhaustive.  Most security</td><td class="lineno" valign="top"></td></tr>
    17431742      <tr><td class="lineno" valign="top"></td><td class="left">   concerns related to HTTP semantics are about securing server-side</td><td> </td><td class="right">   concerns related to HTTP semantics are about securing server-side</td><td class="lineno" valign="top"></td></tr>
    1744       <tr><td><a name="diff0095" /></td></tr>
     1743      <tr><td><a name="diff0094" /></td></tr>
    17451744      <tr><td class="lineno" valign="top"></td><td class="lblock">   applications (code behind the HTTP <span class="delete">interface),</span> securing <span class="delete">user agent</span></td><td> </td><td class="rblock">   applications (code behind the HTTP <span class="insert">interface) or</span> securing <span class="insert">user-agent</span></td><td class="lineno" valign="top"></td></tr>
    17461745      <tr><td class="lineno" valign="top"></td><td class="lblock">   processing of payloads received via <span class="delete">HTTP, or secure</span> use of the</td><td> </td><td class="rblock">   processing of payloads received via <span class="insert">HTTP.  Secure</span> use of the Internet</td><td class="lineno" valign="top"></td></tr>
     
    17561755      <tr><td class="lineno" valign="top"></td><td class="left">   representations.  Implementers need to be aware that most file</td><td> </td><td class="right">   representations.  Implementers need to be aware that most file</td><td class="lineno" valign="top"></td></tr>
    17571756      <tr><td class="lineno" valign="top"></td><td class="left">   systems are not designed to protect against malicious file or path</td><td> </td><td class="right">   systems are not designed to protect against malicious file or path</td><td class="lineno" valign="top"></td></tr>
    1758       <tr><td><a name="diff0096" /></td></tr>
     1757      <tr><td><a name="diff0095" /></td></tr>
    17591758      <tr><td class="lineno" valign="top"></td><td class="lblock">   names<span class="delete">, and thus</span> depend on the origin server to avoid mapping to file</td><td> </td><td class="rblock">   names<span class="insert"> and, thus,</span> depend on the origin server to avoid mapping to file</td><td class="lineno" valign="top"></td></tr>
    17601759      <tr><td class="lineno" valign="top"></td><td class="left">   names, folders, or directories that have special significance to the</td><td> </td><td class="right">   names, folders, or directories that have special significance to the</td><td class="lineno" valign="top"></td></tr>
     
    17631762      <tr><td class="lineno" valign="top"></td><td class="left">   For example, UNIX, Microsoft Windows, and other operating systems use</td><td> </td><td class="right">   For example, UNIX, Microsoft Windows, and other operating systems use</td><td class="lineno" valign="top"></td></tr>
    17641763      <tr><td class="lineno" valign="top"></td><td class="left">   ".." as a path component to indicate a directory level above the</td><td> </td><td class="right">   ".." as a path component to indicate a directory level above the</td><td class="lineno" valign="top"></td></tr>
    1765       <tr><td><a name="diff0097" /></td></tr>
     1764      <tr><td><a name="diff0096" /></td></tr>
    17661765      <tr><td class="lineno" valign="top"></td><td class="lblock">   current one, and use specially named paths or file names to send data</td><td> </td><td class="rblock">   current one, and <span class="insert">they</span> use specially named paths or file names to send</td><td class="lineno" valign="top"></td></tr>
    17671766      <tr><td class="lineno" valign="top"></td><td class="lblock">   to system devices.  Similar naming conventions might exist within</td><td> </td><td class="rblock">   data to system devices.  Similar naming conventions might exist</td><td class="lineno" valign="top"></td></tr>
     
    17931792      <tr><td class="lineno" valign="top"></td><td class="left">   information about the user's immediate browsing history and any</td><td> </td><td class="right">   information about the user's immediate browsing history and any</td><td class="lineno" valign="top"></td></tr>
    17941793      <tr><td class="lineno" valign="top"></td><td class="left">   personal information that might be found in the referring resource's</td><td> </td><td class="right">   personal information that might be found in the referring resource's</td><td class="lineno" valign="top"></td></tr>
    1795       <tr><td><a name="diff0098" /></td></tr>
     1794      <tr><td><a name="diff0097" /></td></tr>
    17961795      <tr><td class="lineno" valign="top"></td><td class="lblock">   URI.  Limitations on Referer are described in Section 5.5.2 to</td><td> </td><td class="rblock">   URI.  Limitations on <span class="insert">the</span> Referer <span class="insert">header field</span> are described in</td><td class="lineno" valign="top"></td></tr>
    17971796      <tr><td class="lineno" valign="top"></td><td class="lblock">   address some of its security considerations.</td><td> </td><td class="rblock">   Section 5.5.2 to address some of its security considerations.</td><td class="lineno" valign="top"></td></tr>
     
    18071806      <tr><td class="lineno" valign="top"></td><td class="left">   disclosing one site's fragment to another site.  If the first site</td><td> </td><td class="right">   disclosing one site's fragment to another site.  If the first site</td><td class="lineno" valign="top"></td></tr>
    18081807      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    1809       <tr bgcolor="gray" ><td></td><th><a name="part-l47" /><small>skipping to change at</small><em> page 85, line 33</em></th><th> </th><th><a name="part-r47" /><small>skipping to change at</small><em> page 85, line 33</em></th><td></td></tr>
    1810       <tr><td class="lineno" valign="top"></td><td class="left">   negotiation header fields in relayed requests.</td><td> </td><td class="right">   negotiation header fields in relayed requests.</td><td class="lineno" valign="top"></td></tr>
    1811       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1812       <tr><td class="lineno" valign="top"></td><td class="left">10.  Acknowledgments</td><td> </td><td class="right">10.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
    1813       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1814       <tr><td class="lineno" valign="top"></td><td class="left">   See Section 10 of [RFC7230].</td><td> </td><td class="right">   See Section 10 of [RFC7230].</td><td class="lineno" valign="top"></td></tr>
    1815       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1816       <tr><td class="lineno" valign="top"></td><td class="left">11.  References</td><td> </td><td class="right">11.  References</td><td class="lineno" valign="top"></td></tr>
    1817       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1818       <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>
    1819       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1808      <tr bgcolor="gray" ><td></td><th><a name="part-l47" /><small>skipping to change at</small><em> page 86, line 15</em></th><th> </th><th><a name="part-r47" /><small>skipping to change at</small><em> page 86, line 15</em></th><td></td></tr>
     1809      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1810      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td> </td><td class="right">   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td class="lineno" valign="top"></td></tr>
     1811      <tr><td class="lineno" valign="top"></td><td class="left">              Languages", BCP 47, RFC 5646, September 2009.</td><td> </td><td class="right">              Languages", BCP 47, RFC 5646, September 2009.</td><td class="lineno" valign="top"></td></tr>
     1812      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1813      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC6365]  Hoffman, P. and J. Klensin, "Terminology Used in</td><td> </td><td class="right">   [RFC6365]  Hoffman, P. and J. Klensin, "Terminology Used in</td><td class="lineno" valign="top"></td></tr>
     1814      <tr><td class="lineno" valign="top"></td><td class="left">              Internationalization in the IETF", BCP 166, RFC 6365,</td><td> </td><td class="right">              Internationalization in the IETF", BCP 166, RFC 6365,</td><td class="lineno" valign="top"></td></tr>
     1815      <tr><td class="lineno" valign="top"></td><td class="left">              September 2011.</td><td> </td><td class="right">              September 2011.</td><td class="lineno" valign="top"></td></tr>
     1816      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1817      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
     1818      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
     1819      <tr><td><a name="diff0098" /></td></tr>
     1820      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
     1821      <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>
     1822      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1823      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    18201824      <tr><td><a name="diff0099" /></td></tr>
    1821       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2045]     Freed, N. and N. Borenstein, "Multipurpose Internet</td><td> </td><td class="rblock">   [RFC2045]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail</td><td class="lineno" valign="top"></td></tr>
    1822       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Mail Extensions (MIME) Part One: Format of Internet</td><td> </td><td class="rblock">              Extensions (MIME) Part One: Format of Internet Message</td><td class="lineno" valign="top"></td></tr>
    1823       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Message Bodies", RFC 2045, November 1996.</td><td> </td><td class="rblock">              Bodies", RFC 2045, November 1996.</td><td class="lineno" valign="top"></td></tr>
    1824       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1825      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
     1826      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
     1827      <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>
     1828      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1829      <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>
     1830      <tr><td class="lineno" valign="top"></td><td class="left">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td> </td><td class="right">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr>
    18251831      <tr><td><a name="diff0100" /></td></tr>
    1826       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2046]     Freed, N. and N. Borenstein, "Multipurpose Internet</td><td> </td><td class="rblock">   [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail</td><td class="lineno" valign="top"></td></tr>
    1827       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Mail Extensions (MIME) Part Two: Media Types",</td><td> </td><td class="rblock">              Extensions (MIME) Part Two: Media Types", RFC 2046,</td><td class="lineno" valign="top"></td></tr>
    1828       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 2046, November 1996.</td><td> </td><td class="rblock">              November 1996.</td><td class="lineno" valign="top"></td></tr>
    1829       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1832      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p5-range-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
     1833      <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>
     1834      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1835      <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>
     1836      <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>
    18301837      <tr><td><a name="diff0101" /></td></tr>
    1831       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2119]     Bradner, S., "Key words for use in RFCs to Indicate</td><td> </td><td class="rblock">   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate</td><td class="lineno" valign="top"></td></tr>
    1832       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Requirement Levels", BCP 14, RFC 2119, March 1997.</td><td> </td><td class="rblock">              Requirement Levels", BCP 14, RFC 2119, March 1997.</td><td class="lineno" valign="top"></td></tr>
    1833       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1838      <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>
     1839      <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>
     1840      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1841      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    18341842      <tr><td><a name="diff0102" /></td></tr>
    1835       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC3986]     Berners-Lee, T., Fielding, R., and L. Masinter,</td><td> </td><td class="rblock">   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform</td><td class="lineno" valign="top"></td></tr>
    1836       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "Uniform Resource Identifier (URI): Generic Syntax",</td><td> </td><td class="rblock">              Resource Identifier (URI): Generic Syntax", STD 66,</td><td class="lineno" valign="top"></td></tr>
    1837       <tr><td class="lineno" valign="top"></td><td class="lblock">                 STD 66, RFC 3986, January 2005.</td><td> </td><td class="rblock">              RFC 3986, January 2005.</td><td class="lineno" valign="top"></td></tr>
    1838       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1843      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
     1844      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1845      <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>
     1846      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1847      <tr><td class="lineno" valign="top"></td><td class="left">11.2.  Informative References</td><td> </td><td class="right">11.2.  Informative References</td><td class="lineno" valign="top"></td></tr>
     1848      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1849      <tr><td class="lineno" valign="top"></td><td class="left">   [BCP13]    Freed, N., Klensin, J., and T. Hansen, "Media Type</td><td> </td><td class="right">   [BCP13]    Freed, N., Klensin, J., and T. Hansen, "Media Type</td><td class="lineno" valign="top"></td></tr>
     1850      <tr><td class="lineno" valign="top"></td><td class="left">              Specifications and Registration Procedures", BCP 13,</td><td> </td><td class="right">              Specifications and Registration Procedures", BCP 13,</td><td class="lineno" valign="top"></td></tr>
     1851      <tr><td class="lineno" valign="top"></td><td class="left">              RFC 6838, January 2013.</td><td> </td><td class="right">              RFC 6838, January 2013.</td><td class="lineno" valign="top"></td></tr>
     1852      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1853      <tr><td class="lineno" valign="top"></td><td class="left">   [BCP178]   Saint-Andre, P., Crocker, D., and M. Nottingham,</td><td> </td><td class="right">   [BCP178]   Saint-Andre, P., Crocker, D., and M. Nottingham,</td><td class="lineno" valign="top"></td></tr>
     1854      <tr><td class="lineno" valign="top"></td><td class="left">              "Deprecating the "X-" Prefix and Similar Constructs in</td><td> </td><td class="right">              "Deprecating the "X-" Prefix and Similar Constructs in</td><td class="lineno" valign="top"></td></tr>
     1855      <tr><td class="lineno" valign="top"></td><td class="left">              Application Protocols", BCP 178, RFC 6648, June 2012.</td><td> </td><td class="right">              Application Protocols", BCP 178, RFC 6648, June 2012.</td><td class="lineno" valign="top"></td></tr>
     1856      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     1857      <tr bgcolor="gray" ><td></td><th><a name="part-l48" /><small>skipping to change at</small><em> page 88, line 32</em></th><th> </th><th><a name="part-r48" /><small>skipping to change at</small><em> page 88, line 26</em></th><td></td></tr>
     1858      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td> </td><td class="right">   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td class="lineno" valign="top"></td></tr>
     1859      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1860      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC6265]  Barth, A., "HTTP State Management Mechanism", RFC 6265,</td><td> </td><td class="right">   [RFC6265]  Barth, A., "HTTP State Management Mechanism", RFC 6265,</td><td class="lineno" valign="top"></td></tr>
     1861      <tr><td class="lineno" valign="top"></td><td class="left">              April 2011.</td><td> </td><td class="right">              April 2011.</td><td class="lineno" valign="top"></td></tr>
     1862      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1863      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC6266]  Reschke, J., "Use of the Content-Disposition Header Field</td><td> </td><td class="right">   [RFC6266]  Reschke, J., "Use of the Content-Disposition Header Field</td><td class="lineno" valign="top"></td></tr>
     1864      <tr><td class="lineno" valign="top"></td><td class="left">              in the Hypertext Transfer Protocol (HTTP)", RFC 6266,</td><td> </td><td class="right">              in the Hypertext Transfer Protocol (HTTP)", RFC 6266,</td><td class="lineno" valign="top"></td></tr>
     1865      <tr><td class="lineno" valign="top"></td><td class="left">              June 2011.</td><td> </td><td class="right">              June 2011.</td><td class="lineno" valign="top"></td></tr>
     1866      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     1867      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="right">   [RFC7238]  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr>
    18391868      <tr><td><a name="diff0103" /></td></tr>
    1840       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC4647]     Phillips, A., Ed. and M. Davis, Ed., "Matching of</td><td> </td><td class="rblock">   [RFC4647]  Phillips, A., Ed. and M. Davis, Ed., "Matching of Language</td><td class="lineno" valign="top"></td></tr>
    1841       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Language Tags", BCP 47, RFC 4647, September 2006.</td><td> </td><td class="rblock">              Tags", BCP 47, RFC 4647, September 2006.</td><td class="lineno" valign="top"></td></tr>
    1842       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1843       <tr><td><a name="diff0104" /></td></tr>
    1844       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5234]     Crocker, D., Ed. and P. Overell, "Augmented BNF for</td><td> </td><td class="rblock">   [RFC5234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax</td><td class="lineno" valign="top"></td></tr>
    1845       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Syntax Specifications: ABNF", STD 68, RFC 5234,</td><td> </td><td class="rblock">              Specifications: ABNF", STD 68, RFC 5234, January 2008.</td><td class="lineno" valign="top"></td></tr>
    1846       <tr><td class="lineno" valign="top"></td><td class="lblock">                 January 2008.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1847       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1848       <tr><td><a name="diff0105" /></td></tr>
    1849       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5646]     Phillips, A., Ed. and M. Davis, Ed., "Tags for</td><td> </td><td class="rblock">   [RFC5646]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying</td><td class="lineno" valign="top"></td></tr>
    1850       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Identifying Languages", BCP 47, RFC 5646,</td><td> </td><td class="rblock">              Languages", BCP 47, RFC 5646, September 2009.</td><td class="lineno" valign="top"></td></tr>
    1851       <tr><td class="lineno" valign="top"></td><td class="lblock">                 September 2009.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1852       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1853       <tr><td><a name="diff0106" /></td></tr>
    1854       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC6365]     Hoffman, P. and J. Klensin, "Terminology Used in</td><td> </td><td class="rblock">   [RFC6365]  Hoffman, P. and J. Klensin, "Terminology Used in</td><td class="lineno" valign="top"></td></tr>
    1855       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Internationalization in the IETF", BCP 166, RFC 6365,</td><td> </td><td class="rblock">              Internationalization in the IETF", BCP 166, RFC 6365,</td><td class="lineno" valign="top"></td></tr>
    1856       <tr><td class="lineno" valign="top"></td><td class="lblock">                 September 2011.</td><td> </td><td class="rblock">              September 2011.</td><td class="lineno" valign="top"></td></tr>
    1857       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1858       <tr><td><a name="diff0107" /></td></tr>
    1859       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7230]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="rblock">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1860       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Transfer Protocol (HTTP/1.1): Message Syntax and</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
    1861       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Routing", <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1862       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 in progress),</span> May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1863       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1864       <tr><td><a name="diff0108" /></td></tr>
    1865       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7232]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="rblock">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1866       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Transfer Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
    1867       <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
    1868       <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>
    1869       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1870       <tr><td><a name="diff0109" /></td></tr>
    1871       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7233]     Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td> </td><td class="rblock">   [RFC7233]  Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,</td><td class="lineno" valign="top"></td></tr>
    1872       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "Hypertext Transfer Protocol (HTTP/1.1): Range</td><td> </td><td class="rblock">              "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",</td><td class="lineno" valign="top"></td></tr>
    1873       <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">              <span class="insert">RFC 7233,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1874       <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>
    1875       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1876       <tr><td><a name="diff0110" /></td></tr>
    1877       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7234]     Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="rblock">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
    1878       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="rblock">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
    1879       <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>
    1880       <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>
    1881       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1882       <tr><td><a name="diff0111" /></td></tr>
    1883       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC7235]     Fielding, R., Ed. and J. Reschke, Ed., "Hypertext</td><td> </td><td class="rblock">   [RFC7235]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    1884       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Transfer Protocol (HTTP/1.1): Authentication",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Authentication", <span class="insert">RFC 7235,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    1885       <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-ietf-httpbis-p7-auth-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1886       <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>
    1887       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1888       <tr><td class="lineno" valign="top"></td><td class="left">11.2.  Informative References</td><td> </td><td class="right">11.2.  Informative References</td><td class="lineno" valign="top"></td></tr>
    1889       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1890       <tr><td><a name="diff0112" /></td></tr>
    1891       <tr><td class="lineno" valign="top"></td><td class="lblock">   [BCP13]       Freed, N., Klensin, J., and T. Hansen, "Media Type</td><td> </td><td class="rblock">   [BCP13]    Freed, N., Klensin, J., and T. Hansen, "Media Type</td><td class="lineno" valign="top"></td></tr>
    1892       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Specifications and Registration Procedures", BCP 13,</td><td> </td><td class="rblock">              Specifications and Registration Procedures", BCP 13,</td><td class="lineno" valign="top"></td></tr>
    1893       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 6838, January 2013.</td><td> </td><td class="rblock">              RFC 6838, January 2013.</td><td class="lineno" valign="top"></td></tr>
    1894       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1895       <tr><td><a name="diff0113" /></td></tr>
    1896       <tr><td class="lineno" valign="top"></td><td class="lblock">   [BCP178]      Saint-Andre, P., Crocker, D., and M. Nottingham,</td><td> </td><td class="rblock">   [BCP178]   Saint-Andre, P., Crocker, D., and M. Nottingham,</td><td class="lineno" valign="top"></td></tr>
    1897       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "Deprecating the "X-" Prefix and Similar Constructs in</td><td> </td><td class="rblock">              "Deprecating the "X-" Prefix and Similar Constructs in</td><td class="lineno" valign="top"></td></tr>
    1898       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Application Protocols", BCP 178, RFC 6648, June 2012.</td><td> </td><td class="rblock">              Application Protocols", BCP 178, RFC 6648, June 2012.</td><td class="lineno" valign="top"></td></tr>
    1899       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1900       <tr><td><a name="diff0114" /></td></tr>
    1901       <tr><td class="lineno" valign="top"></td><td class="lblock">   [BCP90]       Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td> </td><td class="rblock">   [BCP90]    Klyne, G., Nottingham, M., and J. Mogul, "Registration</td><td class="lineno" valign="top"></td></tr>
    1902       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Procedures for Message Header Fields", BCP 90,</td><td> </td><td class="rblock">              Procedures for Message Header Fields", BCP 90, RFC 3864,</td><td class="lineno" valign="top"></td></tr>
    1903       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 3864, September 2004.</td><td> </td><td class="rblock">              September 2004.</td><td class="lineno" valign="top"></td></tr>
    1904       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1905       <tr><td><a name="diff0115" /></td></tr>
    1906       <tr><td class="lineno" valign="top"></td><td class="lblock">   [OWASP]       van der Stock, A., Ed., "A Guide to Building Secure Web</td><td> </td><td class="rblock">   [OWASP]    van der Stock, A., Ed., "A Guide to Building Secure Web</td><td class="lineno" valign="top"></td></tr>
    1907       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Applications and Web Services", The Open Web</td><td> </td><td class="rblock">              Applications and Web Services", The Open Web Application</td><td class="lineno" valign="top"></td></tr>
    1908       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Application Security Project (OWASP) 2.0.1, July 2005,</td><td> </td><td class="rblock">              Security Project (OWASP) 2.0.1, July 2005,</td><td class="lineno" valign="top"></td></tr>
    1909       <tr><td class="lineno" valign="top"></td><td class="lblock">                 &lt;https://www.owasp.org/&gt;.</td><td> </td><td class="rblock">              &lt;https://www.owasp.org/&gt;.</td><td class="lineno" valign="top"></td></tr>
    1910       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1911       <tr><td><a name="diff0116" /></td></tr>
    1912       <tr><td class="lineno" valign="top"></td><td class="lblock">   [REST]        Fielding, R., "Architectural Styles and the Design of</td><td> </td><td class="rblock">   [REST]     Fielding, R., "Architectural Styles and the Design of</td><td class="lineno" valign="top"></td></tr>
    1913       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Network-based Software Architectures",</td><td> </td><td class="rblock">              Network-based Software Architectures",</td><td class="lineno" valign="top"></td></tr>
    1914       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Doctoral Dissertation, University of California,</td><td> </td><td class="rblock">              Doctoral Dissertation, University of California, Irvine,</td><td class="lineno" valign="top"></td></tr>
    1915       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Irvine, September 2000,</td><td> </td><td class="rblock">              September 2000,</td><td class="lineno" valign="top"></td></tr>
    1916       <tr><td class="lineno" valign="top"></td><td class="lblock">                 &lt;http://roy.gbiv.com/pubs/dissertation/top.htm&gt;.</td><td> </td><td class="rblock">              &lt;http://roy.gbiv.com/pubs/dissertation/top.htm&gt;.</td><td class="lineno" valign="top"></td></tr>
    1917       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1918       <tr><td><a name="diff0117" /></td></tr>
    1919       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC1945]     Berners-Lee, T., Fielding, R., and H. Nielsen,</td><td> </td><td class="rblock">   [RFC1945]  Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext</td><td class="lineno" valign="top"></td></tr>
    1920       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "Hypertext Transfer Protocol -- HTTP/1.0", RFC 1945,</td><td> </td><td class="rblock">              Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.</td><td class="lineno" valign="top"></td></tr>
    1921       <tr><td class="lineno" valign="top"></td><td class="lblock">                 May 1996.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1922       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1923       <tr><td><a name="diff0118" /></td></tr>
    1924       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2049]     Freed, N. and N. Borenstein, "Multipurpose Internet</td><td> </td><td class="rblock">   [RFC2049]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail</td><td class="lineno" valign="top"></td></tr>
    1925       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Mail Extensions (MIME) Part Five: Conformance Criteria</td><td> </td><td class="rblock">              Extensions (MIME) Part Five: Conformance Criteria and</td><td class="lineno" valign="top"></td></tr>
    1926       <tr><td class="lineno" valign="top"></td><td class="lblock">                 and Examples", RFC 2049, November 1996.</td><td> </td><td class="rblock">              Examples", RFC 2049, November 1996.</td><td class="lineno" valign="top"></td></tr>
    1927       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1928       <tr><td><a name="diff0119" /></td></tr>
    1929       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2068]     Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and</td><td> </td><td class="rblock">   [RFC2068]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.</td><td class="lineno" valign="top"></td></tr>
    1930       <tr><td class="lineno" valign="top"></td><td class="lblock">                 T. Berners-Lee, "Hypertext Transfer Protocol --</td><td> </td><td class="rblock">              Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",</td><td class="lineno" valign="top"></td></tr>
    1931       <tr><td class="lineno" valign="top"></td><td class="lblock">                 HTTP/1.1", RFC 2068, January 1997.</td><td> </td><td class="rblock">              RFC 2068, January 1997.</td><td class="lineno" valign="top"></td></tr>
    1932       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1933       <tr><td><a name="diff0120" /></td></tr>
    1934       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2295]     Holtman, K. and A. Mutz, "Transparent Content</td><td> </td><td class="rblock">   [RFC2295]  Holtman, K. and A. Mutz, "Transparent Content Negotiation</td><td class="lineno" valign="top"></td></tr>
    1935       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Negotiation in HTTP", RFC 2295, March 1998.</td><td> </td><td class="rblock">              in HTTP", RFC 2295, March 1998.</td><td class="lineno" valign="top"></td></tr>
    1936       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1937       <tr><td><a name="diff0121" /></td></tr>
    1938       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2388]     Masinter, L., "Returning Values from Forms:  multipart/</td><td> </td><td class="rblock">   [RFC2388]  Masinter, L., "Returning Values from Forms:  multipart/</td><td class="lineno" valign="top"></td></tr>
    1939       <tr><td class="lineno" valign="top"></td><td class="lblock">                 form-data", RFC 2388, August 1998.</td><td> </td><td class="rblock">              form-data", RFC 2388, August 1998.</td><td class="lineno" valign="top"></td></tr>
    1940       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1941       <tr><td><a name="diff0122" /></td></tr>
    1942       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2557]     Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,</td><td> </td><td class="rblock">   [RFC2557]  Palme, F., Hopmann, A., Shelness, N., and E. Stefferud,</td><td class="lineno" valign="top"></td></tr>
    1943       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "MIME Encapsulation of Aggregate Documents, such as</td><td> </td><td class="rblock">              "MIME Encapsulation of Aggregate Documents, such as HTML</td><td class="lineno" valign="top"></td></tr>
    1944       <tr><td class="lineno" valign="top"></td><td class="lblock">                 HTML (MHTML)", RFC 2557, March 1999.</td><td> </td><td class="rblock">              (MHTML)", RFC 2557, March 1999.</td><td class="lineno" valign="top"></td></tr>
    1945       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1946       <tr><td><a name="diff0123" /></td></tr>
    1947       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2616]     Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,</td><td> </td><td class="rblock">   [RFC2616]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,</td><td class="lineno" valign="top"></td></tr>
    1948       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td> </td><td class="rblock">              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext</td><td class="lineno" valign="top"></td></tr>
    1949       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</td><td> </td><td class="rblock">              Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.</td><td class="lineno" valign="top"></td></tr>
    1950       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1951       <tr><td><a name="diff0124" /></td></tr>
    1952       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2774]     Frystyk, H., Leach, P., and S. Lawrence, "An HTTP</td><td> </td><td class="rblock">   [RFC2774]  Frystyk, H., Leach, P., and S. Lawrence, "An HTTP</td><td class="lineno" valign="top"></td></tr>
    1953       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Extension Framework", RFC 2774, February 2000.</td><td> </td><td class="rblock">              Extension Framework", RFC 2774, February 2000.</td><td class="lineno" valign="top"></td></tr>
    1954       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1955       <tr><td><a name="diff0125" /></td></tr>
    1956       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2817]     Khare, R. and S. Lawrence, "Upgrading to TLS Within</td><td> </td><td class="rblock">   [RFC2817]  Khare, R. and S. Lawrence, "Upgrading to TLS Within</td><td class="lineno" valign="top"></td></tr>
    1957       <tr><td class="lineno" valign="top"></td><td class="lblock">                 HTTP/1.1", RFC 2817, May 2000.</td><td> </td><td class="rblock">              HTTP/1.1", RFC 2817, May 2000.</td><td class="lineno" valign="top"></td></tr>
    1958       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1959       <tr><td><a name="diff0126" /></td></tr>
    1960       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2978]     Freed, N. and J. Postel, "IANA Charset Registration</td><td> </td><td class="rblock">   [RFC2978]  Freed, N. and J. Postel, "IANA Charset Registration</td><td class="lineno" valign="top"></td></tr>
    1961       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Procedures", BCP 19, RFC 2978, October 2000.</td><td> </td><td class="rblock">              Procedures", BCP 19, RFC 2978, October 2000.</td><td class="lineno" valign="top"></td></tr>
    1962       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1963       <tr><td><a name="diff0127" /></td></tr>
    1964       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5226]     Narten, T. and H. Alvestrand, "Guidelines for Writing</td><td> </td><td class="rblock">   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an</td><td class="lineno" valign="top"></td></tr>
    1965       <tr><td class="lineno" valign="top"></td><td class="lblock">                 an IANA Considerations Section in RFCs", BCP 26,</td><td> </td><td class="rblock">              IANA Considerations Section in RFCs", BCP 26, RFC 5226,</td><td class="lineno" valign="top"></td></tr>
    1966       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 5226, May 2008.</td><td> </td><td class="rblock">              May 2008.</td><td class="lineno" valign="top"></td></tr>
    1967       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1968       <tr><td><a name="diff0128" /></td></tr>
    1969       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5246]     Dierks, T. and E. Rescorla, "The Transport Layer</td><td> </td><td class="rblock">   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security</td><td class="lineno" valign="top"></td></tr>
    1970       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Security (TLS) Protocol Version 1.2", RFC 5246,</td><td> </td><td class="rblock">              (TLS) Protocol Version 1.2", RFC 5246, August 2008.</td><td class="lineno" valign="top"></td></tr>
    1971       <tr><td class="lineno" valign="top"></td><td class="lblock">                 August 2008.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    1972       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1973       <tr><td><a name="diff0129" /></td></tr>
    1974       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5322]     Resnick, P., "Internet Message Format", RFC 5322,</td><td> </td><td class="rblock">   [RFC5322]  Resnick, P., "Internet Message Format", RFC 5322,</td><td class="lineno" valign="top"></td></tr>
    1975       <tr><td class="lineno" valign="top"></td><td class="lblock">                 October 2008.</td><td> </td><td class="rblock">              October 2008.</td><td class="lineno" valign="top"></td></tr>
    1976       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1977       <tr><td><a name="diff0130" /></td></tr>
    1978       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5789]     Dusseault, L. and J. Snell, "PATCH Method for HTTP",</td><td> </td><td class="rblock">   [RFC5789]  Dusseault, L. and J. Snell, "PATCH Method for HTTP",</td><td class="lineno" valign="top"></td></tr>
    1979       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 5789, March 2010.</td><td> </td><td class="rblock">              RFC 5789, March 2010.</td><td class="lineno" valign="top"></td></tr>
    1980       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1981       <tr><td><a name="diff0131" /></td></tr>
    1982       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5905]     Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,</td><td> </td><td class="rblock">   [RFC5905]  Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,</td><td class="lineno" valign="top"></td></tr>
    1983       <tr><td class="lineno" valign="top"></td><td class="lblock">                 "Network Time Protocol Version 4: Protocol and</td><td> </td><td class="rblock">              "Network Time Protocol Version 4: Protocol and Algorithms</td><td class="lineno" valign="top"></td></tr>
    1984       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Algorithms Specification", RFC 5905, June 2010.</td><td> </td><td class="rblock">              Specification", RFC 5905, June 2010.</td><td class="lineno" valign="top"></td></tr>
    1985       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1986       <tr><td><a name="diff0132" /></td></tr>
    1987       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5987]     Reschke, J., "Character Set and Language Encoding for</td><td> </td><td class="rblock">   [RFC5987]  Reschke, J., "Character Set and Language Encoding for</td><td class="lineno" valign="top"></td></tr>
    1988       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Hypertext Transfer Protocol (HTTP) Header Field</td><td> </td><td class="rblock">              Hypertext Transfer Protocol (HTTP) Header Field</td><td class="lineno" valign="top"></td></tr>
    1989       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Parameters", RFC 5987, August 2010.</td><td> </td><td class="rblock">              Parameters", RFC 5987, August 2010.</td><td class="lineno" valign="top"></td></tr>
    1990       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1991       <tr><td><a name="diff0133" /></td></tr>
    1992       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5988]  <span class="delete">   </span>Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td> </td><td class="rblock">   [RFC5988]  Nottingham, M., "Web Linking", RFC 5988, October 2010.</td><td class="lineno" valign="top"></td></tr>
    1993       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1994       <tr><td><a name="diff0134" /></td></tr>
    1995       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC6265]     Barth, A., "HTTP State Management Mechanism", RFC 6265,</td><td> </td><td class="rblock">   [RFC6265]  Barth, A., "HTTP State Management Mechanism", RFC 6265,</td><td class="lineno" valign="top"></td></tr>
    1996       <tr><td class="lineno" valign="top"></td><td class="lblock">                 April 2011.</td><td> </td><td class="rblock">              April 2011.</td><td class="lineno" valign="top"></td></tr>
    1997       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    1998       <tr><td><a name="diff0135" /></td></tr>
    1999       <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC6266]     Reschke, J., "Use of the Content-Disposition Header</td><td> </td><td class="rblock">   [RFC6266]  Reschke, J., "Use of the Content-Disposition Header Field</td><td class="lineno" valign="top"></td></tr>
    2000       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Field in the Hypertext Transfer Protocol (HTTP)",</td><td> </td><td class="rblock">              in the Hypertext Transfer Protocol (HTTP)", RFC 6266,</td><td class="lineno" valign="top"></td></tr>
    2001       <tr><td class="lineno" valign="top"></td><td class="lblock">                 RFC 6266, June 2011.</td><td> </td><td class="rblock">              June 2011.</td><td class="lineno" valign="top"></td></tr>
    2002       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2003       <tr><td><a name="diff0136" /></td></tr>
    2004       <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">[status-308]</span>  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td> </td><td class="rblock">   <span class="insert">[RFC7238]</span>  Reschke, J., "The Hypertext Transfer Protocol (HTTP)</td><td class="lineno" valign="top"></td></tr>
    2005       <tr><td class="lineno" valign="top"></td><td class="lblock">                 Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock">              Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr>
    2006       <tr><td class="lineno" valign="top"></td><td class="lblock">                 <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    2007       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">                 March 2012.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1869      <tr><td class="lineno" valign="top"></td><td class="lblock">              Status Code 308 (Permanent Redirect)",</td><td> </td><td class="rblock">              Status Code 308 (Permanent Redirect)", <span class="insert">RFC 7238, May 2014.</span></td><td class="lineno" valign="top"></td></tr>
     1870      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-reschke-http-status-308-07 (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     1871      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              March 2012.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    20081872      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20091873      <tr><td class="lineno" valign="top"></td><td class="left">Appendix A.  Differences between HTTP and MIME</td><td> </td><td class="right">Appendix A.  Differences between HTTP and MIME</td><td class="lineno" valign="top"></td></tr>
     
    20141878      <tr><td class="lineno" valign="top"></td><td class="left">   variety of representations and with extensible header fields.</td><td> </td><td class="right">   variety of representations and with extensible header fields.</td><td class="lineno" valign="top"></td></tr>
    20151879      <tr><td class="lineno" valign="top"></td><td class="left">   However, RFC 2045 is focused only on email; applications of HTTP have</td><td> </td><td class="right">   However, RFC 2045 is focused only on email; applications of HTTP have</td><td class="lineno" valign="top"></td></tr>
    2016       <tr><td><a name="diff0137" /></td></tr>
     1880      <tr><td><a name="diff0104" /></td></tr>
    20171881      <tr><td class="lineno" valign="top"></td><td class="lblock">   many characteristics that differ from <span class="delete">email, and hence</span> HTTP has</td><td> </td><td class="rblock">   many characteristics that differ from <span class="insert">email; hence,</span> HTTP has features</td><td class="lineno" valign="top"></td></tr>
    20181882      <tr><td class="lineno" valign="top"></td><td class="lblock">   features that differ from MIME.  These differences were carefully</td><td> </td><td class="rblock">   that differ from MIME.  These differences were carefully chosen to</td><td class="lineno" valign="top"></td></tr>
     
    20321896      <tr><td class="lineno" valign="top"></td><td class="left">   a single MIME-Version header field to indicate what version of the</td><td> </td><td class="right">   a single MIME-Version header field to indicate what version of the</td><td class="lineno" valign="top"></td></tr>
    20331897      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    2034       <tr bgcolor="gray" ><td></td><th><a name="part-l48" /><small>skipping to change at</small><em> page 90, line 32</em></th><th> </th><th><a name="part-r48" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr>
     1898      <tr bgcolor="gray" ><td></td><th><a name="part-l49" /><small>skipping to change at</small><em> page 90, line 27</em></th><th> </th><th><a name="part-r49" /><small>skipping to change at</small><em> page 90, line 20</em></th><td></td></tr>
    20351899      <tr><td class="lineno" valign="top"></td><td class="left">   message to an HTTP client.</td><td> </td><td class="right">   message to an HTTP client.</td><td class="lineno" valign="top"></td></tr>
    20361900      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    20431907      <tr><td class="lineno" valign="top"></td><td class="left">   likelihood of safe transport over the destination protocol.</td><td> </td><td class="right">   likelihood of safe transport over the destination protocol.</td><td class="lineno" valign="top"></td></tr>
    20441908      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2045       <tr><td><a name="diff0138" /></td></tr>
     1909      <tr><td><a name="diff0105" /></td></tr>
    20461910      <tr><td class="lineno" valign="top"></td><td class="lblock">A.6.  MHTML and Line<span class="delete"> </span>Length Limitations</td><td> </td><td class="rblock">A.6.  MHTML and Line<span class="insert">-</span>Length Limitations</td><td class="lineno" valign="top"></td></tr>
    20471911      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20481912      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP implementations that share code with MHTML [RFC2557]</td><td> </td><td class="right">   HTTP implementations that share code with MHTML [RFC2557]</td><td class="lineno" valign="top"></td></tr>
    2049       <tr><td><a name="diff0139" /></td></tr>
     1913      <tr><td><a name="diff0106" /></td></tr>
    20501914      <tr><td class="lineno" valign="top"></td><td class="lblock">   implementations need to be aware of MIME line<span class="delete"> </span>length limitations.</td><td> </td><td class="rblock">   implementations need to be aware of MIME line<span class="insert">-</span>length limitations.</td><td class="lineno" valign="top"></td></tr>
    20511915      <tr><td class="lineno" valign="top"></td><td class="left">   Since HTTP does not have this limitation, HTTP does not fold long</td><td> </td><td class="right">   Since HTTP does not have this limitation, HTTP does not fold long</td><td class="lineno" valign="top"></td></tr>
    20521916      <tr><td class="lineno" valign="top"></td><td class="left">   lines.  MHTML messages being transported by HTTP follow all</td><td> </td><td class="right">   lines.  MHTML messages being transported by HTTP follow all</td><td class="lineno" valign="top"></td></tr>
    2053       <tr><td><a name="diff0140" /></td></tr>
     1917      <tr><td><a name="diff0107" /></td></tr>
    20541918      <tr><td class="lineno" valign="top"></td><td class="lblock">   conventions of MHTML, including line<span class="delete"> </span>length limitations and folding,</td><td> </td><td class="rblock">   conventions of MHTML, including line<span class="insert">-</span>length limitations and folding,</td><td class="lineno" valign="top"></td></tr>
    20551919      <tr><td class="lineno" valign="top"></td><td class="left">   canonicalization, etc., since HTTP transfers message-bodies as</td><td> </td><td class="right">   canonicalization, etc., since HTTP transfers message-bodies as</td><td class="lineno" valign="top"></td></tr>
     
    20681932      <tr><td class="lineno" valign="top"></td><td class="left">   representations and representations from resources.</td><td> </td><td class="right">   representations and representations from resources.</td><td class="lineno" valign="top"></td></tr>
    20691933      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2070       <tr><td><a name="diff0141" /></td></tr>
     1934      <tr><td><a name="diff0108" /></td></tr>
    20711935      <tr><td class="lineno" valign="top"></td><td class="lblock">   A new requirement has been added that semantics embedded in a URI</td><td> </td><td class="rblock">   A new requirement has been added that semantics embedded in a URI be</td><td class="lineno" valign="top"></td></tr>
    20721936      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">should</span> be disabled when those semantics are inconsistent with the</td><td> </td><td class="rblock">   disabled when those semantics are inconsistent with the request</td><td class="lineno" valign="top"></td></tr>
     
    20751939      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20761940      <tr><td class="lineno" valign="top"></td><td class="left">   An algorithm has been added for determining if a payload is</td><td> </td><td class="right">   An algorithm has been added for determining if a payload is</td><td class="lineno" valign="top"></td></tr>
    2077       <tr><td><a name="diff0142" /></td></tr>
     1941      <tr><td><a name="diff0109" /></td></tr>
    20781942      <tr><td class="lineno" valign="top"></td><td class="lblock">   associated with a specific identifier<span class="delete">.  (Section 3.1.4.1)</span></td><td> </td><td class="rblock">   associated with a specific identifier<span class="insert"> (Section 3.1.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    20791943      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    20811945      <tr><td class="lineno" valign="top"></td><td class="left">   removed; the default is now whatever the media type definition says.</td><td> </td><td class="right">   removed; the default is now whatever the media type definition says.</td><td class="lineno" valign="top"></td></tr>
    20821946      <tr><td class="lineno" valign="top"></td><td class="left">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td> </td><td class="right">   Likewise, special treatment of ISO-8859-1 has been removed from the</td><td class="lineno" valign="top"></td></tr>
    2083       <tr><td><a name="diff0143" /></td></tr>
     1947      <tr><td><a name="diff0110" /></td></tr>
    20841948      <tr><td class="lineno" valign="top"></td><td class="lblock">   Accept-Charset header field.  (Section<span class="delete"> 3.1.1.3 and Section 5.3.3</span>)</td><td> </td><td class="rblock">   Accept-Charset header field.  (Section<span class="insert">s 3.1.1.3 and 5.3.3.</span>)</td><td class="lineno" valign="top"></td></tr>
    20851949      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    20871951      <tr><td class="lineno" valign="top"></td><td class="left">   affect the base URI for resolving relative URI references, due to</td><td> </td><td class="right">   affect the base URI for resolving relative URI references, due to</td><td class="lineno" valign="top"></td></tr>
    20881952      <tr><td class="lineno" valign="top"></td><td class="left">   poor implementation support and the undesirable effect of potentially</td><td> </td><td class="right">   poor implementation support and the undesirable effect of potentially</td><td class="lineno" valign="top"></td></tr>
    2089       <tr><td><a name="diff0144" /></td></tr>
     1953      <tr><td><a name="diff0111" /></td></tr>
    20901954      <tr><td class="lineno" valign="top"></td><td class="lblock">   breaking relative links in content-negotiated <span class="delete">resources.</span></td><td> </td><td class="rblock">   breaking relative links in content-negotiated <span class="insert">resources</span></td><td class="lineno" valign="top"></td></tr>
    20911955      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.1.4.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.1.4.2).</span></td><td class="lineno" valign="top"></td></tr>
     
    20931957      <tr><td class="lineno" valign="top"></td><td class="left">   To be consistent with the method-neutral parsing algorithm of</td><td> </td><td class="right">   To be consistent with the method-neutral parsing algorithm of</td><td class="lineno" valign="top"></td></tr>
    20941958      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230], the definition of GET has been relaxed so that requests</td><td> </td><td class="right">   [RFC7230], the definition of GET has been relaxed so that requests</td><td class="lineno" valign="top"></td></tr>
    2095       <tr><td><a name="diff0145" /></td></tr>
     1959      <tr><td><a name="diff0112" /></td></tr>
    20961960      <tr><td class="lineno" valign="top"></td><td class="lblock">   can have a body, even though a body has no meaning for <span class="delete">GET.</span></td><td> </td><td class="rblock">   can have a body, even though a body has no meaning for <span class="insert">GET</span></td><td class="lineno" valign="top"></td></tr>
    20971961      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.1).</span></td><td class="lineno" valign="top"></td></tr>
    20981962      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    20991963      <tr><td class="lineno" valign="top"></td><td class="left">   Servers are no longer required to handle all Content-* header fields</td><td> </td><td class="right">   Servers are no longer required to handle all Content-* header fields</td><td class="lineno" valign="top"></td></tr>
    2100       <tr><td><a name="diff0146" /></td></tr>
     1964      <tr><td><a name="diff0113" /></td></tr>
    21011965      <tr><td class="lineno" valign="top"></td><td class="lblock">   and use of Content-Range has been explicitly banned in PUT <span class="delete">requests.</span></td><td> </td><td class="rblock">   and use of Content-Range has been explicitly banned in PUT <span class="insert">requests</span></td><td class="lineno" valign="top"></td></tr>
    21021966      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">4.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">4.3.4).</span></td><td class="lineno" valign="top"></td></tr>
    21031967      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21041968      <tr><td class="lineno" valign="top"></td><td class="left">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td> </td><td class="right">   Definition of the CONNECT method has been moved from [RFC2817] to</td><td class="lineno" valign="top"></td></tr>
    2105       <tr><td><a name="diff0147" /></td></tr>
     1969      <tr><td><a name="diff0114" /></td></tr>
    21061970      <tr><td class="lineno" valign="top"></td><td class="lblock">   this specification<span class="delete">.  (Section 4.3.6)</span></td><td> </td><td class="rblock">   this specification<span class="insert"> (Section 4.3.6).</span></td><td class="lineno" valign="top"></td></tr>
    21071971      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2108       <tr><td><a name="diff0148" /></td></tr>
     1972      <tr><td><a name="diff0115" /></td></tr>
    21091973      <tr><td class="lineno" valign="top"></td><td class="lblock">   The OPTIONS and TRACE request methods have been defined as being</td><td> </td><td class="rblock">   The OPTIONS and TRACE request methods have been defined as being <span class="insert">safe</span></td><td class="lineno" valign="top"></td></tr>
    21101974      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">safe.</span>  (Section 4.3.7 and Section <span class="delete">4.3.8)</span></td><td> </td><td class="rblock">   (Section 4.3.7 and Section <span class="insert">4.3.8).</span></td><td class="lineno" valign="top"></td></tr>
    21111975      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21121976      <tr><td class="lineno" valign="top"></td><td class="left">   The Expect header field's extension mechanism has been removed due to</td><td> </td><td class="right">   The Expect header field's extension mechanism has been removed due to</td><td class="lineno" valign="top"></td></tr>
    2113       <tr><td><a name="diff0149" /></td></tr>
     1977      <tr><td><a name="diff0116" /></td></tr>
    21141978      <tr><td class="lineno" valign="top"></td><td class="lblock">   widely<span class="delete">-deployed broken implementations.  (Section 5.1.1)</span></td><td> </td><td class="rblock">   widely<span class="insert"> deployed broken implementations (Section 5.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    21151979      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21161980      <tr><td class="lineno" valign="top"></td><td class="left">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td> </td><td class="right">   The Max-Forwards header field has been restricted to the OPTIONS and</td><td class="lineno" valign="top"></td></tr>
    21171981      <tr><td class="lineno" valign="top"></td><td class="left">   TRACE methods; previously, extension methods could have used it as</td><td> </td><td class="right">   TRACE methods; previously, extension methods could have used it as</td><td class="lineno" valign="top"></td></tr>
    2118       <tr><td><a name="diff0150" /></td></tr>
     1982      <tr><td><a name="diff0117" /></td></tr>
    21191983      <tr><td class="lineno" valign="top"></td><td class="lblock">   well<span class="delete">.  (Section 5.1.2)</span></td><td> </td><td class="rblock">   well<span class="insert"> (Section 5.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    21201984      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    21221986      <tr><td class="lineno" valign="top"></td><td class="left">   header field when no referring URI is applicable, which distinguishes</td><td> </td><td class="right">   header field when no referring URI is applicable, which distinguishes</td><td class="lineno" valign="top"></td></tr>
    21231987      <tr><td class="lineno" valign="top"></td><td class="left">   that case from others where the Referer field is not sent or has been</td><td> </td><td class="right">   that case from others where the Referer field is not sent or has been</td><td class="lineno" valign="top"></td></tr>
    2124       <tr><td><a name="diff0151" /></td></tr>
     1988      <tr><td><a name="diff0118" /></td></tr>
    21251989      <tr><td class="lineno" valign="top"></td><td class="lblock">   removed<span class="delete">.  (Section 5.5.2)</span></td><td> </td><td class="rblock">   removed<span class="insert"> (Section 5.5.2).</span></td><td class="lineno" valign="top"></td></tr>
    21261990      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21271991      <tr><td class="lineno" valign="top"></td><td class="left">   The following status codes are now cacheable (that is, they can be</td><td> </td><td class="right">   The following status codes are now cacheable (that is, they can be</td><td class="lineno" valign="top"></td></tr>
    21281992      <tr><td class="lineno" valign="top"></td><td class="left">   stored and reused by a cache without explicit freshness information</td><td> </td><td class="right">   stored and reused by a cache without explicit freshness information</td><td class="lineno" valign="top"></td></tr>
    2129       <tr><td><a name="diff0152" /></td></tr>
     1993      <tr><td><a name="diff0119" /></td></tr>
    21301994      <tr><td class="lineno" valign="top"></td><td class="lblock">   present): 204, 404, 405, 414, 501<span class="delete">.  (Section 6)</span></td><td> </td><td class="rblock">   present): 204, 404, 405, 414, 501<span class="insert"> (Section 6).</span></td><td class="lineno" valign="top"></td></tr>
    21311995      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21321996      <tr><td class="lineno" valign="top"></td><td class="left">   The 201 (Created) status description has been changed to allow for</td><td> </td><td class="right">   The 201 (Created) status description has been changed to allow for</td><td class="lineno" valign="top"></td></tr>
    2133       <tr><td><a name="diff0153" /></td></tr>
     1997      <tr><td><a name="diff0120" /></td></tr>
    21341998      <tr><td class="lineno" valign="top"></td><td class="lblock">   the possibility that more than one resource has been <span class="delete">created.</span></td><td> </td><td class="rblock">   the possibility that more than one resource has been <span class="insert">created</span></td><td class="lineno" valign="top"></td></tr>
    21351999      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.2)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.2).</span></td><td class="lineno" valign="top"></td></tr>
    21362000      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21372001      <tr><td class="lineno" valign="top"></td><td class="left">   The definition of 203 (Non-Authoritative Information) has been</td><td> </td><td class="right">   The definition of 203 (Non-Authoritative Information) has been</td><td class="lineno" valign="top"></td></tr>
    2138       <tr><td><a name="diff0154" /></td></tr>
     2002      <tr><td><a name="diff0121" /></td></tr>
    21392003      <tr><td class="lineno" valign="top"></td><td class="lblock">   broadened to include cases of payload transformations as <span class="delete">well.</span></td><td> </td><td class="rblock">   broadened to include cases of payload transformations as <span class="insert">well</span></td><td class="lineno" valign="top"></td></tr>
    21402004      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">6.3.4)</span></td><td> </td><td class="rblock">   (Section <span class="insert">6.3.4).</span></td><td class="lineno" valign="top"></td></tr>
     
    21442008      <tr><td class="lineno" valign="top"></td><td class="left">   based upon the request method semantics.  The redirect status codes</td><td> </td><td class="right">   based upon the request method semantics.  The redirect status codes</td><td class="lineno" valign="top"></td></tr>
    21452009      <tr><td class="lineno" valign="top"></td><td class="left">   301, 302, and 307 no longer have normative requirements on response</td><td> </td><td class="right">   301, 302, and 307 no longer have normative requirements on response</td><td class="lineno" valign="top"></td></tr>
    2146       <tr><td><a name="diff0155" /></td></tr>
     2010      <tr><td><a name="diff0122" /></td></tr>
    21472011      <tr><td class="lineno" valign="top"></td><td class="lblock">   payloads and user interaction<span class="delete">.  (Section 6.4)</span></td><td> </td><td class="rblock">   payloads and user interaction<span class="insert"> (Section 6.4).</span></td><td class="lineno" valign="top"></td></tr>
    21482012      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21492013      <tr><td class="lineno" valign="top"></td><td class="left">   The status codes 301 and 302 have been changed to allow user agents</td><td> </td><td class="right">   The status codes 301 and 302 have been changed to allow user agents</td><td class="lineno" valign="top"></td></tr>
    2150       <tr><td><a name="diff0156" /></td></tr>
     2014      <tr><td><a name="diff0123" /></td></tr>
    21512015      <tr><td class="lineno" valign="top"></td><td class="lblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3)</td><td> </td><td class="rblock">   to rewrite the method from POST to GET.  (Sections 6.4.2 and 6.4.3<span class="insert">.</span>)</td><td class="lineno" valign="top"></td></tr>
    21522016      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2153       <tr><td><a name="diff0157" /></td></tr>
     2017      <tr><td><a name="diff0124" /></td></tr>
    21542018      <tr><td class="lineno" valign="top"></td><td class="lblock">   The description of 303 (See Other) status code has been changed to</td><td> </td><td class="rblock">   The description of <span class="insert">the</span> 303 (See Other) status code has been changed</td><td class="lineno" valign="top"></td></tr>
    21552019      <tr><td class="lineno" valign="top"></td><td class="lblock">   allow it to be cached if explicit freshness information is given, and</td><td> </td><td class="rblock">   to allow it to be cached if explicit freshness information is given,</td><td class="lineno" valign="top"></td></tr>
     
    21582022      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21592023      <tr><td class="lineno" valign="top"></td><td class="left">   The 305 (Use Proxy) status code has been deprecated due to security</td><td> </td><td class="right">   The 305 (Use Proxy) status code has been deprecated due to security</td><td class="lineno" valign="top"></td></tr>
    2160       <tr><td><a name="diff0158" /></td></tr>
     2024      <tr><td><a name="diff0125" /></td></tr>
    21612025      <tr><td class="lineno" valign="top"></td><td class="lblock">   concerns regarding in-band configuration of a proxy<span class="delete">.  (Section 6.4.5)</span></td><td> </td><td class="rblock">   concerns regarding in-band configuration of a proxy<span class="insert"> (Section 6.4.5).</span></td><td class="lineno" valign="top"></td></tr>
    21622026      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21632027      <tr><td class="lineno" valign="top"></td><td class="left">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td> </td><td class="right">   The 400 (Bad Request) status code has been relaxed so that it isn't</td><td class="lineno" valign="top"></td></tr>
    2164       <tr><td><a name="diff0159" /></td></tr>
     2028      <tr><td><a name="diff0126" /></td></tr>
    21652029      <tr><td class="lineno" valign="top"></td><td class="lblock">   limited to syntax errors<span class="delete">.  (Section 6.5.1)</span></td><td> </td><td class="rblock">   limited to syntax errors<span class="insert"> (Section 6.5.1).</span></td><td class="lineno" valign="top"></td></tr>
    21662030      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21672031      <tr><td class="lineno" valign="top"></td><td class="left">   The 426 (Upgrade Required) status code has been incorporated from</td><td> </td><td class="right">   The 426 (Upgrade Required) status code has been incorporated from</td><td class="lineno" valign="top"></td></tr>
    2168       <tr><td><a name="diff0160" /></td></tr>
     2032      <tr><td><a name="diff0127" /></td></tr>
    21692033      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC2817]<span class="delete">.  (Section 6.5.15)</span></td><td> </td><td class="rblock">   [RFC2817]<span class="insert"> (Section 6.5.15).</span></td><td class="lineno" valign="top"></td></tr>
    21702034      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21712035      <tr><td class="lineno" valign="top"></td><td class="left">   The target of requirements on HTTP-date and the Date header field</td><td> </td><td class="right">   The target of requirements on HTTP-date and the Date header field</td><td class="lineno" valign="top"></td></tr>
    21722036      <tr><td class="lineno" valign="top"></td><td class="left">   have been reduced to those systems generating the date, rather than</td><td> </td><td class="right">   have been reduced to those systems generating the date, rather than</td><td class="lineno" valign="top"></td></tr>
    2173       <tr><td><a name="diff0161" /></td></tr>
     2037      <tr><td><a name="diff0128" /></td></tr>
    21742038      <tr><td class="lineno" valign="top"></td><td class="lblock">   all systems sending a date<span class="delete">.  (Section 7.1.1)</span></td><td> </td><td class="rblock">   all systems sending a date<span class="insert"> (Section 7.1.1).</span></td><td class="lineno" valign="top"></td></tr>
    21752039      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    21772041      <tr><td class="lineno" valign="top"></td><td class="left">   URI references, including relative references and fragments, along</td><td> </td><td class="right">   URI references, including relative references and fragments, along</td><td class="lineno" valign="top"></td></tr>
    21782042      <tr><td class="lineno" valign="top"></td><td class="left">   with some clarifications as to when use of fragments would not be</td><td> </td><td class="right">   with some clarifications as to when use of fragments would not be</td><td class="lineno" valign="top"></td></tr>
    2179       <tr><td><a name="diff0162" /></td></tr>
     2043      <tr><td><a name="diff0129" /></td></tr>
    21802044      <tr><td class="lineno" valign="top"></td><td class="lblock">   appropriate<span class="delete">.  (Section 7.1.2)</span></td><td> </td><td class="rblock">   appropriate<span class="insert"> (Section 7.1.2).</span></td><td class="lineno" valign="top"></td></tr>
    21812045      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    21832047      <tr><td class="lineno" valign="top"></td><td class="left">   option to specify it in a PUT request.  Requirements relating to the</td><td> </td><td class="right">   option to specify it in a PUT request.  Requirements relating to the</td><td class="lineno" valign="top"></td></tr>
    21842048      <tr><td class="lineno" valign="top"></td><td class="left">   content of Allow have been relaxed; correspondingly, clients are not</td><td> </td><td class="right">   content of Allow have been relaxed; correspondingly, clients are not</td><td class="lineno" valign="top"></td></tr>
    2185       <tr><td><a name="diff0163" /></td></tr>
    2186       <tr><td class="lineno" valign="top"></td><td class="lblock">   required to always trust its <span class="delete">value.</span>  (Section <span class="delete">7.4.1)</span></td><td> </td><td class="rblock">   required to always trust its <span class="insert">value</span> (Section <span class="insert">7.4.1).</span></td><td class="lineno" valign="top"></td></tr>
    2187       <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>
    2188       <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   A Method Registry has been defined (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>
    2189       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2190       <tr><td><a name="diff0164" /></td></tr>
    2191       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   A Method Registry has been defined.  (Section 8.1)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     2049      <tr><td><a name="diff0130" /></td></tr>
     2050      <tr><td class="lineno" valign="top"></td><td class="lblock">   required to always trust its value<span class="delete">.  (Section 7.4.1)</span></td><td> </td><td class="rblock">   required to always trust its value<span class="insert"> (Section 7.4.1).</span></td><td class="lineno" valign="top"></td></tr>
     2051      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     2052      <tr><td><a name="diff0131" /></td></tr>
     2053      <tr><td class="lineno" valign="top"></td><td class="lblock">   A Method Registry has been defined<span class="delete">.  (Section 8.1)</span></td><td> </td><td class="rblock">   A Method Registry has been defined<span class="insert"> (Section 8.1).</span></td><td class="lineno" valign="top"></td></tr>
     2054      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    21922055      <tr><td class="lineno" valign="top"></td><td class="left">   The Status Code Registry has been redefined by this specification;</td><td> </td><td class="right">   The Status Code Registry has been redefined by this specification;</td><td class="lineno" valign="top"></td></tr>
    2193       <tr><td><a name="diff0165" /></td></tr>
     2056      <tr><td><a name="diff0132" /></td></tr>
    21942057      <tr><td class="lineno" valign="top"></td><td class="lblock">   previously, it was defined in Section 7.1 of <span class="delete">[RFC2817].</span></td><td> </td><td class="rblock">   previously, it was defined in Section 7.1 of <span class="insert">[RFC2817]</span> (Section <span class="insert">8.2).</span></td><td class="lineno" valign="top"></td></tr>
     2058      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21952059      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">8.2)</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    21962060      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    2197       <tr><td><a name="diff0166" /></td></tr>
     2061      <tr><td><a name="diff0133" /></td></tr>
    21982062      <tr><td class="lineno" valign="top"></td><td class="lblock">   Registration of <span class="delete">Content Codings</span> has been changed to require IETF</td><td> </td><td class="rblock">   Registration of <span class="insert">content codings</span> has been changed to require IETF</td><td class="lineno" valign="top"></td></tr>
    21992063      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Review.</span>  (Section <span class="delete">8.4)</span></td><td> </td><td class="rblock">   <span class="insert">Review</span> (Section <span class="insert">8.4).</span></td><td class="lineno" valign="top"></td></tr>
     
    22092073      <tr><td class="lineno" valign="top"></td><td class="left">   The following core rules are included by reference, as defined in</td><td> </td><td class="right">   The following core rules are included by reference, as defined in</td><td class="lineno" valign="top"></td></tr>
    22102074      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    2211       <tr bgcolor="gray" ><td></td><th><a name="part-l49" /><small>skipping to change at</small><em> page 99, line 47</em></th><th> </th><th><a name="part-r49" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr>
     2075      <tr bgcolor="gray" ><td></td><th><a name="part-l50" /><small>skipping to change at</small><em> page 99, line 45</em></th><th> </th><th><a name="part-r50" /><small>skipping to change at</small><em> page 99, line 40</em></th><td></td></tr>
    22122076      <tr><td class="lineno" valign="top"></td><td class="left">      HEAD method  25</td><td> </td><td class="right">      HEAD method  25</td><td class="lineno" valign="top"></td></tr>
    22132077      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    22202084      <tr><td class="lineno" valign="top"></td><td class="left">   M</td><td> </td><td class="right">   M</td><td class="lineno" valign="top"></td></tr>
    22212085      <tr><td class="lineno" valign="top"></td><td class="left">      Max-Forwards header field  36</td><td> </td><td class="right">      Max-Forwards header field  36</td><td class="lineno" valign="top"></td></tr>
    2222       <tr><td><a name="diff0167" /></td></tr>
     2086      <tr><td><a name="diff0134" /></td></tr>
    22232087      <tr><td class="lineno" valign="top"></td><td class="lblock">      MIME-Version header field  8<span class="delete">9</span></td><td> </td><td class="rblock">      MIME-Version header field  8<span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    22242088      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    22342098
    22352099     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    2236      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 167 change blocks.&nbsp;</a></th></tr>
    2237      <tr class="stats"><td></td><th><i>403 lines changed or deleted</i></th><th><i> </i></th><th><i>377 lines changed or added</i></th><td></td></tr>
     2100     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 134 change blocks.&nbsp;</a></th></tr>
     2101     <tr class="stats"><td></td><th><i>307 lines changed or deleted</i></th><th><i> </i></th><th><i>283 lines changed or added</i></th><td></td></tr>
    22382102     <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>
    22392103   </table>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2633 r2635  
    28112811                  <p><b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart
    28122812                     for <a href="#status.301" class="smpl">301 (Moved
    2813                         Permanently)</a> (<a href="#status-308" id="rfc.xref.status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[status-308]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose).
     2813                        Permanently)</a> (<a href="#RFC7238" id="rfc.xref.RFC7238.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[RFC7238]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose).
    28142814                  </p>
    28152815               </div>
     
    44434443         </tr>
    44444444         <tr>
    4445             <td class="reference"><b id="status-308">[status-308]</b></td>
     4445            <td class="reference"><b id="RFC7238">[RFC7238]</b></td>
    44464446            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
    44474447            </td>
     
    50905090                     </ul>
    50915091                  </li>
     5092                  <li><em>RFC7238</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7238.1">6.4.7</a>, <a href="#RFC7238"><b>11.2</b></a></li>
    50925093               </ul>
    50935094            </li>
     
    51055106                     </ul>
    51065107                  </li>
    5107                   <li><em>status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.status-308.1">6.4.7</a>, <a href="#status-308"><b>11.2</b></a></li>
    51085108               </ul>
    51095109            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2633 r2635  
    32593259    that it does not allow changing the request method from POST to GET. This
    32603260    specification defines no equivalent counterpart for <x:ref>301 (Moved
    3261     Permanently)</x:ref> (<xref target="status-308"/>,
     3261    Permanently)</x:ref> (<xref target="RFC7238"/>,
    32623262    however, defines the status code 308 (Permanent Redirect) for this purpose).
    32633263  </t>
     
    57745774</reference>
    57755775
    5776 <reference anchor="status-308">
     5776<reference anchor="RFC7238">
    57775777        <front>
    57785778    <title abbrev="HTTP Status Code 308">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</title>
Note: See TracChangeset for help on using the changeset viewer.