We are not able to capture the error code 404/500 when we stopped the websphere installed application. Seems some how the IHS is not able to capture the error code and return the error document correctly. Anyone managed to configured this ?
This topic has been locked.
1 reply Latest Post - 2012-12-10T15:39:09Z by Sunit
Pinned topic IHS ErrorDocument 404 500
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-10T15:39:09Z at 2012-12-10T15:39:09Z by Sunit
Sunit 100000DWFV182 PostsACCEPTED ANSWER
Re: IHS ErrorDocument 404 5002012-12-10T15:39:09Z in response to NeoWongeWhen the application is stopped WAS generates the 404 code and IHS will simply pass it back. You have to handle 404 within the application server.
If the content was being served by IHS and NOT by WAS then a 404 will trigger the ErrorDocument directive.
Error code 500 is a catch all and if you want to trigger that then you have to stop the application server not just the application within the server.