RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: It takes X seconds to respond to a request (where X = ProxyTimeout) when the response code is a 404 (or maybe any 4xx).


Version-Release number of selected component (if applicable): httpd-2.4.6-31.el7_1.1.x86_64


How reproducible: Always.


Steps to Reproduce:
1. Add the following configuration to your Apache:
   ProxyPass /sample/ http://localhost:8080/sample/
   ProxyPassReverse /sample/ http://localhost:8080/sample/
   ProxyErrorOverride On
   ProxyTimeout 10

2. Deploy the sample application in EAP. (I used EAP 6.4 and deployed https://tomcat.apache.org/tomcat-7.0-doc/appdev/sample/sample.war) 

3. Try to load a URL that will cause 404 from backend. I used http://jws3/sample/hellonothing.jsp to reproduce.

Actual results:
When you navigate to URL that triggers 404, you must wait for 10 seconds to go by before seeing 404 page. (10 seconds because that is what ProxyTimeout is set to)


Expected results: I would expect an immediate return of 404 page because the proxy is responding very quickly with a 404. 


Additional info:
I used the same setup as described in Reproduction section but used RHEL 6.7's httpd 2.2.15, which does not behave like this.

Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Coding In Progress

Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved

Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Coding In Progress

Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved

See http://red.ht/1JdK1Tp

Bogdan Sikora <bsikora> updated the status of jira JWS-183 to Reopened

Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2534.html