Angie and Angie PRO updated to version 1.12.3#
A maintenance release of Angie and Angie PRO 1.12.3 fixes ACME certificate issuance, connection reuse in upstream groups with keepalive, and request hangs on retries, and adds two third-party modules.
Maintenance releases of Angie and its commercial version Angie PRO — 1.12.3 — have been published. They contain no security fixes; instead, they correct several bugs that can affect production configurations:
ACME certificates are now issued in two cases that used to fail: for an IP address validated with ALPN, which Let's Encrypt rejected, and for deeper subdomains such as
test.sub.example.comwhen the domain list also contains a wildcard such as*.example.com;in an
upstreamblock that combines the keepalive and zone directives, removing a server, for example during a DNS update with the resolve option, no longer corrupts shared memory, so a cached connection is no longer reused for a different server;a
POST,LOCK, orPATCHrequest whose response status is listed in proxy_next_upstream withoutnon_idempotentnow returns that status at once instead of hanging until the read timeout and ending with 504;the SSL statistics of status_zone now count failed and timed-out handshakes on HTTP/3 connections.
In Angie PRO, active upstream_probe probes no
longer keep a recovered server out of load balancing longer than
fail_timeout after passive checks marked it unavailable.
The bundled third-party module packages were also refreshed: two new modules,
angie-module-cache-turbo and angie-module-error-abuse, and new
versions of four more. The Docker images in our
registry are now built on Alpine 3.24, Debian 13, Rocky Linux 10, and
Ubuntu 26.04. Each of these systems also has its own tag that always points to
the latest Angie version: angie:alpine-latest,
angie:debian-latest, angie:rocky-latest, and
angie:ubuntu-latest.
More details about the changes:
Have a great day!