Changeset 2322

Timestamp:

29/07/13 15:00:32 (9 years ago)

Author:

julian.reschke@…

Message:

clarify Proxy-Authenticate and connections (see #473)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires January 16, 2014";
+       content: "Expires January 30, 2014";
   }
   @bottom-right {
@@ -489 +489 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-07-15">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-07-29">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
@@ -517 +517 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">July 15, 2013</td>
+               <td class="right">July 29, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: January 16, 2014</td>
+               <td class="left">Expires: January 30, 2014</td>
                <td class="right"></td>
             </tr>
@@ -546 +546 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 16, 2014.</p>
+      <p>This Internet-Draft will expire on January 30, 2014.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -744 +744 @@
       </p>
       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
-</pre><p id="rfc.section.4.2.p.3">Unlike <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>, the Proxy-Authenticate header field applies only to the current connection, and intermediaries <em class="bcp14">SHOULD NOT</em> 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.
+</pre><p id="rfc.section.4.2.p.3">Unlike <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>, the Proxy-Authenticate header field usually applies to the current connection, and proxies generally will consume it, rather
+         than forwarding 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.
       </p>
       <p id="rfc.section.4.2.p.4">Note that the parsing considerations for <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> apply to this header field as well; see <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;4.4</a> for details.
@@ -1143 +1144 @@
       </ul>
       <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p7-auth-23</a></h2>
-      <p id="rfc.section.D.5.p.1">None yet.</p>
+      <p id="rfc.section.D.5.p.1">Closed issues: </p>
+      <ul>
+         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/473">http://tools.ietf.org/wg/httpbis/trac/ticket/473</a>&gt;: "Forwarding Proxy-*"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.W">W</a> 

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

@@ -399 +399 @@
 <t>
    Unlike <x:ref>WWW-Authenticate</x:ref>, the Proxy-Authenticate header field
-   applies only to 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.
+   usually applies to the current connection, and proxies generally will
+   consume it, rather than forwarding 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.
 </t>
 <t>
@@ -1182 +1182 @@
 <section title="Since draft-ietf-httpbis-p7-auth-23" anchor="changes.since.23">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/473"/>:
+      "Forwarding Proxy-*"
+    </t>
+  </list>
 </t>
 </section>