Changeset 2449

Timestamp:

Oct 30, 2013, 6:28:02 AM (6 years ago)

Author:

julian.reschke@…

Message:

s/upon a request/upon receipt of a request/ (see #510)

Location:

draft-ietf-httpbis/latest

Files:

• p7-auth.html (modified) (2 diffs)
• p7-auth.xml (modified) (2 diffs)

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

@@ -684 +684 @@
             </p>
             <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#challenge.and.response" class="smpl">credentials</a> = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#imported.abnf" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">token68</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
-</pre><p id="rfc.section.2.1.p.14">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 <em class="bcp14">SHOULD</em> send a <a href="#status.401" class="smpl">401 (Unauthorized)</a> response that contains a <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> header field with at least one (possibly new) challenge applicable to the requested resource.
-            </p>
-            <p id="rfc.section.2.1.p.15">Likewise, upon a request that requires authentication by proxies that omit credentials or contain invalid or partial credentials,
-               a proxy <em class="bcp14">SHOULD</em> send a <a href="#status.407" class="smpl">407 (Proxy Authentication Required)</a> response that contains a <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field with a (possibly new) challenge applicable to the proxy.
+</pre><p id="rfc.section.2.1.p.14">Upon receipt of 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 <em class="bcp14">SHOULD</em> send a <a href="#status.401" class="smpl">401 (Unauthorized)</a> response that contains a <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> header field with at least one (possibly new) challenge applicable to the requested resource.
+            </p>
+            <p id="rfc.section.2.1.p.15">Likewise, upon receipt of a request that requires authentication by proxies that omit credentials or contain invalid or partial
+               credentials, a proxy <em class="bcp14">SHOULD</em> send a <a href="#status.407" class="smpl">407 (Proxy Authentication Required)</a> response that contains a <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field with a (possibly new) challenge applicable to the proxy.
             </p>
             <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>).
@@ -1162 +1162 @@
                </li>
             </ul>
+            <p id="rfc.section.D.1.p.2">Partly resolved issues: </p>
+            <ul>
+               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/510">http://tools.ietf.org/wg/httpbis/trac/ticket/510</a>&gt;: "SECDIR review of draft-ietf-httpbis-p7-auth-24"
+               </li>
+            </ul>
          </div>
       </div>

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

@@ -243 +243 @@
 </artwork></figure>
 <t>
-   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; send a <x:ref>401 (Unauthorized)</x:ref> response that
+   Upon receipt of 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; send a <x:ref>401 (Unauthorized)</x:ref> response that
    contains a <x:ref>WWW-Authenticate</x:ref> header field with 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;
-   send a <x:ref>407 (Proxy Authentication Required)</x:ref> response that
-   contains a <x:ref>Proxy-Authenticate</x:ref> header field with a (possibly
-   new) challenge applicable to the proxy.
+   Likewise, upon receipt of a request that requires authentication by proxies
+   that omit credentials or contain invalid or partial credentials, a proxy
+   &SHOULD; send a <x:ref>407 (Proxy Authentication Required)</x:ref> response
+   that contains a <x:ref>Proxy-Authenticate</x:ref> header field with a
+   (possibly new) challenge applicable to the proxy.
 </t>
 <t>
@@ -1107 +1107 @@
   </list>
 </t>
+<t>
+  Partly resolved issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/510"/>:
+      "SECDIR review of draft-ietf-httpbis-p7-auth-24"
+    </t>
+  </list>
+</t>
 </section>
 </section>