cache-host-header
Use the cache-host-header stanza entry to control whether WebSEAL caches the host and protocol of the original request.
cache-host-header = {yes|no}Description
By default, when caching an original request, WebSEAL only caches the URL. That is, WebSEAL does not cache the host and protocol of the original request. In this case, when returning a redirect to the original URL, WebSEAL simply redirects to the current host. This causes problems if a request for a protected resource on one virtual host, hostA, results in an authentication operation being processed on a different virtual host, hostB. In this case, the client is incorrectly redirected to hostB rather than hostA. This behavior can be corrected by enabling this stanza entry so that WebSEAL can cache the host and protocol of the original request to be used for redirection.
Options
yes WebSEAL caches the host and protocol of the original request in addition to the URL. In this case: Limitations associated with this caching behavior:
- Both the host and protocol are cached and used in redirects. They cannot be separately managed.
- The protocol is not cached if the host header is not present.
- Requests will only be recovered from the cache if the protocol, the host and the URL all match the original request.
- The contents of the existing URL macro will not include the protocol and host. No new macros have been added to represent these elements.
- It is not possible to specify a protocol and host when a switch user administrator specifies a URL.
no WebSEAL only caches the URL associated with the original request and redirects to the current host.
Usage: Optional
Default: no
Example:
cache-host-header = yes