Bug 1242416
| Summary: | Apache httpd ProxyPass connectiontimeout parameter does not have effect when proxying to AJP back-end | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Janne Snabb <janne.snabb> |
| Component: | httpd | Assignee: | Luboš Uhliarik <luhliari> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Frodl <mfrodl> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | isenfeld, janne.snabb, jkaluza, jorton |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | httpd-2.4.6-36.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: mod_proxy_ajp created proxy worker with wrong name when the default AJP port (8009) has been explicitely used in the ProxyPass definition.
Consequence: All additional settings set using mentioned ProxyPass directive has been ignored (They have been set to worker with wrong name).
Fix: mod_proxy_ajp now creates proxy worker with the proper name in mentioned situation.
Result: Additional settings set using ProxyPass directive are not ignored anymore.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 04:38:20 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
Janne Snabb
2015-07-13 09:51:15 UTC
I believe that this is a regression introduced by the UDS patch in RHBA-2015:0029-1 / RHSA-2015:0325-2 / BZ#1170286 / BZ#1168081. This has been fixed upstream in <http://svn.apache.org/r1650655>. Thanks for the report Janne, please open a ticket with Red Hat support if you would like a test package to confirm the fix. 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-2015-2194.html |