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/p6-cache.xml

    r1166 r1173  
    679679      <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt=","
    680680      x:sec="13.9"/>) required that caches do not calculate heuristic
    681       freshness for URLs with query components (i.e., those containing '?').
     681      freshness for URIs with query components (i.e., those containing '?').
    682682      In practice, this has not been widely implemented. Therefore, servers
    683683      are encouraged to send explicit directives (e.g., Cache-Control:
     
    11001100</x:note>
    11011101<t>
    1102    An intermediary (i.e., a proxy or gateway, whether or not it implements
    1103    a cache) &MUST; pass cache directives through, regardless of their
     1102   A proxy, whether or not it implements a cache, &MUST; pass cache directives
     1103   through in forwarded messages, regardless of their
    11041104   significance to that application, since the directives might be applicable
    11051105   to all recipients along the request/response chain. It is not possible to
Note: See TracChangeset for help on using the changeset viewer.