Request Filter

Return to previous page

  • 4/7/2015
  • 1644 Views

Comments

1644 Views

Request Filter

Last updated 6 years ago

Comments

Common

(Enter the content of this article below)

Advanced

 
Each rule element in the request filter defines a simple matching expression and the action to take if a match is found. You can define as many rules
as needed. This provides a flexible "or" operation where any one rule can cause the request to be blocked.

Request filter rules are persisted in the DotNetNuke.config file located in the installation root. In the case of catastrophic error (e.g. causing all site requests to redirect to another site), this file may be manually edited to remove the offending rule.

Rule Attributes:

  • servervar: This is the name of a Server variable from the Request.ServerVar hash table. See: http://www.w3schools.com/asp/coll_servervariables.asp
  • operator : Defines the operation that determines whether an actual match exists. Valid values: Regex, Equal, NotEqual
    • Regex :  Uses the regular expression specified in the value attribute to determine a match.  This match is performed in a case-insensitive manner. Regex captured groups may NOT currently be used to specify a location URI (see location attribute below).
    • Equal:  Performs a search of the value list to determine if the value of the specified server variable is in the value list.
    • NotEqual:  Performs a search of the value list to determine if the value of the specified server variable does not exist in the value list.
  • value : Defines the value of the servervar that triggers the rule. For a regex rule, the value should be a regular expression that used as a matching expression.
    If this is not a regex operation, then value can be a semicolon delimited list of values. For example it could include a list of IP addresses that should
    be blocked.
  • action : Defines the action to take if a match occurs. Valid values: NotFound, Redirect, PermanentRedirect.
    • NotFound: Returns a 404 status code and stops all further response processing.
    • Redirect : Performs a standard redirect to the url specified in the location attribute.
    • PermanentRedirect: Performs a permanent redirect (status code 301) to the url specified in the location attribute.
  • location : The url where the request will be redirected. This can be left blank for the 'NotFound' action.
Contents
No sections defined

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out