• SonicOS 7 Profile Objects
• Endpoint Security
• Bandwidth
• Quality of Service (QoS) Marking
  • Classification
  • Marking
  • Conditioning
    • Site to Site VPN over QoS Capable Networks
    • Site to Site VPN over Public Networks
  • 802.1p and DSCP QoS
    • Enabling 802.1p
    • DSCP Marking
      • DSCP Marking and Mixed VPN Traffic
      • Configure for 802.1p CoS 4 – Controlled load
      • QoS Mapping
      • Managing QoS Marking
  • Glossary
• Content Filter
  • Managing CFS Profile Objects
    • About CFS Profile Objects
    • About UUIDs for CFS Profile Objects
    • Configuring CFS Profile Objects
      • Advanced Screen
      • Consent Screen
      • Custom Header Screen
    • Editing a CFS Profile Object
    • Deleting CFS Profile Objects
  • Applying Content Filter Objects
• DHCP Option
  • Configuring DHCP Option Objects
    • RFC-Defined DHCPV4 Option Numbers
    • RFC-Defined DHCPV6 Option Numbers
  • Editing DHCP Option Objects
  • Deleting DHCP Option Objects
• AWS
  • AWS Objects
    • About Address Object Mapping with AWS
    • Viewing Instance Properties in SonicOS
    • Creating a New Address Object Mapping
    • Enable Mapping
    • Configuring Synchronization
    • Configuring Regions to Monitor
    • Verifying AWS Address Objects and Groups
• SonicWall Support
  • About This Document

Custom Header Screen

Starting in SonicOS 6.5.1, you can configure the firewall as a web proxy server to control web service, such as preventing users from signing in to some web services using any accounts other than the accounts provided, or restricting the content viewable by users. The web proxy server adds a custom header to all traffic matched by the Content Filtering policy, and the header identifies the domains whose users can access the web services or the content that users can access. Encrypted HTTPS traffic is supported if DPI-SSL is enabled.

This screen is one of the four screens in Add CFS Profile Object dialog. To open the dialog, navigate Object > Profile Objects > Content Filterpage and click the Add button at the top of the page. Then click Custom Header Screen tab.

This feature requires the following:

• Content Filter Service is enabled.
• Custom header insertion is enabled in the matched CFS profile object.
• DPI-SSL is enabled for custom header insertion with encrypted HTTPS requests.

To configure a CFS custom header and enable custom header insertion

1. Navigate to Object > Profile Objects > Content Filtertab.
2. Click Add at the top of the page.
3. In the Add/Edit CFS Profile Object dialog, click Custom Header tab to display the Custom Header Insertion options.
4. Enable the Enable Custom Header Insertion option.

5. Click Add icon to configure the Domain, Key, and Value for the custom header entry.

   

   Domain is used to check whether the host in an HTTP request is matched to an entry during packet handling. Key and Value are used to generate the right header for the entry when building runtime data for custom header insertion.

   The Domain can contain:

   • Each domain name can contain up to 16 tokens separated by periods (.).
   • The domain name cannot start or end with separators.
   • Each token can contain up to 128 printable ASCII characters.
   • Tokens in a domain name can only contain the characters: 0-9a-zA-z$-_+!’(),.
   • IPv4/IPv6 addresses can be defined as a domain name, e.g. “[2001:2002:2003::2005:2006]”.
6. Click Save.