Please read the taxonomy draft. There are multiple meanings of the word
transparent. The "definition" used in RFC2616 matches what you could
call "semantically transparent", and has nothing to do with knowing the
IP or port of the origin server.
To anwer your question, no a semantically transparent proxy probably
must be capable to forward any kind of request of the major HTTP version
being supported by the proxy. It may do so using either proxying or
tunneling.
Fully semantically transparent proxies are most likely outside the
responsibility of WREC as caching probably is not possible in a fully
semantically transparent proxy. You can however see "semantically
transparent" as a scale of level of semantic transparency. A caching
proxy may be conditionally semantically transparent, and so may a proxy
not forwarding other than a known set of methods.
-- Henrik NordstromBertold Kolics wrote:
> My question is: can we call a proxy transparent if it is unable to handle > a request because it does not implement a method present in the request > header? > > IMO, the transparent proxy has everything it has to know about a request: > the port and IP address of the origin server. Nothing else is needed. > > Bertold
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST