Hosted Web Security Custom URL patterns explained

July 18, 2011 • Administrator       
Synopsis

This article describes the new Custom URL URL pattern matching methodology as it differs from CensorNet Professional.

Article

When entering Custom URL entries into the Hosted Web Security web console, you will need to obey the following rules:

  • You cannot enter a protocol header, e.g. http:// or https://. This is not required.
  • You cannot enter an asterisk (*), this is implied.
  • You cannot start the URL with a period (.), this is implied.

Entering the following URL into the Custom URL module:

whatever.com

Automatically implies *.whatever.com or just whatever.com. 

To allow or block a specific subdomain you should enter it in full, e.g.

http://subdomain.domain.com

becomes

subdomain.domain.com

To allow all sub-domains for domain.com, simply add:

domain.com

 

Related articles


Last modified on Mon, July 18, 2011 « Back