activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Vincent (JIRA)" <>
Subject [jira] [Commented] (AMQ-4072) RESTful HTTP interface responses do not contain a correlation ID header
Date Tue, 25 Sep 2012 07:27:08 GMT


Stephen Vincent commented on AMQ-4072:

This brings me back to a question I have posed to the User form in the past, but have not
noticed an answer.  What is the best way for a RESTful HTTP client supposed to POST a message
having a correlation ID?  I am able to do it using a JMSCorrelationID query parameter in the
URL.  If I want to vary the correlation ID on a per message basis within a given session,
then I must use a content-type of "application/x-www-form-urlencoded", where I have a JMSCorrelationID
query parameter as part of the message body.  That is the way I have been POSTing messages
with correlation IDs when using my RESTful HTTP client, and why my client has not been seeing
the correlation IDs in response headers -- because I have not been POSTing the message with
the correlation ID as a property.
> RESTful HTTP interface responses do not contain a correlation ID header
> -----------------------------------------------------------------------
>                 Key: AMQ-4072
>                 URL:
>             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:
> 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:

View raw message