Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.9.md

RabbitMQ `3.7.9` is a maintenance release. It focuses on bug fixes and minor usability improvements. CLI tools in this release will often produce an extra line of output, as they did in `3.6.x` releases, when `-q` is not provided. Tools that parse CLI command output should use `-q --no-table-headers` to suppress all additional output meant for interactive use or avoid parsing output entirely (e.g. use the HTTP API). When upgrading to this release and upgrading Erlang to 21.0 at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Queue deletion loaded bindings in an inefficient way. GitHub issue: Heartbeat monitor now correctly sends heartbeats at half the negotiated timeout interval. It previously could fail to do so because it considered its own traffic to be on-the-wire activity from the peer. GitHub issue: Nodes were using a was not enabled. GitHub issue: `ERLEPMDPORT` was ignored when configured in `rabbitmq-env.conf`. GitHub issue: Proxy Protocol dependency is now compatible with Erlang/OTP 21. GitHub issue: It is now possible to configure using new style config format. GitHub issue: When a listener fails to start (bind to a server socket), error messages involve less context and are easier to read. GitHub issue: Improved error reporting for when `erl` or `erl.exe` are no in node's `PATH`. GitHub issue: 10 TLS connection acceptors are now used by default. GitHub issue: `rabbitmqctl list_` commands did not include table column headers. GitHub issue: If `RABBITMQ_NODENAME` is configured, CLI tools will use its hostname part when generating its own Erlang node name. GitHub issue: On Windows CLI tool batch scripts exited with a 0 exit code when it failed to connect to the node. Contributed by Artem Zinenko. GitHub issue: . `rabbitmqctl stop` now supports `--idempotent` that makes the command exit with a success when target node is not running. GitHub issue: `rabbitmqctl add_vhost` is now idempotent (no longer returns an error when vhost already exists) GitHub issue: Logo link now works better with a non-blank API endpoint prefix. GitHub issue: Decimal headers and argument values are now serialised to JSON

GitHub issue: It is now possible to configure both HTTPS and HTTP listeners using new syntax that's consistent with Web STOMP and Web MQTT plugins: ``` ini management.tcp.port = 15672 management.ssl.port = 15671 management.ssl.cacertfile = /path/to/ca_certificate.pem management.ssl.certfile = /path/to/server_certificate.pem management.ssl.keyfile = /path/to/server_key.pem ``` GitHub issue: It is now possible to configure `Content-Security-Policy` (CSP) header set by the API. GitHub issue: It is now possible to configure `Strict-Transport-Policy` (HSTS) header set by the API. GitHub issue: `GET /api/nodes/{node}` endpoint aggregated data for other cluster nodes only to discard it later. GitHub issue: When `Handle.exe` is used and returns no file handle information in its output, a warning will be logged. GitHub issue: String matching queries now support multi-value results. GitHub issue: `addomain` and `aduser` are new variables available in LDAP plugin queries. They are extracted from the username when it's in `Domain\User` format, which is typically specific to ActiveDirectory. GitHub issue: Search queries that return referrals will result in an error instead of an exception. GitHub issue: Advanced WebSocket options now can be configured. Compression is enabled by default. Compression won't be used with clients that do not support it. GitHub issues: , WebSocket `PING` frames are now ignored instead of being propagated to MQTT frame handler. GitHub issue: Advanced WebSocket options now can be configured. Compression is enabled by default. Compression won't be used with clients that do not support it. GitHub issues: EC2 API endpoint requests used an unreasonably low timeout (100 ms). The new value is 10 seconds. GitHub issue: It wasn't possible to specify Consul service tags via new style config format. GitHub issue: It wasn't possible to configure lock key prefix via new style config format. GitHub issues: Lock acquisition timeout now can be configured using `clusterformation.consul.locktimeout` as well as `clusterformation.consul.lockwait_time` (an alias), to be consistent with the Etcd implementation. GitHub issue: Lock acquisition timeout now can be configured using `clusterformation.etcd.locktimeout` as well as `clusterformation.etcd.lockwait_time` (an alias), to be consistent with the Consul implementation. GitHub issue: Throughput optimizations reduce probability of high memory consumption by `rabbit_event` processes due to event backlog accumulation. GitHub issue: Post-installation script renamed `rabbitmq.conf` to `rabbitmq-env.conf`. A long time ago `rabbitmq.conf` was used to configure environment variables (like `rabbitmq-env.conf` today) and old post-installation steps were not removed when `rabbitmq.conf` was re-adopted for new style config files. GitHub issue: