[
https://issues.apache.org/jira/browse/CXF-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Diephouse closed CXF-846.
-----------------------------
Resolution: Fixed
I removed the charset=foo from the start-info header in SVN. I've confirmed
this works fine with .NET. Since this is what the JAX-WS RI does as well, we
should be fine.
> 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="<[EMAIL
> PROTECTED]>"; 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.
