[
https://issues.jboss.org/browse/MODCLUSTER-549?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-549:
------------------------------------------------
It only makes in rhel/fedora and if stuff like:
"Fri Dec 21 13:47:17.358196 2018] [ssl:info] [pid 758] AH01876: mod_ssl/2.4.29
compiled against Server: Apache/2.4.29, Library: OpenSSL/1.0.2n"
have also a detailed version.
mod_proxy_cluster should display the full version string of httpd it
was built with
-----------------------------------------------------------------------------------
Key: MODCLUSTER-549
URL:
https://issues.jboss.org/browse/MODCLUSTER-549
Project: mod_cluster
Issue Type: Enhancement
Components: Native (httpd modules)
Affects Versions: 1.2.13.Final, 1.3.5.Final
Reporter: Michal Karm
Assignee: Michal Karm
Priority: Major
This is a suggestion to display: {code}
[Tue Oct 25 12:48:18 2016] [notice] Apache/2.2.15 (Unix) DAV/2
mod_cluster/1.2.13.Final_httpd-2.2.15-39.el6.x86_64 configured -- resuming normal
operations
{code} instead of the current version string {code}
[Mon Oct 31 06:31:31 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_cluster/1.2.13.Final
configured -- resuming normal operations
{code}
The motivation is to clearly state with which httpd it is safe to to run
mod_proxy_cluster modules so as to avoid mysterious SegFaults caused by "I took these
mod_proxy_cluster modules build with httpd x and run them with httpd y and it all seemed
to be good up until...".
I'm not absolutely sure this is the right place to do so though. I'd like to hear
from [~rhusar] and [~jfclere] to either upvote this enhancement or to downvote it into
oblivion.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)