Ignore:
Timestamp:
25/05/14 16:48:47 (6 years ago)
Author:
julian.reschke@…
Message:

Expand document names in introduction (#553)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p7-auth.unpg.txt

    r2692 r2693  
    127127     3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  7
    128128     3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  7
    129    4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  7
     129   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  8
    130130     4.1.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  8
    131      4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  8
     131     4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  9
    132132     4.3.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . .  9
    133      4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  9
     133     4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . . 10
    134134   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
    135135     5.1.  Authentication Scheme Registry . . . . . . . . . . . . . . 10
     
    143143     6.3.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . 14
    144144   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
    145    8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
    146      8.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     145   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     146     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
    147147     8.2.  Informative References . . . . . . . . . . . . . . . . . . 15
    148148   Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . 16
     
    180180   client request and by a client to provide authentication information.
    181181   This document defines HTTP/1.1 authentication in terms of the
    182    architecture defined in [RFC7230], including the general framework
    183    previously described in RFC 2617 and the related fields and status
    184    codes previously defined in RFC 2616.
     182   architecture defined in "Hypertext Transfer Protocol (HTTP/1.1):
     183   Message Syntax and Routing" [RFC7230], including the general
     184   framework previously described in "HTTP Authentication: Basic and
     185   Digest Access Authentication" [RFC2617] and the related fields and
     186   status codes previously defined in "Hypertext Transfer Protocol --
     187   HTTP/1.1" [RFC2616].
    185188
    186189   The IANA Authentication Scheme Registry (Section 5.1) lists
     
    218221   followed by additional information necessary for achieving
    219222   authentication via that scheme.  The latter can be either a comma-
     223
     224
     225
     226Fielding & Reschke      Expires November 26, 2014               [Page 4]
     227
     228
     229Internet-Draft           HTTP/1.1 Authentication                May 2014
     230
     231
    220232   separated list of parameters or a single sequence of characters
    221233   capable of holding base64-encoded information.
    222 
    223 
    224 
    225 
    226 Fielding & Reschke      Expires November 26, 2014               [Page 4]
    227 
    228 
    229 Internet-Draft           HTTP/1.1 Authentication                May 2014
    230 
    231234
    232235   Authentication parameters are name=value pairs, where the name token
     
    275278   Both the Authorization field value and the Proxy-Authorization field
    276279   value contain the client's credentials for the realm of the resource
     280
     281
     282
     283Fielding & Reschke      Expires November 26, 2014               [Page 5]
     284
     285
     286Internet-Draft           HTTP/1.1 Authentication                May 2014
     287
     288
    277289   being requested, based upon a challenge received in a response
    278290   (possibly at some point in the past).  When creating their values,
    279291   the user agent ought to do so by selecting the challenge with what it
    280 
    281 
    282 
    283 Fielding & Reschke      Expires November 26, 2014               [Page 5]
    284 
    285 
    286 Internet-Draft           HTTP/1.1 Authentication                May 2014
    287 
    288 
    289292   considers to be the most secure auth-scheme that it understands,
    290293   obtaining credentials from the user as appropriate.  Transmission of
     
    332335   spaces, each with its own authentication scheme and/or authorization
    333336   database.  The realm value is a string, generally assigned by the
     337
     338
     339
     340Fielding & Reschke      Expires November 26, 2014               [Page 6]
     341
     342
     343Internet-Draft           HTTP/1.1 Authentication                May 2014
     344
     345
    334346   origin server, that can have additional semantics specific to the
    335347   authentication scheme.  Note that a response can have multiple
    336348   challenges with the same auth-scheme but with different realms.
    337 
    338 
    339 
    340 Fielding & Reschke      Expires November 26, 2014               [Page 6]
    341 
    342 
    343 Internet-Draft           HTTP/1.1 Authentication                May 2014
    344 
    345349
    346350   The protection space determines the domain over which credentials can
     
    387391   field (Section 4.4).
    388392
     393
     394
     395
     396
     397Fielding & Reschke      Expires November 26, 2014               [Page 7]
     398
     399
     400Internet-Draft           HTTP/1.1 Authentication                May 2014
     401
     402
    3894034.  Header Field Definitions
    390404
    391405   This section defines the syntax and semantics of header fields
    392406   related to the HTTP authentication framework.
    393 
    394 
    395 
    396 
    397 Fielding & Reschke      Expires November 26, 2014               [Page 7]
    398 
    399 
    400 Internet-Draft           HTTP/1.1 Authentication                May 2014
    401 
    402407
    4034084.1.  WWW-Authenticate
     
    440445      and thus is harmless.
    441446
     447
     448
     449
     450
     451
     452
     453
     454Fielding & Reschke      Expires November 26, 2014               [Page 8]
     455
     456
     457Internet-Draft           HTTP/1.1 Authentication                May 2014
     458
     459
    4424604.2.  Authorization
    443461
     
    449467
    450468     Authorization = credentials
    451 
    452 
    453 
    454 Fielding & Reschke      Expires November 26, 2014               [Page 8]
    455 
    456 
    457 Internet-Draft           HTTP/1.1 Authentication                May 2014
    458 
    459469
    460470   If a request is authenticated and a realm specified, the same
     
    494504   this header field as well; see Section 4.1 for details.
    495505
     506
     507
     508
     509
     510
     511Fielding & Reschke      Expires November 26, 2014               [Page 9]
     512
     513
     514Internet-Draft           HTTP/1.1 Authentication                May 2014
     515
     516
    4965174.4.  Proxy-Authorization
    497518
     
    506527   Unlike Authorization, the Proxy-Authorization header field applies
    507528   only to the next inbound proxy that demanded authentication using the
    508 
    509 
    510 
    511 Fielding & Reschke      Expires November 26, 2014               [Page 9]
    512 
    513 
    514 Internet-Draft           HTTP/1.1 Authentication                May 2014
    515 
    516 
    517529   Proxy-Authenticate field.  When multiple proxies are used in a chain,
    518530   the Proxy-Authorization header field is consumed by the first inbound
     
    548560   There are certain aspects of the HTTP Authentication Framework that
    549561   put constraints on how new authentication schemes can work:
     562
     563
     564
     565
     566
     567
     568Fielding & Reschke      Expires November 26, 2014              [Page 10]
     569
     570
     571Internet-Draft           HTTP/1.1 Authentication                May 2014
     572
    550573
    551574   o  HTTP authentication is presumed to be stateless: all of the
     
    562585      NOT use it in a way incompatible with that definition.
    563586
    564 
    565 
    566 
    567 
    568 Fielding & Reschke      Expires November 26, 2014              [Page 10]
    569 
    570 
    571 Internet-Draft           HTTP/1.1 Authentication                May 2014
    572 
    573 
    574587   o  The "token68" notation was introduced for compatibility with
    575588      existing authentication schemes and can only be used once per
     
    607620      HTTP caches as the "private" Cache-Control response directive
    608621      (Section 5.2.2.6 of [RFC7234]), within the scope of the request in
     622
     623
     624
     625Fielding & Reschke      Expires November 26, 2014              [Page 11]
     626
     627
     628Internet-Draft           HTTP/1.1 Authentication                May 2014
     629
     630
    609631      which they appear.
    610632
     
    615637      (e.g., "no-store", Section 5.2.1.5 of [RFC7234]) or response
    616638      directives (e.g., "private").
    617 
    618 
    619 
    620 
    621 
    622 
    623 
    624 
    625 Fielding & Reschke      Expires November 26, 2014              [Page 11]
    626 
    627 
    628 Internet-Draft           HTTP/1.1 Authentication                May 2014
    629 
    630639
    6316405.2.  Status Code Registration
     
    668677   This section is meant to inform developers, information providers,
    669678   and users of known security concerns specific to HTTP authentication.
     679
     680
     681
     682Fielding & Reschke      Expires November 26, 2014              [Page 12]
     683
     684
     685Internet-Draft           HTTP/1.1 Authentication                May 2014
     686
     687
    670688   More general security considerations are addressed in HTTP messaging
    671689   [RFC7230] and semantics [RFC7231].
     
    677695   the potential considerations for specific authentication schemes
    678696   (which ought to be documented in the specifications that define those
    679 
    680 
    681 
    682 Fielding & Reschke      Expires November 26, 2014              [Page 12]
    683 
    684 
    685 Internet-Draft           HTTP/1.1 Authentication                May 2014
    686 
    687 
    688697   schemes).  Various organizations maintain topical information and
    689698   links to current research on Web application security (e.g.,
     
    725734   scheme definition.
    726735
     736
     737
     738
     739Fielding & Reschke      Expires November 26, 2014              [Page 13]
     740
     741
     742Internet-Draft           HTTP/1.1 Authentication                May 2014
     743
     744
    727745   Circumstances under which credential caching can interfere with the
    728746   application's security model include but are not limited to:
     
    734752   o  Applications that include a session termination indication (such
    735753      as a "logout" or "commit" button on a page) after which the server
    736 
    737 
    738 
    739 Fielding & Reschke      Expires November 26, 2014              [Page 13]
    740 
    741 
    742 Internet-Draft           HTTP/1.1 Authentication                May 2014
    743 
    744 
    745754      side of the application "knows" that there is no further reason
    746755      for the client to retain the credentials.
     
    7827918.  References
    783792
     793
     794
     795
     796Fielding & Reschke      Expires November 26, 2014              [Page 14]
     797
     798
     799Internet-Draft           HTTP/1.1 Authentication                May 2014
     800
     801
    7848028.1.  Normative References
    785803
     
    791809
    792810   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
    793 
    794 
    795 
    796 Fielding & Reschke      Expires November 26, 2014              [Page 14]
    797 
    798 
    799 Internet-Draft           HTTP/1.1 Authentication                May 2014
    800 
    801 
    802811              Protocol (HTTP/1.1): Message Syntax and Routing",
    803812              draft-ietf-httpbis-p1-messaging-latest (work in progress),
     
    839848
    840849   [RFC4648]  Josefsson, S., "The Base16, Base32, and Base64 Data
     850
     851
     852
     853Fielding & Reschke      Expires November 26, 2014              [Page 15]
     854
     855
     856Internet-Draft           HTTP/1.1 Authentication                May 2014
     857
     858
    841859              Encodings", RFC 4648, October 2006.
    842860
     
    847865   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
    848866              (TLS) Protocol Version 1.2", RFC 5246, August 2008.
    849 
    850 
    851 
    852 
    853 Fielding & Reschke      Expires November 26, 2014              [Page 15]
    854 
    855 
    856 Internet-Draft           HTTP/1.1 Authentication                May 2014
    857 
    858867
    859868Appendix A.  Changes from RFCs 2616 and 2617
     
    899908
    900909
    901 
    902 
    903 
    904 
    905 
    906 
    907 
    908 
    909 
    910910Fielding & Reschke      Expires November 26, 2014              [Page 16]
    911911
     
    948948
    949949   A
    950       Authorization header field  8
     950      Authorization header field  9
    951951
    952952   C
     
    957957         auth-param  5
    958958         auth-scheme  5
    959          Authorization  8
     959         Authorization  9
    960960         challenge  5
    961961         credentials  6
    962962         Proxy-Authenticate  9
    963          Proxy-Authorization  9
     963         Proxy-Authorization  10
    964964
    965965
     
    977977      Protection Space  6
    978978      Proxy-Authenticate header field  9
    979       Proxy-Authorization header field  9
     979      Proxy-Authorization header field  10
    980980
    981981   R
  • draft-ietf-httpbis/latest/auth48/rfc7235.abdiff.txt

    r2692 r2693  
    112112      3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  7
    113113      3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  7
    114     4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  7
     114    4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  8
    115115      4.1.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  8
    116       4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  8
     116      4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  9
    117117      4.3.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . .  9
    118       4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  9
     118      4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . . 10
    119119    5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
    120120      5.1.  Authentication Scheme Registry . . . . . . . . . . . . . . 10
     
    128128      6.3.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . 14
    129129    7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
    130     8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
    131       8.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     130    8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     131      8.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
    132132      8.2.  Informative References . . . . . . . . . . . . . . . . . . 15
    133133    Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . 16
     
    180180    client request and by a client to provide authentication information.
    181181    This document defines HTTP/1.1 authentication in terms of the
    182     architecture defined in [RFC7230], including the general framework
    183     previously described in RFC 2617 and the related fields and status
    184     codes previously defined in RFC 2616.
     182    architecture defined in "Hypertext Transfer Protocol (HTTP/1.1):
     183    Message Syntax and Routing" [RFC7230], including the general
     184    framework previously described in "HTTP Authentication: Basic and
     185    Digest Access Authentication" [RFC2617] and the related fields and
     186    status codes previously defined in "Hypertext Transfer Protocol --
     187    HTTP/1.1" [RFC2616].
    185188
    186189NEW:
     
    252255    associated registry entries have been updated according to the
    253256    permanent registrations below (see [BCP90]):
     257
     258
     259Section 6., paragraph 1:
     260OLD:
     261
     262    This section is meant to inform developers, information providers,
     263    and users of known security concerns specific to HTTP authentication.
     264 
     265    More general security considerations are addressed in HTTP messaging
     266    [RFC7230] and semantics [RFC7231].
     267
     268NEW:
     269
     270    This section is meant to inform developers, information providers,
     271    and users of known security concerns specific to HTTP authentication.
     272    More general security considerations are addressed in HTTP messaging
     273    [RFC7230] and semantics [RFC7231].
    254274
    255275
     
    280300
    281301
     302Section 8.1., paragraph 0:
     303OLD:
     304
     305 8.  References
     306 8.1.  Normative References
     307
     308NEW:
     309
     310 8.  References
     311 
     312 8.1.  Normative References
     313
     314
    282315Section 8.1., paragraph 3:
    283316OLD:
     
    343376
    344377    A
    345        Authorization header field  8
     378       Authorization header field  9
    346379
    347380NEW:
     
    370403          auth-param  5
    371404          auth-scheme  5
    372           Authorization  8
     405          Authorization  9
    373406          challenge  5
    374407          credentials  6
    375408          Proxy-Authenticate  9
    376           Proxy-Authorization  9
     409          Proxy-Authorization  10
    377410          token68  5
    378411          WWW-Authenticate  8
     
    399432       Protection Space  6
    400433       Proxy-Authenticate header field  9
    401        Proxy-Authorization header field  9
     434       Proxy-Authorization header field  10
    402435
    403436NEW:
  • draft-ietf-httpbis/latest/auth48/rfc7235.diff.html

    r2692 r2693  
    125125      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  <span class="delete">7</span></td><td> </td><td class="rblock">     3.1.  401 Unauthorized . . . . . . . . . . . . . . . . . . . . .  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    126126      <tr><td class="lineno" valign="top"></td><td class="lblock">     3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  <span class="delete">7</span></td><td> </td><td class="rblock">     3.2.  407 Proxy Authentication Required  . . . . . . . . . . . .  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    127       <tr><td class="lineno" valign="top"></td><td class="lblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="delete">7</span></td><td> </td><td class="rblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
     127      <tr><td class="lineno" valign="top"></td><td class="lblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="delete">8</span></td><td> </td><td class="rblock">   4.  Header Field Definitions . . . . . . . . . . . . . . . . . . .  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    128128      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.1.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  <span class="delete">8</span></td><td> </td><td class="rblock">     4.1.  WWW-Authenticate . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    129       <tr><td class="lineno" valign="top"></td><td class="lblock">     4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">8</span></td><td> </td><td class="rblock">     4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     129      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.2.  Authorization  . . . . . . . . . . . . . . . . . . . . . .  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    130130      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.3.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.3.  Proxy-Authenticate . . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    131       <tr><td class="lineno" valign="top"></td><td class="lblock">     4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">     4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
     131      <tr><td class="lineno" valign="top"></td><td class="lblock">     4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">     4.4.  Proxy-Authorization  . . . . . . . . . . . . . . . . . . .  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    132132      <tr><td class="lineno" valign="top"></td><td class="lblock">   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
    133133      <tr><td class="lineno" valign="top"></td><td class="lblock">     5.1.  Authentication Scheme Registry . . . . . . . . . . . . . . <span class="delete">10</span></td><td> </td><td class="rblock">     5.1.  Authentication Scheme Registry . . . . . . . . . . . . . .  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
     
    141141      <tr><td class="lineno" valign="top"></td><td class="lblock">     6.3.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . <span class="delete">14</span></td><td> </td><td class="rblock">     6.3.  Protection Spaces  . . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
    142142      <tr><td class="lineno" valign="top"></td><td class="lblock">   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">14</span></td><td> </td><td class="rblock">   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
    143       <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">14</span></td><td> </td><td class="rblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
    144       <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="delete">14</span></td><td> </td><td class="rblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
     143      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">15</span></td><td> </td><td class="rblock">   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
     144      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="delete">15</span></td><td> </td><td class="rblock">     8.1.  Normative References . . . . . . . . . . . . . . . . . . . <span class="insert">13</span></td><td class="lineno" valign="top"></td></tr>
    145145      <tr><td class="lineno" valign="top"></td><td class="lblock">     8.2.  Informative References . . . . . . . . . . . . . . . . . . <span class="delete">15</span></td><td> </td><td class="rblock">     8.2.  Informative References . . . . . . . . . . . . . . . . . . <span class="insert">14</span></td><td class="lineno" valign="top"></td></tr>
    146146      <tr><td class="lineno" valign="top"></td><td class="lblock">   Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . <span class="delete">16</span></td><td> </td><td class="rblock">   Appendix A.  Changes from RFCs 2616 and 2617 . . . . . . . . . . . <span class="insert">15</span></td><td class="lineno" valign="top"></td></tr>
     
    156156      <tr><td class="lineno" valign="top"></td><td class="left">   client request and by a client to provide authentication information.</td><td> </td><td class="right">   client request and by a client to provide authentication information.</td><td class="lineno" valign="top"></td></tr>
    157157      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines HTTP/1.1 authentication in terms of the</td><td> </td><td class="right">   This document defines HTTP/1.1 authentication in terms of the</td><td class="lineno" valign="top"></td></tr>
    158       <tr><td class="lineno" valign="top"></td><td class="left">   architecture defined in [RFC7230], including the general framework</td><td> </td><td class="right">   architecture defined in [RFC7230], including the general framework</td><td class="lineno" valign="top"></td></tr>
    159158      <tr><td><a name="diff0008" /></td></tr>
    160       <tr><td class="lineno" valign="top"></td><td class="lblock">   previously described in <span class="delete">RFC 2617</span> and the related fields and status</td><td> </td><td class="rblock">   previously described in <span class="insert">[RFC2617]</span> and the related fields and status</td><td class="lineno" valign="top"></td></tr>
    161       <tr><td class="lineno" valign="top"></td><td class="lblock">   codes previously defined in <span class="delete">RFC 2616.</span></td><td> </td><td class="rblock">   codes previously defined in <span class="insert">[RFC2616].</span></td><td class="lineno" valign="top"></td></tr>
     159      <tr><td class="lineno" valign="top"></td><td class="lblock">   architecture defined in <span class="delete">"Hypertext Transfer Protocol (HTTP/1.1):</span></td><td> </td><td class="rblock">   architecture defined in [RFC7230], including the general framework</td><td class="lineno" valign="top"></td></tr>
     160      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Message Syntax and Routing"</span> [RFC7230], including the general</td><td> </td><td class="rblock">   previously described in [RFC2617] and the related fields and status</td><td class="lineno" valign="top"></td></tr>
     161      <tr><td class="lineno" valign="top"></td><td class="lblock">   framework previously described in <span class="delete">"HTTP Authentication: Basic and</span></td><td> </td><td class="rblock">   codes previously defined in [RFC2616].</td><td class="lineno" valign="top"></td></tr>
     162      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Digest Access Authentication"</span> [RFC2617] and the related fields and</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     163      <tr><td class="lineno" valign="top"></td><td class="lblock">   status codes previously defined in <span class="delete">"Hypertext Transfer Protocol --</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     164      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   HTTP/1.1"</span> [RFC2616].</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    162165      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    163166      <tr><td class="lineno" valign="top"></td><td class="left">   The IANA Authentication Scheme Registry (Section 5.1) lists</td><td> </td><td class="right">   The IANA Authentication Scheme Registry (Section 5.1) lists</td><td class="lineno" valign="top"></td></tr>
     
    171174      <tr><td class="lineno" valign="top"></td><td class="left">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno" valign="top"></td></tr>
    172175      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    173       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 10, line 15</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 9, line 15</em></th><td></td></tr>
     176      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 10, line 28</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 9, line 15</em></th><td></td></tr>
    174177      <tr><td class="lineno" valign="top"></td><td class="left">   the Proxy-Authorization header field is consumed by the first inbound</td><td> </td><td class="right">   the Proxy-Authorization header field is consumed by the first inbound</td><td class="lineno" valign="top"></td></tr>
    175178      <tr><td class="lineno" valign="top"></td><td class="left">   proxy that was expecting to receive credentials.  A proxy MAY relay</td><td> </td><td class="right">   proxy that was expecting to receive credentials.  A proxy MAY relay</td><td class="lineno" valign="top"></td></tr>
     
    211214      <tr><td class="lineno" valign="top"></td><td class="left">      in the request, rather than be dependent on the server remembering</td><td> </td><td class="right">      in the request, rather than be dependent on the server remembering</td><td class="lineno" valign="top"></td></tr>
    212215      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    213       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 12, line 7</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 11, line 7</em></th><td></td></tr>
     216      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 12, line 15</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 11, line 7</em></th><td></td></tr>
    214217      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    215218      <tr><td class="lineno" valign="top"></td><td class="left">      Therefore, new authentication schemes that choose not to carry</td><td> </td><td class="right">      Therefore, new authentication schemes that choose not to carry</td><td class="lineno" valign="top"></td></tr>
     
    256259      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    257260      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    258       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 13, line 23</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 12, line 23</em></th><td></td></tr>
     261      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 13, line 33</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 12, line 23</em></th><td></td></tr>
    259262      <tr><td class="lineno" valign="top"></td><td class="left">   authentication scheme defines how the credentials are encoded prior</td><td> </td><td class="right">   authentication scheme defines how the credentials are encoded prior</td><td class="lineno" valign="top"></td></tr>
    260263      <tr><td class="lineno" valign="top"></td><td class="left">   to transmission.  While this provides flexibility for the development</td><td> </td><td class="right">   to transmission.  While this provides flexibility for the development</td><td class="lineno" valign="top"></td></tr>
     
    280283      <tr><td class="lineno" valign="top"></td><td class="left">6.2.  Authentication Credentials and Idle Clients</td><td> </td><td class="right">6.2.  Authentication Credentials and Idle Clients</td><td class="lineno" valign="top"></td></tr>
    281284      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    282       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 15, line 5</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
     285      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 15, line 14</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 14, line 5</em></th><td></td></tr>
    283286      <tr><td class="lineno" valign="top"></td><td class="left">8.1.  Normative References</td><td> </td><td class="right">8.1.  Normative References</td><td class="lineno" valign="top"></td></tr>
    284287      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    334337      <tr><td class="lineno" valign="top"></td><td class="left">   A</td><td> </td><td class="right">   A</td><td class="lineno" valign="top"></td></tr>
    335338      <tr><td><a name="diff0019" /></td></tr>
    336       <tr><td class="lineno" valign="top"></td><td class="lblock">      Authorization header field  <span class="delete">8</span></td><td> </td><td class="rblock">      Authorization header field  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     339      <tr><td class="lineno" valign="top"></td><td class="lblock">      Authorization header field  <span class="delete">9</span></td><td> </td><td class="rblock">      Authorization header field  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    337340      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    338341      <tr><td class="lineno" valign="top"></td><td class="left">   C</td><td> </td><td class="right">   C</td><td class="lineno" valign="top"></td></tr>
     
    345348      <tr><td class="lineno" valign="top"></td><td class="lblock">         auth-param  <span class="delete">5</span></td><td> </td><td class="rblock">         auth-param  <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    346349      <tr><td class="lineno" valign="top"></td><td class="lblock">         auth-scheme  <span class="delete">5</span></td><td> </td><td class="rblock">         auth-scheme  <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    347       <tr><td class="lineno" valign="top"></td><td class="lblock">         Authorization  <span class="delete">8</span></td><td> </td><td class="rblock">         Authorization  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     350      <tr><td class="lineno" valign="top"></td><td class="lblock">         Authorization  <span class="delete">9</span></td><td> </td><td class="rblock">         Authorization  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
    348351      <tr><td class="lineno" valign="top"></td><td class="lblock">         challenge  <span class="delete">5</span></td><td> </td><td class="rblock">         challenge  <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    349352      <tr><td class="lineno" valign="top"></td><td class="lblock">         credentials  <span class="delete">6</span></td><td> </td><td class="rblock">         credentials  <span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
    350353      <tr><td class="lineno" valign="top"></td><td class="lblock">         Proxy-Authenticate  <span class="delete">9</span></td><td> </td><td class="rblock">         Proxy-Authenticate  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    351       <tr><td class="lineno" valign="top"></td><td class="lblock">         Proxy-Authorization  <span class="delete">9</span></td><td> </td><td class="rblock">         Proxy-Authorization  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
     354      <tr><td class="lineno" valign="top"></td><td class="lblock">         Proxy-Authorization  <span class="delete">10</span></td><td> </td><td class="rblock">         Proxy-Authorization  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    352355      <tr><td class="lineno" valign="top"></td><td class="lblock">         token68  <span class="delete">5</span></td><td> </td><td class="rblock">         token68  <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    353356      <tr><td class="lineno" valign="top"></td><td class="lblock">         WWW-Authenticate  <span class="delete">8</span></td><td> </td><td class="rblock">         WWW-Authenticate  <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
     
    357360      <tr><td class="lineno" valign="top"></td><td class="lblock">      Protection Space  <span class="delete">6</span></td><td> </td><td class="rblock">      Protection Space  <span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
    358361      <tr><td class="lineno" valign="top"></td><td class="lblock">      Proxy-Authenticate header field  <span class="delete">9</span></td><td> </td><td class="rblock">      Proxy-Authenticate header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    359       <tr><td class="lineno" valign="top"></td><td class="lblock">      Proxy-Authorization header field  <span class="delete">9</span></td><td> </td><td class="rblock">      Proxy-Authorization header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
     362      <tr><td class="lineno" valign="top"></td><td class="lblock">      Proxy-Authorization header field  <span class="delete">10</span></td><td> </td><td class="rblock">      Proxy-Authorization header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    360363      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    361364      <tr><td class="lineno" valign="top"></td><td class="left">   R</td><td> </td><td class="right">   R</td><td class="lineno" valign="top"></td></tr>
     
    379382     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    380383     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 24 change blocks.&nbsp;</a></th></tr>
    381      <tr class="stats"><td></td><th><i>106 lines changed or deleted</i></th><th><i> </i></th><th><i>85 lines changed or added</i></th><td></td></tr>
     384     <tr class="stats"><td></td><th><i>110 lines changed or deleted</i></th><th><i> </i></th><th><i>86 lines changed or added</i></th><td></td></tr>
    382385     <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>
    383386   </table>
  • draft-ietf-httpbis/latest/p7-auth.html

    r2692 r2693  
    636636         <p id="rfc.section.1.p.1">HTTP provides a general framework for access control and authentication, via an extensible set of challenge-response authentication
    637637            schemes, which can be used by a server to challenge a client request and by a client to provide authentication information.
    638             This document defines HTTP/1.1 authentication in terms of the architecture defined in <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, including the general framework previously described in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.1">RFC 2617</cite> and the related fields and status codes previously defined in <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>.
     638            This document defines HTTP/1.1 authentication in terms of the architecture defined in "Hypertext Transfer Protocol (HTTP/1.1):
     639            Message Syntax and Routing" <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, including the general framework previously described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a> and the related fields and status codes previously defined in "Hypertext Transfer Protocol -- HTTP/1.1" <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    639640         </p>
    640641         <p id="rfc.section.1.p.2">The IANA Authentication Scheme Registry (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section&nbsp;5.1</a>) lists registered authentication schemes and their corresponding specifications, including the "basic" and "digest" authentication
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2692 r2693  
    125125   provide authentication information. This document defines HTTP/1.1
    126126   authentication in terms of the architecture defined in
     127   "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"
    127128   <xref target="RFC7230"/>, including the general framework previously
    128    described in <xref target="RFC2617" x:fmt="none">RFC 2617</xref> and
     129   described in "HTTP Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/> and
    129130   the related fields and status codes previously defined in
    130    <xref target="RFC2616" x:fmt="none">RFC 2616</xref>.
     131   "Hypertext Transfer Protocol -- HTTP/1.1" <xref target="RFC2616"/>.
    131132</t>
    132133<t>
Note: See TracChangeset for help on using the changeset viewer.