[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484583#comment-13484583
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
I updated my C-based client application with the ability to add a
&JMSCorrelationID= query parameter to the URI found in the start-line(first
header) of my POST requests. This allows my app to POST msgs with a
correlation ID within the same session and without having to use a content-type
of "application/x-www-form-urlencoded". I also updated my application with the
ability to specify a "selector" header. This allows me to GET messages based
on correlation ID, but it still would be nice if the JMSCorrelationID header
field would also come back as a response header. BTW, I it appears that within
a session, the first "selector:" header I send with a GET request is honored,
but I am unable to change that selector on subsequent GET requests within the
same session. Am I out-of-luck, or is there a way to have subsequent GET
requests on the same session(having different selector values) be
recognized/honored? 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.8.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
