[
https://issues.apache.org/jira/browse/ARTEMIS-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916470#comment-16916470
]
Justin Bertram edited comment on ARTEMIS-2455 at 8/30/19 7:12 PM:
------------------------------------------------------------------
bq. If you don't want the translation to happen then don't use the same
character in your MQTT destination names as the configured {{delimiter}}.
I cannot prevent users to publish to topics containing characters that are
perfectly allowed by the MQTT protocol.
So I can assume the MQTT acceptor is not MQTT compliant.
was (Author: [email protected]):
"If you don't want the translation to happen then don't use the same character
in your MQTT destination names as the configured {{delimiter}}."
I cannot prevent users to publish to topics containing characters that are
perfectly allowed by the MQTT protocol.
So I can assume the MQTT acceptor is not MQTT compliant.
> Unexpected MQTT path separator conversion handling
> --------------------------------------------------
>
> Key: ARTEMIS-2455
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2455
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
> Affects Versions: 2.9.0
> Reporter: Riccardo Modanese
> Priority: Minor
> Attachments: MqttTopicIT.java
>
>
> Hello, I noticed an unexpected MQTT path separator conversion handling. (May
> be I'm missing some configuration parameter in the acceptor definition?)
> The char '.' on a MQTT topic is handled by Artemis as a topic separator
> instead of a "normal" topic character. So an MQTT topic like 'a.b.c.d'
> becames 'a/b/c/d'.
> I attach a Junit test I developed for testing different topics.
> I used Artemis 2.9.0. The acceptor configuration is:
> {{tcp://0.0.0.0:1883?tcpSendBufferSize=1048576&tcpReceiveBufferSize=1048576&protocols=MQTT&allowLinkStealing=true&useEpoll=true}}
>
> Regards,
> Riccardo
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
