[
https://issues.apache.org/jira/browse/AMQ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464303#comment-13464303
]
Stephen Vincent commented on AMQ-4072:
--------------------------------------
I believe I found a way for me to POST many messages on the same connection but
with varying correlation IDs. I have learned that the first/start line of a
HTTP request message begins with the method, followed by the identifier of the
resource, and then the protocol version in use. For example:
POST /demo/message?destination=myqueue&type=queue HTTP/1.1
Even though that URI is what I specified at connection time, I am apparently
allowed to modify it on subsequent POSTs. For example, adding/updating a
JMSCorrelationID pparameter seems to be allowed. I have asked the person
supporting our HTTP client layer to allow me to add parameters when making
requests. Unfortunately, he is over-booked and tells me it must wait until our
next release. Bummer.
Even if I were to accidentally mess-up the resource portion of the start line,
I assume I would just get a "not found" error, or something else that will
hopefully be harmless. If you know of any reasons why it is bad to change the
URI on POSTS, please let me know.
> 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
