When server communication fails

Technical Library | Support

Introducing Remote Filtering > When server communication fails

When server communication fails

Deploying the Remote Filter Module | Web Filter & Security | v8.0.x, v8.1.x

Related topics:

Deployment information

How remote filtering works

Policy enforcement occurs when Remote Filtering Client, outside the network, successfully communicates with Remote Filtering Server in the network DMZ. However, there may be times when that communication is unsuccessful.

You can configure what action Remote Filtering Client takes if it cannot contact Remote Filtering Server.

By default, Remote Filtering Client permits all HTTP, HTTPS, and FTP requests (fails open).

Remote Filtering Client continues attempting to contact Remote Filtering Server. When communication is established, the appropriate filtering policy is enforced.

When Remote Filtering Client is configured to block all requests when it cannot communicate with Remote Filtering Server (fail closed), users are not able to access the Internet until a successful connection to Remote Filtering Server has been established.

In cases where users must pay for Internet access, such as in hotels or coffee shops, Remote Filtering Client detects and permits connection to the payment portal. As soon as Internet access has been paid for, Remote Filtering Client starts managing requests.

In earlier versions, users were given open Internet access for a limited timeout period, while Remote Filtering Client attempted to make a connection.

When Remote Filtering Server cannot communicate with Filtering Service, the server stops communicating with Remote Filtering Client. When this occurs, the client fails open or closed, as configured.

To change whether Remote Filtering Client blocks or permits all requests when it cannot communicate with Remote Filtering Server, see Global remote filtering settings.

Introducing Remote Filtering > When server communication fails