Changeset 2463

Timestamp:

01/11/13 13:10:26 (9 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p7-auth.html (modified) (1 diff)
• p7-auth.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p7-auth.html

@@ -688 +688 @@
             </p>
             <p id="rfc.section.2.1.p.16">HTTP does not restrict applications to this simple challenge-response framework for access authentication. Additional mechanisms
-               can be used, such as encryption at the transport level or via message encapsulation, and with additional header fields specifying
-               authentication information. However, such additional mechanisms are not defined by this specification.
+               can be used, such as authentication at the transport level or via message encapsulation, and with additional header fields
+               specifying authentication information. However, such additional mechanisms are not defined by this specification.
             </p>
             <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

@@ -253 +253 @@
 </t>
 <t>
-   HTTP does not restrict applications to this simple
-   challenge-response framework for access authentication. Additional
-   mechanisms can be used, such as encryption at the transport level or
-   via message encapsulation, and with additional header fields
-   specifying authentication information. However, such additional
-   mechanisms are not defined by this specification.
+   HTTP does not restrict applications to this simple challenge-response
+   framework for access authentication. Additional mechanisms can be used, such
+   as authentication at the transport level or via message encapsulation, and
+   with additional header fields specifying authentication information. However,
+   such additional mechanisms are not defined by this specification.
 </t>
 <t>