Apache httpd 2.4.43-4 with brotli support, TLS 1.3 final (RFC 8446) built against OpenSSL 1.1.1f with http2 and ALPN for Red Hat Enterprise Linux 7 and CentOS 7

Apache httpd 2.4.43-4 with brotli compression library from Google, TLS 1.3 Final (RFC 8446), http2 (HTTP/2) support for Red Hat Enterprise Linux and CentOS added to repository. Mod_ssl is built dynamically against OpenSSL 1.1.1g.

Links:

    <...

Apache
httpd 2.4.43-4 with brotli compression library from Google, TLS 1.3 Final (RFC 8446), http2 (HTTP/2) support for Red Hat Enterprise Linux and CentOS added to repository. Mod_ssl is built dynamically against OpenSSL 1.1.1g.

Links:

Since 2.4.33 we added brotli compression library.
Since 2.4.35 release we start building
Apache
httpd against OpenSSL 1.1.1*.
Since 2.4.37 release TLS 1.3 final version (not to be confused with any draft versions) is supported and enabled by default.
Since 2.4.43-4 release we built OpenSSL as a separate package that installs to the separate directory (/opt/codeit/openssl111) and does not affects system libraries.

Please note that TLS 1.3 final version is supported in Chrome 70+ and Mozilla Firefox 63+.

brotli support is already included in base RPM file. All you need is to add filters like

AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript

Http2
Apache
httpd module no longer supports prefork mpm from version 2.4.27. If you need http2 module, please disable prefork mpm and enable evemt mpm in /etc/httpd/conf.modules.d/00-mpm.conf.
We already made this in 00-mpm.conf in our packages. If you are updating other vendor installation, please update this file.

We already included a minimum required SELinux policy into the package.

Feel free to use our CentOS/RHEL repository. Please also note that this package depends on apr-util 1.5.0+ and libnghttp, which you can found in EPEL repository. So, the easiest way to use our builds of
Apache
HTTPd is to add EPEL repository, if you still do not have it: yum install -y epel-release

25 thoughts on “Apache httpd 2.4.43-4 with brotli support, TLS 1.3 final (RFC 8446) built against OpenSSL 1.1.1f with http2 and ALPN for Red Hat Enterprise Linux 7 and CentOS 7”

  1. Dear Friends

    After installing 2.4.43-4, I have got an error with SSLCompression off after restarting httpd.service.

    I would be glad for your help.

    Thank you in advance for your help and support.

    Sincerely

      1. Dear Alexander

        …but in my last configuration I had line SSLCompression off, but when I try to restart httpd.service I have got an error:

        Setting Compression mode unsupported; not implemented by the SSL library

        In the older version of your 2.4.43 it was working fine with this line.

        Any idea how to resolve this?

        Sincerely

        1. Dear User,

          The purpose of our builds are the new standards: fast, modern and highly secure.
          We upgraded our builds to deliver OpenSSL library in a new dynamic way. Also, we disabled old and vulnerable features in it to additionally save traffic and memory.
          If you want to use these older deprecated features such as compression that leads to CRIME/BEAST vulnerabilities, please use the bundled Apache httpd server from CentOS team. Alternatively, you want to use our builds, please disable the compression:

          SSLCompression off

          As it is not supported in this build.

          1. Dear Alexander

            I think you may not understand me like I want to 🙂 I’m using your builds from day one. I just say, that I have already used: “SSLCompression off” in all my configuration files in vhosts. In this new build 2.4.43-4 this command “SSLCompression off” is no longer recognized, so to properly run my httpd.service I needed to delete this command “SSLCompression off” from my configuration files or just add hash “#” before it.

            The way you are trying to explain, to add “SSLCompression off” to my configuration files or ssl.conf is not working in this build.

            For a good understanding of each other. Your build is forced to use “SSLCompression off”, so there is no need to use this command anymore in any configuration files, because it’s always disabled = SSLCompression off? Is it correct?

            Thank you once more for your great work.

            Sincerely

          2. Dear User,

            Thanks for clarification, indeed I did not usnerstood you right.
            Yes, OpenSSL library that we ship, does not support SSL compression and if you use our library, SSL compression is always off, even you do not explicitly specify “SSLCompression off”.

  2. You should not have removed the SSLCompression option.
    It broke all our server when the update was done. And no warning. My Compression was always set to off.

    Very angry.

    But hey, I’m glad you are offering the repo free of charge.

    1. Actually we did not removed it.
      This is original Apache httpd behavior and we never had SSLCompression in sample config files and test hosts.
      Please always test your configuration after upgrade with

      httpd -t

      And restart your server only after that. Also you can have your own staging environment with similar configuration to be less angry.
      I think we will return compression support temporarily because of this regression.

      1. I use apachectl -t
        Is that why I get no return? the command is wrong?

        Since when does this config is invalid then? I had SSLCompression off since 2018

          1. Well, I tested httpd -t and it worked.
            Must be a change that happend sometime ago. Or when I switched repo for yours.

            This morning my system updated to this :
            httpd x86_64 2.4.43-4.codeit.el7 CodeIT 1.4 M
            httpd-filesystem noarch 2.4.43-4.codeit.el7 CodeIT 29 k
            httpd-tools x86_64 2.4.43-4.codeit.el7 CodeIT 94 k
            mod_ssl x86_64 1:2.4.43-4.codeit.el7 CodeIT 121 k
            Installing for dependencies:
            openssl111-libs x86_64 1.1.1g-1.codeit.el7 CodeIT 1.4 M

            Works OK right now. Won’t update manually. Thanks a lot for your help

  3. Our server is crashing almost daily after we upgraded to 2.4.43-4. A lot of mpm errors and zend memory issues. Basically overnight the ram usage goes from 20% to 100% and everything crashes. The only solution is to keep rebooting constantly. Just updated to 2.4.43-5. Do you know what was fixed in this version?

    1. Hello,

      In 2.4.43-5 we only rebuilt it with OpenSSL compression support to return SSLCompression back.

      Please check different mpms and php support for them. Usually they recommend to use php-fpm for event and preform mpms.

  4. Hi Alexander,

    I am working to fix a bug with httpd and mod_http2 (using your 2.4.43 from the centos 7 repo). I need to build an rpm with latest changes from https://github.com/icing/mod_h2 (from master) into a mod_http2.x86_64 1.15.9-x.codeit @CodeIT or similair
    would be good that I use your script for that (to speed up the build) so I can do locally. Is that something you could share? Please could you reply personally?
    This will help to fix mod_http2 – https://github.com/icing/mod_h2/issues/201

      1. hmm, you have an interesting dependancy in the mod_http2-1.15.9-1.codeit.x86_64 on the build being performed under /root/ folder, so tests fail if this process is executed from the non-root user 🙂 but so far going ok

      2. Hi, Alexander

        So there is a new 1.15.12 version of mod_http2 that fixes among other things
        header parsing which prevents 431 errors when cookies number approaches 100 on Firefox and Chrome 🙂
        looking forward to see that in your repos 🙂

  5. Hello,

    First of all, thanks for the great work.

    With your packages (Apache 2.4.43 as well as Apache 2.4.41), I have not able to override umask, which is mandaroty for my use. I tried different solution without effect.

    Is it related to a specific compiling option you are using?

    Many thanks in advance

  6. Hello, if I don’t set MaxConnectionsPerChild 0 or leave it as default httpd becomes unresponsive even if not high CPU or RAM usage, and after a while AH03490: scoreboard is full, not at MaxRequestWorkers.Increase ServerLimit. on error log. So, it could be caused by your additional modules or also modpagespeed from Google. Hard to say what, unless you let me know how to inspect what prevent httpd from correctly recycling children. Thanks

  7. Hi,
    about two weeks ago I replaced the CentOS httpd version with the 2.4.43 on one server that uses WebDAV. Replacement worked well as usual but now I have problems with the WebDAV connections.

    Reading directory contents works but if I try to create a new file/folder I get this message in error_log:
    [dav_fs:crit] [pid 8728:tid 139838229575424] (20019)DSO load failed: AH00576: The DBM driver could not be loaded

    After some seaches on different sites I really don’t understand what could be the cause for that problem. I only could see that all mentioned packages and modules come with the CodeIT version so everything should be fine.

    Just saw that there ist the new version 2.4.46, but after an update I still get this messages.
    So has anybody an idea of what the problem could be?

    Thank you very much!

Leave a Reply

Your email address will not be published. Required fields are marked *