Changeset 1107 for draft-ietf-httpbis/latest/p7-auth.xml

Timestamp:

09/02/11 00:23:14 (10 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:

• draft-ietf-httpbis/latest/p7-auth.xml (modified) (1 diff)

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

@@ -394 +394 @@
    mechanisms &MAY; be used, such as encryption at the transport level or
    via message encapsulation, and with additional header fields
-   specifying authentication information. However, these additional
+   specifying authentication information. However, such additional
    mechanisms are not defined by this specification.
 </t>
 <t>
-   Proxies &MUST; be completely transparent regarding user agent
-   authentication by origin servers. That is, they &MUST; forward the
-   WWW-Authenticate and Authorization headers untouched, and follow the
-   rules found in <xref target="header.authorization"/>. Both the Proxy-Authenticate and
-   the Proxy-Authorization header fields are hop-by-hop headers (see
-   &end-to-end.and-hop-by-hop;).
+   Proxies &MUST; forward the WWW-Authenticate and Authorization headers
+   unmodified and follow the rules found in <xref target="header.authorization"/>.
 </t>