[
https://issues.apache.org/jira/browse/DISPATCH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620601#comment-14620601
]
Ted Ross commented on DISPATCH-148:
-----------------------------------
Another possibility is to strip the x-opt-qd.* headers on egress, so they don't
appear in client applications. This could be configurable per
listener/connector and default to strip.
> Strip qpid-dispatch-specific delivery properties on ingress
> -----------------------------------------------------------
>
> Key: DISPATCH-148
> URL: https://issues.apache.org/jira/browse/DISPATCH-148
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Reporter: Ted Ross
> Fix For: 0.5
>
>
> Messages that ingress from endpoints outside of the router should have any
> x-opt-qd headers removed from the delivery properties.
> Occasionally developers will re-use received messages for transmit and not
> clear the delivery properties. This can result in mysterious dropping of
> messages due to anti-looping (i.e. the x-opt-qd-trace header shows the
> message passing through the router already and the message is dropped).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
