Ignore:
Timestamp:
Feb 8, 2011, 4:23:14 PM (9 years ago)
Author:
fielding@…
Message:

Change the undefined use of "transparent proxy" to a definition
of transforming and non-transforming proxies. Add new definitions
for "intercepts" and the other kind of "transparent proxy".
Should we add informational references to RFC1919 and RFC3040 ?

Addresses #210

File:
1 edited

Legend:

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

    r1106 r1107  
    394394   mechanisms &MAY; be used, such as encryption at the transport level or
    395395   via message encapsulation, and with additional header fields
    396    specifying authentication information. However, these additional
     396   specifying authentication information. However, such additional
    397397   mechanisms are not defined by this specification.
    398398</t>
    399399<t>
    400    Proxies &MUST; be completely transparent regarding user agent
    401    authentication by origin servers. That is, they &MUST; forward the
    402    WWW-Authenticate and Authorization headers untouched, and follow the
    403    rules found in <xref target="header.authorization"/>. Both the Proxy-Authenticate and
    404    the Proxy-Authorization header fields are hop-by-hop headers (see
    405    &end-to-end.and-hop-by-hop;).
     400   Proxies &MUST; forward the WWW-Authenticate and Authorization headers
     401   unmodified and follow the rules found in <xref target="header.authorization"/>.
    406402</t>
    407403
Note: See TracChangeset for help on using the changeset viewer.