Ignore:
Timestamp:
29/07/13 15:00:32 (7 years ago)
Author:
julian.reschke@…
Message:

clarify Proxy-Authenticate and connections (see #473)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2304 r2322  
    399399<t>
    400400   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 need
    403    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 the
    405    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.
    406406</t>
    407407<t>
     
    11821182<section title="Since draft-ietf-httpbis-p7-auth-23" anchor="changes.since.23">
    11831183<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>
    11851191</t>
    11861192</section>
Note: See TracChangeset for help on using the changeset viewer.