Configuration of server-side caching
We can modify settings in the [server] stanza of the WebSEAL configuration file to specify limits to the size of the requests that WebSEAL reads and caches.
Usage notes for server-side request caching:
- Server-side caching helps protect WebSEAL from denial of service attack types that could cause WebSEAL to cache more data than it can handle.
- Server-side request caching does not function correctly if the user session time out value expires during the login process. In this situation, the cache entry is lost.
- Server-side request caching can cause limitations with the browser's ability to manipulate the resource. The browser is unaware that WebSEAL has rebuilt the HTTP redirect. Therefore the browser's reload/refresh function and caching ability can be hindered.
The following sections describe the settings that we can modify:
- Modification of request-body-max-read
The request-body-max-read stanza entry specifies the maximum number of bytes of content to read from the body of POST requests.- Modification of request-max-cache
Parent topic: Server-side request caching