How can I change the default HTML formatting for the built-in exceptions?

Products

• ProxySG Software - SGOS

Issue/Introduction

How can I customize the built-in exceptions page that the ProxySG appliance returns?

Resolution

Built-in exceptions are a set of pre-defined exceptions stored on the ProxySG appliance. You can modify, but not delete, the text message and format of the message displayed in exceptions.

For more details on built-in exceptions, refer to the Visual Policy Manager Reference for your version of SGOS. The procedure in this article is based on 6.2.x.

To change the default the text message and format of the message displayed in exceptions.:

1. Launch the ProxySG Management Console.
2. Select Configuration > Policy > Exceptions.
   
   
    
3. Beside Install Exceptions Definitions from, select Text Editor from the menu and then click Install.
   The current exceptions file opens in the appliance text editor.
4. Scroll to the top of the file.
   
    
   
   The highlighted text in the preceding figure indicates where the formatting begins. There is a corresponding --1dc239bd.58b5-- to indicate where the formatting ends. (The actual code is different on your appliance, but on the start and end tags on the same appliance are matching and should not be modified.)
    
5. You can modify anything between these two tags:
   • Write your custom formatting in HTML, for example, in a text editor such as Notepad. Then, copy it into the exceptions file to overwrite the existing format. Note that the formatting applies to all custom exceptions.
   • Scroll down in the exceptions list to locate the exception(s) whose text you wish to modify. Look for text between the <p> and </p> tags.
6. Click Install.
   
   You might see one of the following warnings:
   
   Warning: /legacy/cache_engine/persistent/Exceptions.4336: Exception name is not recognized as a built-in name, and will not be referenceable: spoof_authentication_error
   Warning: /legacy/cache_engine/persistent/Exceptions.4351: Exception name is not recognized as a built-in name, and will not be referenceable: policy_denied_JobSearch
   
   You can safely ignore these messages