PageViews: 802 hits / 111 nets |
The DeleGate server for this purpose is invoked as a SOCKS server. After the negotiation in the SOCKS protocol is completed, the server process becomes an application level proxy which interprets the application protocol conveyed on the TCP connection between a client and a server, doing cache and logging and so on in the way and the format which are specific to each application protocol.
phase-1) DeleGate acts as a SOCKS server, doing authentication of the client and negotiation about the destination server.
client ================> DeleGate SOCKS / TCP authentication connection
phase-2) DeleGate acts as an application-level proxy, relaying between the client and the server, or relaying data from the cache.
+-----> another-proxy | client ================> DeleGate --+------------> server HTTP cache FTP log NNTP filtering SMTP routing POP mount ... authentication ...
The protocol on a TCP connection is guessed by the pattern of
the first request from the client-side or the first response from the
server-side sent on the connection. (*2)
The connection to the server may not be established when the application
protocol is HTTP and there is a fresh cache for the request.
To configure a DeleGate to act like this, add the names of application
protocols to be interpreted to the
SOCKSTAP
parameter as follows.
delegated -P1080 SERVER=socks CACHE=do SOCKSTAP=http,ftp
The easiest way of the configuration is making arbitrary protocols to
be interpreted as follows.
delegated -P1080 SERVER=socks CACHE=do SOCKSTAP=all
(*2) DeleGate has another kind of "transparent application-level proxy over a circuit-level proxy" which has been called as "Generalist" historically. Since it has the information of the application protocol indicated in it, it is easier to know in which application protocol the communication should be interpreted.
Example: Socks-DeleGate which do caching for HTTP and FTP
Example: Socks-DeleGate which do caching for HTTP with an upstream proxy
See
http://www.delegate.org/delegate/sockstap/>
for more details.
SOCKSTAP parameter* == SOCKSTAP=ProtoList[:[dstHostList][:[srcHostList][:params]]]
-- default: none
If specified with a SOCKS server, the data stream relayed over the SOCKS is
interpreted in each application protocol.
For example, with SOCKSTAP=http, the delegated act as a server
of SERVER=http when the relayed protocol is detected to be the HTTP protocol.