Bug 1340955 - A VirtualHost's ProxyTimeout or Timeout does not always properly override global Timeout
Summary: A VirtualHost's ProxyTimeout or Timeout does not always properly override glo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: mod_cluster
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2.1.1
Assignee: Jean-frederic Clere
QA Contact: Michal Karm Babacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-30 23:13 UTC by Michal Karm Babacek
Modified: 2019-06-13 12:20 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-13 12:20:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker MODCLUSTER-419 0 Major Open A VirtualHost's ProxyTimeout or Timeout does not always properly override global Timeout 2018-12-12 07:50:06 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.