Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1340955

Summary:	A VirtualHost's ProxyTimeout or Timeout does not always properly override global Timeout
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Michal Karm Babacek <mbabacek>
Component:	mod_cluster	Assignee:	Jean-frederic Clere <jclere>
Status:	CLOSED WONTFIX	QA Contact:	Michal Karm Babacek <mbabacek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	aogburn, bperkins, jdoyle, pslavice, rsvoboda
Target Milestone:	---
Target Release:	2.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-13 12:20:04 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:

Description Michal Karm Babacek 2016-05-30 23:13:03 UTC

See https://issues.jboss.org/browse/MODCLUSTER-419 for description.

TL;DR:
With a shorter global Timeout and a longer ProxyTimeout specified in the VirtualHost, the VirtualHost's ProxyTimeout does not always take precedence.