First off, I like the distinction between transparent
(automatic) discovery and transparent use. WPAD supports auto-discovery
of proxies to assist users configuring their browsers. One distinction
with transparent redirection is that end to end semantics are modified.
If a connection is re-routed to a proxy, the client is not talking to
whom it thinks. If a browser initiates a connection with a proxy (via
WPAD, IT department configuration, or end user configuration), then they
are explicitly using an application level proxy. The "hijack" issue
caused a lot of concern earlier on this list; some people are very
bothered by violation of end-to-end semantics. It is good to have
another choice. How to work this into the discussion? Maybe
- discuss discovery separate from access
- introduce traffic interception/redirection
- define "transparent proxy cache" in terms of interception
?
-- jad --
John Dilley <jad@hpl.hp.com>
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST