Changeset 1694 for draft-ietf-httpbis/latest/p7-auth.xml

Timestamp:

24/06/12 09:50:41 (10 years ago)

Author:

julian.reschke@…

Message:

tune conformance language (see #271)

File:

• draft-ietf-httpbis/latest/p7-auth.xml (modified) (2 diffs)

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

@@ -313 +313 @@
 </artwork></figure>
 <t>
-   Requests for protected resources that omit credentials, contain invalid
-   credentials (e.g., a bad password), or partial credentials (e.g., when the
-   authentication scheme requires more than one round trip) &SHOULD; return a
-   401 (Unauthorized) response. Such responses &MUST; include a
-   WWW-Authenticate header field containing at least one (possibly new)
-   challenge applicable to the requested resource.
-</t>
-<t>
-   Likewise, requests that require authentication by proxies that omit
-   credentials, or contain invalid or partial credentials &SHOULD; return a
-   407 (Proxy Authentication Required) response. Such responses &MUST;
-   include a Proxy-Authenticate header field containing a (possibly new)
-   challenge applicable to the proxy.
+   Upon a request for a protected resource that omits credentials, contains
+   invalid credentials (e.g., a bad password) or partial credentials (e.g.,
+   when the authentication scheme requires more than one round trip), an origin
+   server &SHOULD; return a 401 (Unauthorized) response. Such responses &MUST;
+   include a WWW-Authenticate header field containing at least one (possibly
+   new) challenge applicable to the requested resource.
+</t>
+<t>
+   Likewise, upon a request that requires authentication by proxies that omit
+   credentials or contain invalid or partial credentials, a proxy &SHOULD;
+   return a 407 (Proxy Authentication Required) response. Such responses
+   &MUST; include a Proxy-Authenticate header field containing a (possibly
+   new) challenge applicable to the proxy.
 </t>
 <t>
@@ -600 +600 @@
 <t>
    Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to
-   the current connection and &SHOULD-NOT;  be passed on to downstream
-   clients. However, an intermediate proxy might need to obtain its own
-   credentials by requesting them from the downstream client, which in
+   the current connection, and intermediaries &SHOULD-NOT;  forward it to
+   downstream clients. However, an intermediate proxy might need to obtain its
+   own credentials by requesting them from the downstream client, which in
    some circumstances will appear as if the proxy is forwarding the
    Proxy-Authenticate header field.