Skip to content

Conversation

@Ksloveyuan
Copy link

When integrate with id3, I find out that in the header of response, the content type is

multipart/related; type="application/xop+xml";start="<http://tempuri.org/0>";boundary="uuid:xxxx";start-info="text/xml"

I have to tweak a bit to make it work, not sure if it is the problem of id3, or the check logic

@giovanni-orciuolo
Copy link
Contributor

I'm having the same problem with another soap service which returns MTOM with text/xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants