You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/10/30 10:38:26 UTC
[jira] [Resolved] (AMQ-4659) REST API MessageServlet does not
accept JSON or plain text content types in request
[ https://issues.apache.org/jira/browse/AMQ-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved AMQ-4659.
------------------------------
Resolution: Duplicate
Fix Version/s: 5.10.0
Assignee: Claus Ibsen
Thanks for reporting. Marking this as duplicate of AMQ-4668 where we have a patch to make this better.
> REST API MessageServlet does not accept JSON or plain text content types in request
> -----------------------------------------------------------------------------------
>
> Key: AMQ-4659
> URL: https://issues.apache.org/jira/browse/AMQ-4659
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, Connector
> Affects Versions: 5.8.0
> Environment: n/a
> Reporter: Ed Valdez-Guillen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 5.10.0
>
>
> Currently, the MessageServlet that ships with ActiveMQ (used by the REST API) ignores the body of HTTP POST requests if the content type is NOT "text/xml". This results in empty messages being sent to target destinations.
> For my particular needs, it would be nice if "text/plain" were allowed because I'm hoping to use the REST API for posting text messages from a VXML voice/web application. However, the VXML platform I'm using only supports "text/plain" content type (not XML or JSON) and the VXML standard itself does not specify which content type(s) should be supported in this case.
> Anyway, I'm not sure if supporting the "text/plain" content type conflicts with REST principles, but I believe at a minimum "application/json" should be allowed along with "text/xml" in the POST request (not just the response).
--
This message was sent by Atlassian JIRA
(v6.1#6144)