How to inject a custom HTTP/HTTPS header into traffic with CFS 4.0 (184.108.40.206 & Above)
03/26/2020 116 9936
This article guides through the process of enabling HTTP/HTTPS header injection using Content Filtering Service (CFS) 4.0.
Common use headers are pre-configured in the appliance. As of 220.127.116.11, the following common use headers are included:
Google G Suite Restrict- Creates restriction of Google domains a user can access. i.e. users can only access company Google accounts
YouTube Strict Mode- Restricts users to access YouTube strict mode
YouTube Moderate Mode- Restricts users to access YouTube moderate mode
These header injections are applied through the CFS 4.0 engine and can be applied on a per-policy basis. I.e. students can be applied YouTube strict mode, while teachers can be applied YouTube moderate mode.
3 items are needed to configure:
domain for the header to be applied on
value for the header
NOTE: For HTTPS sessions, DPI-SSL is required to be able to inject information into the header.
Navigate to the Manage tab.
Access the Objects | Content Filter Objects page.
Click on the CFS Profile Objects button.
Click the configure icon next to the profile you wish to add a custom header on.
Check Enable Custom Header Insertion.
Click Add. The Add Custom Header Entry pop-up displays
Fill-in the Domain field or select one of the pre-filled options.
If applicable, fill-in the Key and Value fields based on your needs.
Click Save to save your changes. The policy is now in effect for the modified CFS profile object.