Ignore:
Timestamp:
Mar 13, 2011, 4:39:25 AM (9 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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1168 r1173  
    11331133   &SHOULD; reflect the message received back to the client as the
    11341134   message-body of a 200 (OK) response. The final recipient is either the
    1135    origin server or the first proxy or gateway to receive a Max-Forwards
     1135   origin server or the first proxy to receive a Max-Forwards
    11361136   value of zero (0) in the request (see <xref target="header.max-forwards"/>).
    11371137   A TRACE request &MUST-NOT; include a message-body.
     
    23022302   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
    23032303   methods to limit the number of times that the request is forwarded by
    2304    proxies or gateways. This can be useful when the client is attempting to
     2304   proxies. This can be useful when the client is attempting to
    23052305   trace a request which appears to be failing or looping in mid-chain.
    23062306</t>
     
    23142314</t>
    23152315<t>
    2316    Each proxy or gateway recipient of a TRACE or OPTIONS request
     2316   Each recipient of a TRACE or OPTIONS request
    23172317   containing a Max-Forwards header field &MUST; check and update its
    23182318   value prior to forwarding the request. If the received value is zero
Note: See TracChangeset for help on using the changeset viewer.