[
https://issues.apache.org/jira/browse/DISPATCH-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021577#comment-17021577
]
Charles E. Rolke commented on DISPATCH-1553:
--------------------------------------------
Sorry, I should have taken my time more in viewing input and output. Router IDs
sent between routers and to qdstat are the literal python strings created after
a config file is decoded by python json.
Mostly this is manageable. Problems arise with control characters (\r, \t, \f,
\n) when they are displayed as text by qdstat or as whitespace by dispatch
console gui.
> Router ID text name is not restricted
> -------------------------------------
>
> Key: DISPATCH-1553
> URL: https://issues.apache.org/jira/browse/DISPATCH-1553
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 1.10.0
> Reporter: Charles E. Rolke
> Priority: Major
>
> The router allows unicode, punctuation, and escaped characters in the Router
> ID attribute string. It is possible to construct an ID that becomes
> python-escaped when displayed in qdstat and log files. The output is
> confusing to read and hard to consume with automated tools since the strings
> are different in a) the config file, b) over the wire between routers, and c)
> in qdstat and logs.
> The proposal here is to limit the characters allowed in a Router ID to the
> following printable ASCII characters:
> * A-Z - uppercase letters
> * a-z - lowercase letters
> * 0-9 - numeric digits
> * '-' - hyphen
> * '.' - period
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
