Transparent Proxy over SOCKS by DeleGate
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
...
|
| PageViews: 8,365 hits / 469 nets |
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.
% delegated -P1080 SERVER=socks CACHE=do SOCKSTAP=http,ftp
% delegated -P1080 SERVER=socks SOCKSTAP="http:::CACHE=do PROXY=pxserv:8080"