Content Matching
- Last Updated: December 11, 2024
- 2 minute read
- LoadMaster
- LoadMaster LTSF
- Documentation
When the Rule Type selected is Content Matching the following describes the options available.
Rule Name
The name of the rule.
Match Type:
-
Regular Expression: compares the header to the rule
-
Prefix: compares the prefix of the header according to the rule
-
Postfix: compares the postfix of the header according to the rule
Header Field
The header field name must be matched. If no header field name is set, the default is to match the string within the URL.
Rules can be matched based on the Source IP of the client by entering src-ip within the Header Field text box. The header field is populated by the source IP of the client.
Similarly, rules can also be matched based on the HTTP Method used, for example GET, POST or HEAD. The methods that are to be matched should be written in uppercase.
The body of a request can also be matched by typing body in the Header Field text box.
Match String
Input the pattern that is to be matched. Both Regular Expressions and PCRE are supported. The maximum number of characters allowed is 250.
For further information on Regular Expressions and PCRE, please refer to the Content Rules Feature Description.
Negation
Invert the sense of the match.
Ignore Case
Ignore case when comparing strings.
Include Host in URL
Prepend the hostname to request URL before performing the match.
Include Query in URL
Append the query string to the URL before performing a match.
Fail On Match
If this rule is matched, then always fail to connect.
Perform If Flag Set
Only try to execute this rule if the specified flag is set.
Perform If Flag is NOT Set
Only try to execute this rule if the specified flag is not set.
Set Flag If Matched
If the rule is successfully matched, set the specified flag.
Using the Perform If Flag Set and Set Flag If Matched options, it is possible to make rules dependent on each other, that is, only execute a particular rule if another rule has been successfully matched. For more detailed instructions on ‘chaining’ rules, please refer to the Content Rules Feature Description.