[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-549) mod_proxy_cluster should display the full version string of httpd it was built with

Michal Karm Babacek (JIRA) issues at jboss.org
Mon Oct 31 06:37:00 EDT 2016


Michal Karm Babacek created MODCLUSTER-549:
----------------------------------------------

             Summary: 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.3.5.Final, 1.2.13.Final
            Reporter: Michal Karm Babacek
            Assignee: Michal Karm Babacek


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.2.2#72004)


More information about the mod_cluster-issues mailing list