Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Configuration Files > filter.config
Filtering rules stored in filter.config allow you to:
Filtering rules should be defined in Content Gateway Manager on the Configure > Security > Access Control > Filtering tab. See Creating filtering rules.
Note 
Filtering rules for NTLM and LDAP are defined on the Access Control > Authentication Realms tab and stored in the auth.config file.
Important 
After you modify the file, run content_line -x from the Content Gateway bin directory (/opt/WCG/bin) to apply the changes. When you apply the changes to a node in a cluster, Content Gateway applies the changes to all nodes in the cluster.
Each line in filter.config is a filtering rule. Content Gateway applies the rules in the order listed, starting at the top of the file. If no rule matches, the request is allowed to proceed.
primary_destination=value secondary_specifier=value action=value
Note 
*
*
*
FTP (for FTP over HTTP only)
*
allow - to allow particular URL requests to bypass authentication. The proxy caches and serves the requested content.
*
deny - to deny requests for HTTP or FTP objects from specific destinations. When a request is denied, the client receives an access denied message.
*
radius - not supported.
add_hdr="header_name:header_value"
The following example configures Content Gateway to disallow puts to the origin server www.server2.com:
dest_host=notthatsite.com action=deny

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
Configuration Files > filter.config