[MXS-3686] Object names with characters outside of the ASCII range are not rejected Created: 2021-07-26 Updated: 2021-08-26 Resolved: 2021-08-25 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
It is currently possible to define object names with characters that are outside of the ASCII character set range. This causes the links to them to always be invalid as they contain characters that are not suitably encoded. The simple solution to this would be to reject all object names that contain non-ASCII characters and which would require extra processing to format correctly for URL generation. A reasonable requirement would be that the object name could only contain characters from the set of URI unreserved characters. That is, the name would have to match the following PCRE2 pattern:
|
| Comments |
| Comment by markus makela [ 2021-08-24 ] |
|
Limiting the names isn't a very practical solution as production setups might be using unsafe names. To let the users know that there are problems in naming objects like this, a warning can be logged in the MaxScale log as well as interactively in maxctrl. |