Changeset 1173 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

13/03/11 11:39:25 (10 years ago)

Author:

fielding@…

Message:

Clarify that gateways are just origin servers with additional
proxy issues and then refer only to origin servers when
describing their outbound requirements.

Consistently use the term URI instead of URL.

Rewrite the section on Host to be clear on where the information
comes from and how proxies differ from other clients.
Warn about security holes in stupid interception proxies.

Addresses #218

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1133 +1133 @@
    &SHOULD; reflect the message received back to the client as the
    message-body of a 200 (OK) response. The final recipient is either the
-   origin server or the first proxy or gateway to receive a Max-Forwards
+   origin server or the first proxy to receive a Max-Forwards
    value of zero (0) in the request (see <xref target="header.max-forwards"/>).
    A TRACE request &MUST-NOT; include a message-body.
@@ -2302 +2302 @@
    TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
    methods to limit the number of times that the request is forwarded by
-   proxies or gateways. This can be useful when the client is attempting to
+   proxies. This can be useful when the client is attempting to
    trace a request which appears to be failing or looping in mid-chain.
 </t>
@@ -2314 +2314 @@
 </t>
 <t>
-   Each proxy or gateway recipient of a TRACE or OPTIONS request
+   Each recipient of a TRACE or OPTIONS request
    containing a Max-Forwards header field &MUST; check and update its
    value prior to forwarding the request. If the received value is zero