NGINX 1.23.2 mainline added to EL7, EL8, EL9 repositories. brotli compression module from Google, http2, ngx cache purge и ngx http geoip2 modules added or built-in. OpenSSL built dynamically using OpenSSL+QUIC 1.1.1r.
TLS 1.3 final works with Google Chrome 70+ and Mozilla Firefox 63+.
RHEL 7 / CentOS 7:
yum upgrade -y codeit-repo-release yum-config-manager --enable CodeIT-quic --save
RHEL 8-9 / Alma Linux 8-9 / Rocky Linux 8-9 / CentOS 8-9 / Other EL8/EL9 repos are modular now. To install nginx with HTTP/3 support, you need to enable the appropriate stream:
dnf module enable -y nginx:codeit-quic
We build OpenSSL+QUIC 1.1.1 separately since v1.21.6, installing it separately to /lib64 with .so.81.1.1 suffix to ensure it won’t interfere with your system libraries.
I have been using this suite on AlmaLinux 8 for a month, it is still very stable, thanks, I have upgraded to the latest version, but nginx still shows nginx/1.23.1, it should be nginx/1.23.2, please pay attention to the details , continue to improve everyone’s confidence. grateful
[root@server ~]# nginx -v
nginx version: nginx/1.23.1
[root@server ~]# yum upgrade -y
Last metadata expiration check: 0:30:15 ago on Tue 01 Nov 2022 04:57:13 PM CST.
Dependencies resolved.
Nothing to do.
Complete!
[root@server ~]# rpm -qa|grep nginx
nginx-1.23.2-1.module_codeit_quic.codeit.el8.x86_64
nginx-filesystem-1.20.1-6.module_el8+12928+992082b2.noarch
Thanks for reporting! This is the known versioning problem of the upstream nginx: they first update the code for weeks, then perform the update release tags. When we see tags are updated, we do the QUIC release.
Only then versions are updated, sometimes day after, sometimes weeks (as they merge upstream minor changes to https://hg.nginx.org/nginx-quic/).
Earlier, nginx made update first for the next version instead. In this case you would receive 1.23.3 even it is not released yet.
Of course, we can ship a minor updates after that (but there are no significant changes at all yet), but please do not expect exact versions match for the quic branch because we build it from the repository (replacing the tarball in the mainline version).
Thanks for the explanation, it turned out to be a problem with the nginx upstream, I understand, please understand my rudeness.
No problem at all, you are welcome.
So the problem is nginx do not provide QUIC releases at all, it’s a live repository, so we tied our own releases to the mainline versions release.
These two version numbers are wrong and have not been fixed.
[root@server ~]# rpm -qa|grep el7
libbrotli-1.0.9-1.codeit.el7.x86_64
brotli-1.0.9-1.codeit.el7.x86_64
These packages are manual EL9 rebuilds of EL7 version of our package.
I see the error, but we have no CI/CD process for the brotli package now (as the upstream releases are stopped) and cannot provide additional effort to rebuild it at this moment.
When 1.0.10 will be released, we will set up full CI/CD process for all the supported repos and the tag will be fixed.
Do you have any side effects from the wrong package name?
The repo is free and we need to mitigate the efforts, if they have no or minor problems for the users.
Thanks for the understanding.
Thank you for your explanation. Except for the suspicious and disturbing package name, it has no real impact. I hope you can fix it when the new version comes out. You guys have done a great job, thank you for your efforts.