Bug 961377 - Apache httpd returns 500 status code instead of custom status code when using mod_proxy
Summary: Apache httpd returns 500 status code instead of custom status code when using...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Apache Server (httpd) and Connectors
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER8
: EAP 6.1.0
Assignee: Permaine Cheung
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On: JBEWS-4
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-09 13:49 UTC by Permaine Cheung
Modified: 2013-07-23 18:46 UTC (History)
12 users (show)

Fixed In Version:
Clone Of: JBEWS-4
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEWS-4 0 Major Closed Apache httpd returns 500 status code instead of custom status code when using mod_proxy 2013-10-07 12:03:58 UTC

Comment 2 Fernando Nasser 2013-05-09 14:03:08 UTC
This can break RESTful apps, we should include it.

Comment 3 Fernando Nasser 2013-05-09 14:59:45 UTC
Needed to avoid an async EAP errata to make it match EWS 2.0.1

Comment 4 Permaine Cheung 2013-05-09 16:12:14 UTC
The .18 builds are incorporated into jboss-ews-2.0.1-3.ep6.el[56], which are incorporated in the latest jboss-eap6-httpd-natives-6.1.0-5.ep6.el6 build and jboss-eap6-natives-compose-6.1.0-15.CR1.ep6.el6.

Comment 5 Permaine Cheung 2013-05-09 17:56:05 UTC
Will be in ER8.

Comment 6 Jan Stefl 2013-05-14 11:01:54 UTC
Verified in EAP 6.1.0.ER8 - OK


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