You can use Application Control features with the internal HTTP Proxy service and external proxies. Depending on what type of proxy is used, Application Control might be limited or require additional configuration.
|Sub-application Detection||No||Yes (with an access rule for HTTPS)||Yes||Yes|
|SSL Interception||Yes (via HTTP Proxy Service)||Yes (with an access rule for HTTPS)||Yes||Yes|
||Yes (via HTTP Proxy Service)||Yes (via HTTP Proxy Service)||Yes||Yes|
|URL Filter||Yes (via HTTP Proxy Service or Firewall Service)||Yes (via HTTP Proxy Service or Firewall Service)||Yes||Yes|
|Application Based Provider Selection||No||No||-||-|
|Google Accounts Filtering||No||No||No||No|
|File Content Filtering||No||No||No||No|
|User Agent Filtering||Yes||Yes||Yes||Yes|
HTTP Proxy Service (Forward Proxy)
When the client is configured to use the HTTP Proxy service for both HTTP and HTTPS, Application Control can be used to detect applications for HTTP connections. Clients contact the HTTP Proxy service directly on port 3128 or 8080 for both HTTP and HTTPS connections. SSL Interception is handled in the HTTP Proxy service
HTTP Proxy Service (Transparent Proxy)
When the HTTP Proxy service on the F-Series Firewall is configured as a transparent proxy, only HTTP traffic is sent to the HTTP Proxy. To pass HTTPS traffic through Application Control and SSL Interception, you must configure an explicit access rule.
When clients use an external proxy for both HTTP and HTTPS traffic, there are no restrictions. Application Control can inspect all traffic coming from or going to the proxy.
Separate HTTP and HTTPS (SSL) Proxies
No limitations apply when clients are configured to use separate external HTTP and HTTPS proxies. Application Control and SSL Interception can inspect all traffic coming from and going to the HTTP and HTTPS proxies.