Ignore:
Timestamp:
01/11/13 13:10:26 (7 years ago)
Author:
julian.reschke@…
Message:

Rephrase statement about additional methods to authenticate (see #510)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.html

    r2461 r2463  
    688688            </p>
    689689            <p id="rfc.section.2.1.p.16">HTTP does not restrict applications to this simple challenge-response framework for access authentication. Additional mechanisms
    690                can be used, such as encryption at the transport level or via message encapsulation, and with additional header fields specifying
    691                authentication information. However, such additional mechanisms are not defined by this specification.
     690               can be used, such as authentication at the transport level or via message encapsulation, and with additional header fields
     691               specifying authentication information. However, such additional mechanisms are not defined by this specification.
    692692            </p>
    693693            <p id="rfc.section.2.1.p.17">A proxy <em class="bcp14">MUST</em> forward the <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> and <a href="#header.authorization" class="smpl">Authorization</a> header fields unmodified and follow the rules found in <a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;4.1</a>.
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2461 r2463  
    253253</t>
    254254<t>
    255    HTTP does not restrict applications to this simple
    256    challenge-response framework for access authentication. Additional
    257    mechanisms can be used, such as encryption at the transport level or
    258    via message encapsulation, and with additional header fields
    259    specifying authentication information. However, such additional
    260    mechanisms are not defined by this specification.
     255   HTTP does not restrict applications to this simple challenge-response
     256   framework for access authentication. Additional mechanisms can be used, such
     257   as authentication at the transport level or via message encapsulation, and
     258   with additional header fields specifying authentication information. However,
     259   such additional mechanisms are not defined by this specification.
    261260</t>
    262261<t>
Note: See TracChangeset for help on using the changeset viewer.