[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839857#comment-13839857
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
Updating the MessageServlet to have the JMSCorrelationID message header field
added as a response header(as is done with the message properties) would be
great. That will allow my client app to make the *real* JMSCorrelationID
*field* available to my users without depending on the originators of the
messages creating a correlation ID message *property* as a circumvention.
Thanks in advance.
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>
> Key: AMQ-4072
> URL: https://issues.apache.org/jira/browse/AMQ-4072
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.6.0
> Environment: RESTful HTTP client
> Reporter: Stephen Vincent
> Fix For: 5.x
>
> Attachments: CorrelId.java
>
>
> When using a RESTful HTTP client to GET a message that has a correlation ID,
> the correlation ID is not sent as a header in the response from the broker.
> This inhibits my RESTful HTTP client from performing request-response.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
