04-16-2021 12:40 AM
Hi,
I would like to show the custom error page configured in web.xml of alfresco web app for the 401 ,400 ,500 errors.
web.xml configuration :
<error-page> <error-code>401</error-code> <location>/errorPage.html</location> </error-page> <error-page> <error-code>500</error-code> <location>/errorPage.html</location> </error-page> <error-page>
Currently webscript errors in the admin console of alfresco thrown the exception in browser like below :
06-22-2021 06:10 AM
We were about to submit a ticket, then one of our team members was able to access via Chrome instead of Microsoft Edge. We are not sure what policies were applied to our Edge browsers, but we can finally connect.
We saw the issue during tests after our monthly patching and a second new security product was added to our linux servers in the past few weeks, so that is where we started troubleshooting. We had fully regression tested everything in April and had not changed app configurations, so we jumped to the wrong source of evironmental changes.
04-16-2021 03:26 AM
The web script framework has its own error / status template handling and does not fall back to the global servlet error page set via web.xml. See response status code templates (documentation)
06-21-2021 10:24 AM
This error recently appeared when trying to log into the Alfresco 6.1 admin page. Alfresco is still up and running and functional. I am not aware of what RHEL 7 patch or a new security product that was recently installed.
06-22-2021 05:30 AM
Hi @JMRowland
Have you raised a support ticket for this issue?
Cheers
06-22-2021 06:10 AM
We were about to submit a ticket, then one of our team members was able to access via Chrome instead of Microsoft Edge. We are not sure what policies were applied to our Edge browsers, but we can finally connect.
We saw the issue during tests after our monthly patching and a second new security product was added to our linux servers in the past few weeks, so that is where we started troubleshooting. We had fully regression tested everything in April and had not changed app configurations, so we jumped to the wrong source of evironmental changes.
Explore our Alfresco products with the links below. Use labels to filter content by product module.