KB Article | Forcepoint Support

Notes & Warnings

Important Never modify the original block files in the ...\BlockPages\en\Default directory. Copy these files to the ...\BlockPages\en\Custom directory first. Afterwards, only modify the copied files in the Custom directory.

Note Remote Filtering Server has 32 KB limit per image item. If using Remote Filtering, you should limit the image file size to 32 KB or less.
 

Problem Description

How do I modify the block page content for a custom block page?

Resolution

Important Before getting started, read the information below:

  1. For Content Gateway, creating or editing the HTML for a block page is the same as Windows server, however uploading the custom page is different depending on the version and type of Content Gateway.
  2. Restarts of the Filtering Service and potentially Network Agent will be necessary to test changes to the block page, which will impact production. To avoid affecting end users:
    • Move users to a secondary existing environment for filtering.
    • Install a secondary environment for testing, complete with Filtering and Network Agent and ensure only the test user account is being filtered by this secondary setup while creating and testing the block page.
    • Wait until a change management window before attempting to edit the block page.
    • In all scenarios: filtering service on the production environment will need to be restarted to implement the finished custom block page.
Note If you are running Forcepoint software in stand-alone mode (not integrated with a third-party product or device), it is a good idea to also restart the Websense Network Agent service.
  1. Forcepoint Technical Support policies prevent technicians from assisting customers in creating or modifying custom block pages. This includes and is not limited to:
    • font creation
    • page style
    • spacing
    • html editing
However, when a URL is blocked, Technical Support can assist in implementing a custom block page to display properly after it has been configured. 
  1. Block pages are sent to end users by a module inside Filtering Service. If you create custom block pages, you will need to copy the customized files to each Filtering Service instance that should use them.

Note When Filtering Service runs on a Windows server, updating block page files is as simple as copying the files to the "Custom" directory and restarting Filtering Service.


Two options are available to display customized block page content:

  • Customize the predefined block pages.
  • Create custom HTML files, and then configure Filtering Service to pull in block message content from those files.
 
For versions 7.5 to 8.2:
  1. Log onto the Appliance Manager,
  2. Navigate to Administration > Toolbox > Web Security Block Pages.
  3. Select Custom block page.
  4. Download the original block page files by highlighting the file and then click Download File(s).
  5. Upload the customized files.
  6. When Apply Changes is clicked, Filtering Service will restart.

For versions 8.3 to 8.5:
Note As of version 8.3, Appliance Manager was replaced with Forcepoint Security Appliance Manager (FSAM or CM). This GUI currently does not have functionality to upload Block Page information. Instead, Curl commands are used as outlined in the link above.
 
For Software Content Gateway (all versions):
  1. The paths for where the files are kept are as follows:
    • /opt/Websense/BlockPages/en/Default
    • /opt/Websense/BlockPages/en/Custom
  2. The instructions for block page create creation are the same as the versions above.
  3. Uploading the block page information can be done via FTP, WinSCP or any other SSH file transfer method allowed in the deployment.
  4. Filtering Service can be restarted using the /opt/Websense/WebsenseDaemonControl tool

Article Feedback



Thank you for the feedback and comments.