Product Documentation
Abstract
How to return Backend Server original error messages intead of having ISAM replace its own error page
as per error code and associated .html page.
Content
When WebSEAL is unable to process a request from a client, WebSEAL returns an HTML error message page to the client. The error message page explains why the request failed. The error message pages are installed when the WebSEAL instance is configured. Each error message page is a separate static HTML file. The names of the files are the hexadecimal values of the returned error codes.
If the backend returns an error code that is listed in Management Root / errors, the WebSeal will display its own error page as per error code and associated html page.
However, if we want WebSeal to return the original error code form the Backend server instead, we need to the delete the
corresponding .html so WebSeal does not replace with its own.
For example, if the Backend server returns an HTTP 400 error code, WebSeal will replace it with the content found
in 38cf0424.html. So WebSeal does not replace, in the Management Root / errors page in the LMI, locate 38cf0424.html > Export it (to keep as backup) and then delete it...
The idea is that if the error code is not listed then WebSeal will show the error that the Backend shows and not replace with its own.
Also, this behavior cannot be configured on a specific junction. Deleting the file allows to get the Backend response, but this is Webseal-wide and there's not a per-junction configuration stanza for this.
Publication Number
1
Copyright Date
03/08/2018
Original Publication Date
03 August 2018
Related Information
Was this topic helpful?
Document Information
More support for:
IBM Security Access Manager
Software version:
All Versions
Operating system(s):
Linux
Document number:
730213
Modified date:
04 September 2018
UID
ibm10730213