Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.4.2
-
None
-
None
Description
Wildcards only work on destination paths, separated by standard separator (.), so
FOO.>
FOO.*.BAR
are valid. But if someone want to use non-standard path separator (like /)
FOO/>
FOO/*/BAR
wildcards in won't work. Also, policy, security and other settings that use them will also be ignored.
The easiest way to support this is to create a plugin that will convert destination names using non-standard path separator to default one, so clients can use whatever convention they want and broker config remains the same.