+3.1.5. Making Proxy Connections
+
+ The simplist form of firewall traversal is the HTTP CONNECT command.
+ The CONNECT command was implemented to allow a public web server which
+ usually resides on the boundary between the public and private networks
+ to forward HTTP requests from clients on the private network to public
+ web sites. In order to allow secure web connections to be established,
+ the CONNECT command works by authenticating the client with a
+ username/password and then establishing a tunnel to the desired host.
+
+ Many web servers support the CONNECT command and it can be configured
+ to allow outgoing connections to authenticated user to any TCP/IP
+ hostname/port combination accessible to the web server. The limitations
+ of HTTP CONNECT is that it can only be used for outgoing connections
+ for protocols that are implemented using TCP/IP. Protocols such as
+ Kerberos authentication that use UDP/IP cannot be tunneled using HTTP
+ CONNECT.
+
+ Kermit provides support for the use of HTTP CONNECT proxy services with
+ the command:
+
+ SET TCP HTTP-PROXY [/USER:username /PASSWORD:password] hostname/ip-address[:po
+rt]
+
+ When a port is not specified the default port configured on the HTTP
+ server is used. This is frequently port 443. When a hostname is
+ specified, it is resolved using the DNS available to the web server.
+