SonicOS 7.0 Objects
- SonicOS 7.0
- Match Objects
- Zones
- How Zones Work
- Default Zones
- Security Types
- Allow Interface Trust
- Effect of Wireless Controller Modes
- Zones Overview
- The Zones Page
- Adding a New Zone
- Adding a New Zone in Policy Mode
- Adding a New Zone in Classic Mode
- Configuring a Zone for Guest Access
- Configuring a Zone for Open Authentication and Social Login
- Configuring the WLAN Zone
- Configuring the RADIUS Server
- Configuring DPI-SSL Granular Control per Zone
- Enabling Automatic Redirection to the User-Policy Page
- Cloning a Zone
- Editing a Zone
- Deleting Custom Zones
- Addresses
- Addresses Page
- About UUIDs for Address Objects and Groups
- Working with Dynamic Address Objects
- Services
- URI Lists
- Schedules
- Dynamic Group
- Email Addresses
- Match Objects
- Countries
- Applications
- Web Categories
- Websites
- Match Patterns
- Custom Match
- Profile Objects
- Endpoint Security
- Bandwidth
- QoS Marking
- Content Filter
- DHCP Option
- Block Page
- Anti-Spyware
- Gateway Anti-Virus
- Log and Alerts
- Intrusion Prevention
- AWS
- Action Profiles
- Security Action Profile
- DoS Action Profile
- Action Objects
- App Rule Actions
- Content Filter Actions
- Object Viewer
- SonicWall Support
Custom Header Screen
From SonicOS 6.5.1 and later, 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.
Before configuring the Custom Header, make sure that:
- 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
- Navigate to OBJECT | Profile Objects > Content Filter.
- Click the Add icon.
- Click Custom Header tab to display the Custom Header Insertion options.
-
Enable Custom Header Insertion option.
-
Click Add icon to configure the Domain, Key, and Value for the custom header entry.
Domain is used to check if 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.
Make sure that the Domain follows the conditions listed below:
- 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].
- Click Save.
Was This Article Helpful?
Help us to improve our support portal