reprocess-root-jct-404s

reprocess-root-jct-404s

reprocess-root-jct-404s = {yes|no}

Description

Used to reprocess requests for root junction resources that result in an HTTP 404 error.
The dont-reprocess-jct-404s entry (also in the [junction] stanza) can be set to yes to avoid multiple attempts to prepend a junction point to the beginning of the URL string when reprocessing requests that have resulted in an HTTP 404 status code.
WebSEAL determines whether the request is already known to be for a non-local junction.However, WebSEAL fails to add a junction point when requests have been made for a root junction created at "/". To modify this behavior and cause requests for root junction resources that result in an HTTP 404 error to be reprocessed, we can use this reprocess-root-jct-404s stanza entry.
Options

yes Cause requests for root junction resources that result in an HTTP 404 error to be reprocessed regardless of the setting of the dont-reprocess-jct-404s entry (also in the [junction] stanza).
no The value for the dont-reprocess-jct-404s entry (also in the [junction] stanza) will determine Whether root junction requests that result in an HTTP 404 error are reprocessed. That is, if the value for dont-reprocess-jct-404s is no then the HTTP 404 errors will still be reprocessed.

Usage: Optional
Default value no
Example: reprocess-root-jct-404s = yes
Parent topic: [junction] stanza

yes	Cause requests for root junction resources that result in an HTTP 404 error to be reprocessed regardless of the setting of the dont-reprocess-jct-404s entry (also in the [junction] stanza).
no	The value for the dont-reprocess-jct-404s entry (also in the [junction] stanza) will determine Whether root junction requests that result in an HTTP 404 error are reprocessed. That is, if the value for dont-reprocess-jct-404s is no then the HTTP 404 errors will still be reprocessed.