waf web-cache-exception
Use this command to configure FortiWeb to cache responses from your servers.
Use web-cache-exception
to cache all URLs except for a few. To cache only a few URLs, see waf web-cache-policy.
To apply this policy, include it in an inline protection profile. For details, see waf web-protection-profile inline-protection.
To use this command, your administrator account’s access control profile must have either w
or rw
permission to the wafgrp
area. For details, see Permissions.
Syntax
config waf web-cache-exception
edit "<web-cache-exception_rule_name>"
config exception-list
edit <entry_index>
set host-status {enable | disable}
set url-type {plain | regular}
set url-patten "<url-pattern_str>"
set cookie-name "<cookie-name_str>"
end
next
end
Variable | Description | Default |
Enter the name of a new or existing rule. The maximum length is 63 characters. To display the list of existing policies, enter:
|
No default. | |
Enter the index number of the individual entry in the table. The valid range is 1–9,999,999,999,999,999,999. |
No default. | |
Specify |
disable | |
Specify which protected host names entry (either a web host name or IP address) that the Maximum length is 256 characters. This option is available only if the value of host-status {enable | disable} is |
No default. | |
Specify the type of value that is used for url-patten "<url-pattern_str>":
|
plain |
|
If the value of url-type {plain | regular} is If the value of Do not include the domain name, such as Maximum length is 256 characters. Tip: Generally, URLs that require autolearning adapters do not work well with caching either. Do not cache dynamic URLs that contain variables such as user names (e.g. older versions of Microsoft OWA) or volatile data such as parameters. Because FortiWeb is unlikely to receive identical subsequent requests for them, dynamic URLs can rapidly consume cache without improving performance. |
No default. | |
Specify the name of the cookie, such as Maximum length is 127 characters. Tip: Content that is unique to a user, such as personalized pages that appear after a person has logged in, usually should not be cached. If the web application’s authentication is cookie-based, configure this setting with the name of the authentication cookie. Otherwise, if it is parameter-based, configure the exception with a URL pattern that matches the authentication ID parameter. |
No default. |