Response caching is not supported on FortiWeb 400B due to limited available memory. |
Setting name | Description |
Host | Select which protected host names entry (either a web host name or IP address) that the Host: field of the HTTP request must be in to match the exception. This option is available only if Host Status is enabled. |
Host Status | Enable to require that the Host: field of the HTTP request match a protected host names entry in order to match the exception. Also configure Host. |
Type | |
URL Pattern | Depending on your selection in Type, enter either: • the literal URL, such as /index.php, that the HTTP request must contain in order to match the rule. The URL must begin with a slash ( / ). • a regular expression, such as ^/*.php, matching all and only the URLs to which the rule should apply. The pattern does not require a slash ( / ); however, it must at match URLs that begin with a slash, such as /index.cfm. Do not include the domain name, such as www.example.com, which is configured separately in the Host drop-down list. To create and test a regular expression, click the >> (test) icon. This opens the Regular Expression Validator window where you can fine-tune the expression (see “Regular expression syntax”). Tip: Generally, URLs that require autolearning adapters do not work well with caching either. Dynamic URLs that contain variables such as user names (e.g. older versions of Microsoft OWA) or volatile data such as parameters usually should not be cached. Because FortiWeb is unlikely to receive identical subsequent requests for them, dynamic URLs can rapidly consume cache without improving performance. |
Cookie Name | Type the name of the cookie, such as sessionid, as it appears in the Cookie: HTTP header. 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. |
Setting name | Description |
Host | Select which protected host names entry (either a web host name or IP address) that the Host: field of the HTTP request must be in to match the policy. This option is available only if Host Status is enabled. |
Cache Size | Type the maximum size in megabytes (MB) of RAM to allocate to caching content. Storing cached content to FortiWeb’s hard disk is not supported. Tip: For improved performance, adjust this setting until it is as small as possible yet FortiWeb can still fit most graphics and server processing-intensive pages into its cache. This allows FortiWeb to allocate more RAM to other features that also affect throughput, such as scanning for attacks. |
Maximum Cached Page Size | Type the maximum size in kilobytes (KB) of each URL that FortiWeb will cache. Objects such as high-resolution images, movies, or music that are larger than this limit will not be cached. Tip: For improved performance, adjust this setting until FortiWeb can fit most graphics and server processing-intensive pages into its cache. |
Default Cache Timeout | Type the time to live for each entry in the cache. Expired entries will be removed. A subsequent request for the URL will cause FortiWeb to forward the request to the server in order to cache the response again. Any additional requests will receive FortiWeb’s cached response until the URL’s cache timeout occurs. |
Exception | Select a list of exceptions, if any, to this list of cached URLs. |
Setting name | Description |
Host | Select which protected host names entry (either a web host name or IP address) that the Host: field of the HTTP request must be in to match the policy. This option is available only if Host Status is enabled. |
Host Status | Enable to require that the Host: field of the HTTP request match a protected host names entry in order to match the policy. Also configure Host. |
Type | |
URL Pattern | Depending on your selection in Type, enter either: • the literal URL, such as /index.php, that the HTTP request must contain in order to match the policy. The URL must begin with a slash ( / ). • a regular expression, such as ^/*.php, matching all and only the URLs to which the policy should apply. The pattern does not require a slash ( / ); however, it must at match URLs that begin with a slash, such as /index.cfm. Do not include the domain name, such as www.example.com, which is configured separately in the Host drop-down list. To create and test a regular expression, click the >> (test) icon. This opens the Regular Expression Validator window where you can fine-tune the expression (see “Regular expression syntax”). |