You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/09/30 13:53:15 UTC

[GitHub] [pulsar] teabot commented on pull request #17151: [fix][broker] Added check for invisible characters for subscription name

teabot commented on PR #17151:
URL: https://github.com/apache/pulsar/pull/17151#issuecomment-1263605886

   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. Practically speaking, it should be possible to correctly transport any characters (including invisible ones) via a correctly encoded URL. If this is the case, I'd recommend:
   
   1. Preventing **new** names from being created with invisible/indistinguishable characters 
   2. Fix URL handling so that any existing names with such characters can still be managed


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org