Bug 1310582

Summary: when ProxyErrorOverride is On, modcluster return 503 status code on subsequent requests
Product: Red Hat Enterprise Linux 6 Reporter: Patrick <pbajenez>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact: Mirek Jahoda <mjahoda>
Priority: urgent    
Version: 6.4CC: aogburn, bnater, dmasirka, jorton, luhliari, mbabacek, mfrodl, mjahoda
Target Milestone: rcKeywords: Patch, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: httpd-2.2.15-56.el6 Doc Type: Bug Fix
Doc Text:
Previously, when the ProxyErrorOverride directive was enabled, the mod_cluster load balancer returned the 503 status code on subsequent requests for about one second. This caused failover, which then propagated through the instances. Additionaly, this bug could be used for the denial of service (DoS) attack. With this update, the requests in the described scenario are now handled correctly with the 200 status code.
 Story Points: ---
Clone Of:
: 1391517 (view as bug list) Environment:
Last Closed: 2017-03-21 11:50:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269194, 1359263, 1391517    
Attachments:
Description Flags
reproducer none

Description Patrick 2016-02-22 10:06:17 UTC 
Description of problem:

When ProxyErrorOverride is On, modcluster return  503 status code on subsequent requests, for about a second before returning 200 status code

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

mod_cluster : 1.2.6.Final  and 1.2.11.Final 
Version jboss EAP : 6.1.1
Version apache httpd : 2.2.15
Version OS : RHEL 6.4
How reproducible:


Steps to Reproduce:
Customer provided a sample app to reproduce.

1. setup mod_cluster and deploy the sample app
2. run the test script, which curl to the sample app. 
3. Observe access and error log

Actual results:
we see around 10 calls after the error, getting 503 while, they should go through

Expected results:

After the broken call, all subsequent unbroken calls should return 200 status


Additional info:
Comment 1 Patrick 2016-02-22 10:12:33 UTC 
Created attachment 1129209 [details]
reproducer
Comment 6 Michal Karm Babacek 2016-11-01 13:16:49 UTC 
You might find this helpful:
See https://bugzilla.redhat.com/show_bug.cgi?id=1309598#c3
And https://bugzilla.redhat.com/show_bug.cgi?id=1309598#c5
Comment 16 errata-xmlrpc 2017-03-21 11:50:08 UTC 
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/RHBA-2017-0784.html
Comment 17 Chris Williams 2017-08-16 16:05:17 UTC 
*** Bug 1450298 has been marked as a duplicate of this bug. ***