Topic: mod_proxy : error page handling

[rsinklair]

hi all, a question on mod_proxy :

We're using mod_proxy as a simple reverse proxy (ProxyPass & ProxyPassReverse) to reverse-proxy various back-end PHP and Mono/.NET apps.

One problem we see is that when the back-end PHP app suffers an error (e.g. a 404 or 500) , then mod_proxy ignores the nicely-formatted custom error page served up by our PHP app, and instead serves a very plain generic mod_proxy 404 or 500 error page back to the client.

Is there a way to configure mod_proxy to serve up the 500/404 error page content which is created by the back-end app ?

( We thought ProxyErrorOverride might help, but it seems to be intended for the opposite scenario, where I want to *ignore* the 404 page content from the back-end and show a mod_proxy-defined error page instead.

We're using apache 2.2 on 64-bit CentOS 6.5 ( httpd-2.2.15-31.el6.centos.x86_64 )

Config like:
...
ProxyPass /abc/ http://server4/abc/
ProxyPassReverse /abc/ http://server4/abc/

thanks
Rob
London, UK

[rsinklair]

update - we discovered we had 'ProxyOverride On' set elsewhere in our apache config , so looks like this was a self-inflicted problem !
*doh*