Bug 1240399 - Use of ProxyErrorOverride causes slow response time for error status code (4xx)
Summary: Use of ProxyErrorOverride causes slow response time for error status code (4xx)
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: JBoss Web Server 3
Classification: Retired
Component: httpd
Version: 3.0.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Weinan Li
QA Contact: Michal Karm Babacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-06 19:43 UTC by Robert Bost
Modified: 2016-02-10 07:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-07-07 04:52:02 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JWS-183 0 Critical Resolved Use of ProxyErrorOverride causes slow response time for error status code (4xx) 2016-02-10 07:25:22 UTC

Description Robert Bost 2015-07-06 19:43:04 UTC
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): 3.0


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 JBoss EWS 2.1. I did not see the issue in 2.1.

Comment 2 Michal Karm Babacek 2015-07-07 04:52:02 UTC
JWS 3 product issues are no longer tracked in BugZilla.

Please, follow: https://issues.jboss.org/browse/JWS-183

Comment 3 JBoss JIRA Server 2015-12-17 11:00:48 UTC
Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Coding In Progress

Comment 4 JBoss JIRA Server 2015-12-17 11:08:58 UTC
Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved

Comment 5 JBoss JIRA Server 2015-12-17 11:13:22 UTC
Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Coding In Progress

Comment 6 JBoss JIRA Server 2015-12-17 11:13:28 UTC
Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved

Comment 7 JBoss JIRA Server 2016-01-21 13:50:40 UTC
Bogdan Sikora <bsikora> updated the status of jira JWS-183 to Reopened

Comment 8 JBoss JIRA Server 2016-02-10 07:25:23 UTC
Michal Karm Babacek <mbabacek> updated the status of jira JWS-183 to Resolved


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