Changeset 2322
- Timestamp:
- 29/07/13 15:00:32 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.html
r2304 r2322 449 449 } 450 450 @bottom-center { 451 content: "Expires January 16, 2014";451 content: "Expires January 30, 2014"; 452 452 } 453 453 @bottom-right { … … 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2013-07- 15">491 <meta name="dct.issued" scheme="ISO8601" content="2013-07-29"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <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> 518 518 <td class="left">Intended status: Standards Track</td> 519 <td class="right">July 15, 2013</td>519 <td class="right">July 29, 2013</td> 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: January 16, 2014</td>522 <td class="left">Expires: January 30, 2014</td> 523 523 <td class="right"></td> 524 524 </tr> … … 546 546 in progress”. 547 547 </p> 548 <p>This Internet-Draft will expire on January 16, 2014.</p>548 <p>This Internet-Draft will expire on January 30, 2014.</p> 549 549 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 550 550 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 744 744 </p> 745 745 <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> 746 </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 747 from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate header 748 field. 746 </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 747 than forwarding it to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting 748 them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate 749 header field. 749 750 </p> 750 751 <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 4.4</a> for details. … … 1143 1144 </ul> 1144 1145 <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p7-auth-23</a></h2> 1145 <p id="rfc.section.D.5.p.1">None yet.</p> 1146 <p id="rfc.section.D.5.p.1">Closed issues: </p> 1147 <ul> 1148 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/473">http://tools.ietf.org/wg/httpbis/trac/ticket/473</a>>: "Forwarding Proxy-*" 1149 </li> 1150 </ul> 1146 1151 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1147 1152 <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
r2304 r2322 399 399 <t> 400 400 Unlike <x:ref>WWW-Authenticate</x:ref>, the Proxy-Authenticate header field 401 applies only to the current connection, and intermediaries &SHOULD-NOT;402 forward it to downstream clients. However, an intermediate proxy might need403 to obtain its own credentials by requesting them from the downstream client,404 which in some circumstances will appear as if the proxy is forwarding the405 Proxy-Authenticate header field.401 usually applies to the current connection, and proxies generally will 402 consume it, rather than forwarding it to downstream clients. However, an 403 intermediate proxy might need to obtain its own credentials by requesting 404 them from the downstream client, which in some circumstances will appear as 405 if the proxy is forwarding the Proxy-Authenticate header field. 406 406 </t> 407 407 <t> … … 1182 1182 <section title="Since draft-ietf-httpbis-p7-auth-23" anchor="changes.since.23"> 1183 1183 <t> 1184 None yet. 1184 Closed issues: 1185 <list style="symbols"> 1186 <t> 1187 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/473"/>: 1188 "Forwarding Proxy-*" 1189 </t> 1190 </list> 1185 1191 </t> 1186 1192 </section>
Note: See TracChangeset
for help on using the changeset viewer.