[MXS-4301] Allow case-insensitive [maxscale] section name Created: 2022-09-19  Updated: 2023-03-28  Resolved: 2022-11-11

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 22.08.0, 22.08.1
Fix Version/s: 22.08.3

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-170

 Description   

Up to maxscale 6.4 the [maxscale] header could be written in mixed case, e.g. [MaxScale] would also work. Starting with 22.08.0 this is no longer the case and only the lower case [maxscale].

While this case insensitive behavior was never really documented, and documentation examples seem to have used the lower case form exclusively as far as I can tell, we already had one customer running into problems on an upgrade to 22.08 due to this.

So we should either restore the previous behavior, or at least clearly document this as backwards incompatible change in the 22.08 release notes ...


Generated at Thu Feb 08 04:27:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.