github bunkerity/bunkerweb v1.6.10-rc6

pre-release11 hours ago

Documentation : https://docs.bunkerweb.io/1.6.10~rc6/

Docker tags :

  • All-in-one : bunkerity/bunkerweb-all-in-one:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb-all-in-one:1.6.10-rc6
  • BunkerWeb : bunkerity/bunkerweb:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb:1.6.10-rc6
  • Scheduler : bunkerity/bunkerweb-scheduler:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb-scheduler:1.6.10-rc6
  • Autoconf : bunkerity/bunkerweb-autoconf:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb-autoconf:1.6.10-rc6
  • UI : bunkerity/bunkerweb-ui:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb-ui:1.6.10-rc6
  • API : bunkerity/bunkerweb-api:1.6.10-rc6 or ghcr.io/bunkerity/bunkerweb-api:1.6.10-rc6

Linux packages : https://packagecloud.io/app/bunkerity/bunkerweb/search?q=1.6.10~rc6&filter=all&dist=

Changelog :

  • [BUGFIX] misc: fix per-service HTTPS handshakes aborting with no ssl_client_hello_by_lua* defined in server <name> under DISABLE_DEFAULT_SERVER_STRICT_SNI=yes after the rc5 NGINX 1.30.0 bump, by emitting a no-op ssl_client_hello_by_lua_block in per-service blocks. Unknown-SNI rejection on the default server is unchanged.
  • [BUGFIX] database: add a __del__ safety net on the SQLAlchemy Database wrapper so per-job engines dispose cleanly on GC. Without it, scheduler jobs reloaded via importlib.reload dropped their pool connections without sending COM_QUIT (MariaDB/MySQL) or the protocol Terminate (PostgreSQL), producing a burst of Aborted connection ... (Got an error reading communication packets) warnings every cycle.
  • [FEATURE] misc: new MAX_HEADERS setting (default 100) caps header lines per request, leveraging the max_headers directive shipped with the NGINX 1.30.0 bump.
  • [FEATURE] reverseproxy: new per-backend REVERSE_PROXY_HTTP_VERSION setting (default 1.1, accepts 1.0/1.1/2) lets operators opt the upstream leg onto HTTP/2, leveraging the proxy_http_version 2 support shipped with the NGINX 1.30.0 bump. The WebSocket branch stays pinned to 1.1 since WS Upgrade is incompatible with HTTP/2 upstream.
  • [FEATURE] templates: the bundled ui and api templates now pin REVERSE_PROXY_KEEPALIVE=yes, reusing the upstream TCP/TLS connection across admin clicks and API calls for lower click-to-render latency.
  • [PERF] database: add 18 missing single-column indexes. (Fixes #3368, addresses #3367)

Don't miss a new bunkerweb release

NewReleases is sending notifications on new releases.