cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-846) MTOM Content-Type header is invalid
Date Thu, 26 Jul 2007 01:52:31 GMT

    [ https://issues.apache.org/jira/browse/CXF-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515473
] 

Daniel Kulp commented on CXF-846:
---------------------------------


This is actually a bug in tomcat:
https://issues.apache.org/bugzilla/show_bug.cgi?id=42976

Investigating if we can not have the charset in the start-info....

> MTOM Content-Type header is invalid
> -----------------------------------
>
>                 Key: CXF-846
>                 URL: https://issues.apache.org/jira/browse/CXF-846
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.0
>            Reporter: Daniel Kulp
>            Assignee: Dan Diephouse
>             Fix For: 2.0.1
>
>
> When using MTOM, the Content-Type header in the result message is not valid.  Example:
> HTTP/1.1 200 OK 
> Server: Apache-Coyote/1.1 
> SOAPAction: "" 
> Content-Type: multipart/related; type="application/xop+xml"; boundary="----=_Part_0_2147172487.1185331898894";
start="<root.message@cxf.apache.org>"; start-info="text/xml;charset=UTF-8 
> Content-Length: 7015 
> Date: Wed, 25 Jul 2007 02:51:38 GMT
> Note that the "start-info" section does not have a closing double quote.   Thus, header
parsers may choke on it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message