We noticed an unexpected behavior of the Apache Webserver when configured to relay requests as a proxy to another server regarding the handling of the error pages to be shown. Until now, the Proxy tried to fetch the configured error pages from the backend server that usually reported a "404 not found" for the requested path (unless it was by chance also a managed server from Ops One) instead of returning the needed error page.
The configuration was now changed to avoid this and instead use and deliver the locally present error page documents if needed.
