Changeset 2452

Timestamp:

30/10/13 16:16:19 (9 years ago)

Author:

julian.reschke@…

Message:

s/The HTTP protocol/HTTP/

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

@@ -692 +692 @@
             <p id="rfc.section.2.1.p.16">A server receiving credentials that are valid, but not adequate to gain access, ought to respond with the <a href="p2-semantics.html#status.403" class="smpl">403 (Forbidden)</a> status code (<a href="p2-semantics.html#status.403" title="403 Forbidden">Section 6.5.3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).
             </p>
-            <p id="rfc.section.2.1.p.17">The HTTP protocol 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.
+            <p id="rfc.section.2.1.p.17">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.
             </p>
             <p id="rfc.section.2.1.p.18">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

@@ -262 +262 @@
 </t>
 <t>
-   The HTTP protocol does not restrict applications to this simple
+   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