W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1999

Re: http proxy & tunnel differences ??

From: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
Date: Tue, 26 Oct 1999 08:39:49 -0700
To: Scott Lawrence <lawrence@agranat.com>
cc: Vinit Kumar <kumar_vinit@hotmail.com>, http-wg@hplb.hpl.hp.com
Message-ID: <199910260839.aa19287@gremlin-relay.ics.uci.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/618
>> A proxy works by taking a request from a client and
>> connecting to the origin
>> server indicated in the request.  Here the client is configured to go
>> through the proxy.
>
>Actually, the client may or may not know about the proxy.

The client always knows about the proxy -- that is what distinguishes
a proxy from a gateway.  A "reverse proxy" is a gateway.

>> How does a http tunnel work. Is the initial connection similar ?
>> Does a client (browser) need to configured differently when
>> it goes through
>> a tunnel or is it same as the configuration required when it
>> goes through
>> the proxy ? Are there to separate tcp connections for each
>> request even in a
>> tunnel ?

Some tunnels are activated by a proxy request, some are simply
port forwarding TCP firewalls (either on the client side or the
server side, or both), and others are gateways to other servers.
The important thing from HTTP's perspective is that once an
intermediary becomes a tunnel, it is no longer conscious of the
HTTP communication -- only of bytes being relayed from one connection
to another.

....Roy
Received on Tuesday, 26 October 1999 08:44:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:06 UTC