On 05/06/2015 02:33, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd 2.4.13 can be found > at the usual place: > > http://httpd.apache.org/dev/dist/ [1] > > I'm calling a VOTE on releasing these as Apache httpd 2.4.13 GA. > > [ ] +1: Good to go > [ ] +0: meh > [ ] -1: Danger Will Robinson. And why. > > Vote will last the normal 72 hrs. > > NOTE: The *-deps are only there for convenience. > > Thx! Not a great fan of this ... The SSLCertificateChainFile directive (/usr/local/apache/conf/virtuals/xxxxxxx) is deprecated, SSLCertificateFile should be used instead at all, let alone for every single ssl host conf file :) Was any great thought done to the impact for admins who manage 10's or 100's of thousands of domains and the nightmare hell they will be forced to go through when this is eventually dropped, to convert existing confs, not to mention a large number of commercial control panels will also need modification, as well as the inhouse portals and automation scripts as well. For us its easy enough to overcome when I need to, since we really only seem to have 2 cert providers, but others may have a myriad of them and are in for a rough ride if they have a lot of domains. I know its been in changes since 2.4.9 or so, and I know that it likely wont go away before 2.6, but those upgrading to this version will encounter alarms since the output returns unexpected responses, if they have any sort of monitoring on daemon restarts etc, newbie admins will also likely panic thinking it isnt loading at all. I disagree with this removal, it will cause more problems then benefits IMHO, make it a recommendation to use SSLCertificateFile, but not an essential requirement, perhaps log it, and log it only once, not per every domain, not throw them to std out. Apart from that, builds fine with latest APR APR-Util on multiple Slackware platforms and versions. Links: ------ [1] http://httpd.apache.org/dev/dist/
