Documentation Home
MySQL Router Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 275.4Kb
PDF (A4) - 275.7Kb


MySQL Router Release Notes  /  Changes in MySQL Router 26.x  /  Changes in MySQL Router 26.7.0 (2026-07-28)

Changes in MySQL Router 26.7.0 (2026-07-28)

Important

As of this release, MySQL Router moves to a single version release model. MySQL Router series 8.4 and 9.7 are now discontinued.

The latest version of MySQL Router remains compatible with all supported MySQL Server versions. That is, MySQL Router 26.7 is compatible with MySQL Server 8.4, 9.7, and 26.7.

It is recommended that you use the latest version of this software.

Functionality Added or Changed

  • MySQL Router can now enforce limits on HTTP connections, and request and response body sizes. The following http_server configuration parameters are introduced:

    • max_http_connections: Maximum number of simultaneously active client connections the HTTP server will allow. Permitted range is 1 to 100000 connections. Default value is 1024.

    • max_request_body_size: Maximum allowed size, in bytes, of a HTTP request body. Permitted range is 0 to 2147483648 (2 GiB). Default value is 16777216 (16MiB).

    • max_response_body_size: Maximum allowed size, in bytes, of a HTTP response body sent by the HTTP server. Permitted range is 0 to 2147483648 (2 GiB). Default value is 16777216 (16MiB).

    The options can be set in the [http_server] or [DEFAULT] configuration sections Values defined in [http_server] takes precedence. The defaults apply when neither section supplies a value and replace the previous unlimited behavior.

    When the connection limit is reached, the HTTP server closes or refuses excess TCP connections without sending an HTTP response. An oversized request is rejected with 413 Payload Too Large, followed by graceful shutdown of the connection. An oversized response is replaced with 500 Internal Server Error without a response body, after which the connection is closed. Rejection logging is rate-limited to prevent log flooding. (Bug #39268619, WL #17288)

Bugs Fixed

  • Trailing semi-colons following START TRANSACTION, BEGIN, and BEGIN WORK, resulted in rejection of those transactions when connection sharing was enabled. (Bug #39190243)

  • Fixed an issue relating to shutdown sequences. (Bug #38537545)