activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3518) MessageServletSupport request body does not check the content-type in an intelligent way
Date Thu, 29 Sep 2011 22:01:47 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-3518.
-------------------------------

    Resolution: Fixed

Applied a fix for this, although I did it in a slightly different way than the patch.  

{code}
String contentType = request.getContentType();
if (answer == null && contentType != null && contentType.toLowerCase().startsWith("text/xml"))
{
{code}
                
> MessageServletSupport request body does not check the content-type in an intelligent
way
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQ-3518
>                 URL: https://issues.apache.org/jira/browse/AMQ-3518
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Samples
>    Affects Versions: 5.5.0
>         Environment: Servlet container
>            Reporter: Tadish Durbin
>              Labels: patch
>             Fix For: 5.6.0
>
>         Attachments: MessageServletSupport.patch
>
>
> The MessageServlet used for the REST interface supplied in the demo web app will not
correctly use the request body of an HTTP POST request if the content-type header contains
more than just the MIME type.
> The specification for this header indicates that there can be multiple values in this
header.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message