Bug 968960 - "ProxyErrorOverride On" does not work if used with mod_proxy_ajp module
Summary: "ProxyErrorOverride On" does not work if used with mod_proxy_ajp module
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Web Server 1
Classification: JBoss
Component: httpd22
Version: EWS 1.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Weinan Li
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 11:26 UTC by Dasharath Masirkar
Modified: 2013-05-30 13:56 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-30 13:56:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 694939 0 medium CLOSED mod_proxy_ajp does not honor "ProxyErrorOverride" 2021-02-22 00:41:40 UTC

Description Dasharath Masirkar 2013-05-30 11:26:59 UTC
Description of problem:

"ProxyErrorOverride On" does not work if used with mod_proxy_ajp module.

[ Config Snippet ]

ProxyPass /app/  ajp://127.0.0.1:8009/app/
ProxyErrorOverride On
ErrorDocument 404  /error/404.html

When I access a 404 URL in the /app context, which is proxied with AJP, I get a 404 page from JBoss EAP. Accessing 404 URLs via non-proxied content works as intended, as defined in "ErrorDocument".

Version-Release number of selected component (if applicable):

JBoss EWS 1.0.2 httpd-2.2.17


How reproducible:

Everytime.


Steps to Reproduce:

1. Define "ErrorDocument"
2. Enable "ProxyErrorOverride"
3. Access 404 URL via definied "ProxyPass" context
  

Actual results:

404 error from backend (proxied) server


Expected results:

404 error as defined in "ErrorDocument" via Apache


Additional info:
There is existing [Bug 694939](https://bugzilla.redhat.com/show_bug.cgi?id=694939) with Apache httpd provided with RHEL6, which got fixed in Apache httpd rpm provided with RHEL 6.2

Comment 1 Weinan Li 2013-05-30 13:56:48 UTC
We just provide CVE fixes with high priorities for EWS 1.x as it's enters the maintenance lifecycle.


Note You need to log in before you can comment on or make changes to this bug.