You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/04/30 13:53:00 UTC
[jira] [Resolved] (ARTEMIS-1793) Do not expose the
_AMQ_ROUTING_TYPE header (at least) in STOMP
[ https://issues.apache.org/jira/browse/ARTEMIS-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-1793.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.1
> Do not expose the _AMQ_ROUTING_TYPE header (at least) in STOMP
> --------------------------------------------------------------
>
> Key: ARTEMIS-1793
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1793
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: STOMP
> Affects Versions: 2.5.0
> Reporter: Lionel Cons
> Assignee: Justin Bertram
> Priority: Minor
> Fix For: 2.5.1
>
>
> Artemis currently exposes the {{_AMQ_ROUTING_TYPE}} at least when using STOMP.
> Here is what a STOMP {{MESSAGE}} frame currently looks like (header part only):
> {code}
> _AMQ_ROUTING_TYPE:1
> content-length:1
> content-type:text/unknown
> destination:whatever
> expires:0
> message-id:123
> persistent:false
> priority:4
> redelivered:false
> timestamp:1523267009887
> {code}
> All the header lines are useful (and with typical lowercase names) except {{_AMQ_ROUTING_TYPE}}.
> If this information can be useful to messaging clients then a more "user friendly" name should be used and documented.
> Otherwise, this header should probably not be exposed, at least not by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)