New Category Release: SafeSearch via CONNECT header [NEW]
The new category name ‘SafeSearch via CONNECT header [NEW]’ replaces the old category name, ‘Enable Google SafeSearch [NEW]’.
Content Modification rule to enforce SafeSearch on a limited number of Search engines via a CONNECT header rewrite, for example, google.com -> forcesafesearch.google.com. Google, Bing, and Pixabay services are all supported by this content modification.
This content modification does not require any HTTPS D&I policy to be in place, but it is very limited in its coverage. Because of this, we recommend Force SafeSearch Content Modification to be used as well as this covers more services but works differently in the way it enables SafeSearch, and will require a valid HTTPS D&I policy in place.
For customers who were previously using the “Enable Google SafeSearch [NEW]” category, they do not need to anything as this is the exact same category, just named differently as it covers more than just Google.
More information can be found on this by Google here, or in our knowledge base articles:
Activating safe search
Make search engine browsing safer