[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463013#comment-13463013
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
If my HTTP client were to make a POST request containing a header such as
"JMSCorrelationID: mycorelID", it would be great if the MessageServlet would
notice it and call message.setJMSCorrelationID. Is that something that could
be considered? I would love to be able to make many POST requests within the
same session with varying correlation IDs, and not have to use a content-type
of "application/x-www-form-urlencoded".
> 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: Broker
> Affects Versions: 5.6.0
> Environment: RESTful HTTP client
> Reporter: Stephen Vincent
> Priority: Critical
> Fix For: 5.7.0
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
