lordcheng10 commented on PR #17151: URL: https://github.com/apache/pulsar/pull/17151#issuecomment-1264206243
> Is the root of the problem here that the character sequences in question are not being properly encoded when forming the admin URLs? From the example given, I am seeing what looks to be a URL encoding of a Java[Script] escaped form of the original name, rather than a direct encoding of the original name. There are also some pretty odd character codes in the formed URL — the backslash of `\u....` seems to have been encoded as `%255C`: > > * [%255C — ╜](https://www.htmlsymbols.xyz/unicode/U+255c) > * [%25BD — ▽](https://www.htmlsymbols.xyz/unicode/U+25bd) > * [%25BF — ▿](https://www.htmlsymbols.xyz/unicode/U+25bf) > * [%25ED — ◯](https://www.htmlsymbols.xyz/unicode/U+25ed) > > Practically speaking, it should be possible to correctly transport any characters (including invisible ones) via a correctly encoded URL. I suspect there is a character encoding issue somewhere. If this is the case, I'd recommend: > > 1. Preventing **new** names from being created with invisible/indistinguishable characters > 2. Fix name encoding / URL handling so that any existing names with such characters can still be managed 1. There is no problem with encoding; 2. The problem is that the subscription name contains invisible characters, and invisible characters cannot be entered on the command line, resulting in the command reporting an error: Subscription not found -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
