Configuring SOCKS firewall integration

Security > Configuring SOCKS firewall integration

Configuring SOCKS firewall integration

Help | Content Gateway | Version 7.7.3

Related topics:

Configuring SOCKS servers

Setting SOCKS proxy options

Setting SOCKS server bypass

SOCKS is commonly used as a network firewall, allowing hosts behind a SOCKS server to gain full access to the Internet while preventing unauthorized access from the Internet to hosts inside the firewall.

When Content Gateway receives a request for content that is not in the cache, it must request the content from the origin server. In a SOCKS configuration, instead of accessing the origin server directly, the proxy goes through a SOCKS server. The SOCKS server authorizes communication between the proxy and the origin server and relays the data to the origin server. The origin server then sends the content back to the proxy through the SOCKS server. If caching is enabled, Content Gateway caches the content before sending it to the client.

Content Gateway can act as a SOCKS client, where it receives and serves HTTP or FTP requests as usual.

Content Gateway can act as a SOCKS proxy, relaying requests to and from the SOCKS server (usually on port 1080).

When Content Gateway is installed on a V-Series appliance it can act as a SOCKS server, providing all of the services of a SOCKS server. (When Content Gateway is not installed on an appliance, it cannot act as a SOCKS server.)

Note: Content Gateway does not perform user authentication with the client. However, the proxy can perform user name and password authentication with a SOCKS server running SOCKS version 5.

Security > Configuring SOCKS firewall integration

Support

Search

Article Rating:

Related Articles

Quick Links

Service Requests

How are we doing?