Search Engine: Elastic

Article ID: 117101, created on Sep 4, 2013, last review on May 11, 2014

  • Applies to:
  • Operations Automation 5.5


Provider or reseller used 'Custom Error Documents' feature to assign custom error document to the HTTP Error 404 for branded Control Panel website.

However, when accessing non-existing webpage in scope of Provider/reseller branded CP the original, non-customized, error appears in browser, see the example below:

HTTP Status 404 - /pem/docroot/some-non-existing-document.html
type Status report
message /pem/docroot/some-non-existing-document.html
description The requested resource (/pem/docroot/some-non-existing-document.html) is not available.
Apache Tomcat/5.5.36

Example of used URL: https://cp.provider.tld/some-non-existing-document.html, where cp.provider.tld is the hostname of the branded Control Panel website.


The 'Custom Error Documents' feature does not work for brands due to specifics of the branded websites' configuration.


The problem is going to be fixed in the future updates to POA in scope of the request POA-80290.

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF