Forum Discussion
CirrusASM - SOAP attachment problem
Hi,
is anyone familiar with SOAP attachments?
I try to implement this in a webservice, but I allways get the error message: xop:Include, Element is not not defined in schema
Does the ASM doesn't support MTOM attachments with xop:include, what is recommended by w3c?
Thx & regards
17 Replies
Mike_MaherNimbostratus
What version are you running?
Can you post an copy of the request and violation?
Tortisry,
we are running v11.2
a request looks like this:POST /webservice HTTP/1.1 Accept-Encoding: gzip,deflate SOAPAction: "soapaction" Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_24_10162050.1354098068576" MIME-Version: 1.0 User-Agent: Jakarta Commons-HttpClient/3.1 Host: host Content-Length: 155375 ------=_Part_24_10162050.1354098068576 Content-Type: application/xop+xml; charset=UTF-8; type="text/xml" Content-Transfer-Encoding: 8bit Content-ID: .... .... ------=_Part_24_10162050.1354098068576 Content-Type: application/pdf; name=file.pdf Content-Transfer-Encoding: binary Content-ID: Content-Disposition: attachment; filename="file.pdf" %PDF-1.3 %�쏢 7 0 obj <> stream ....
Violation is:
XML data does not comply with schema or WSDL document
XML Bufferxop:Include
DescriptionMalformed document - schema validation failed, Element is not defined in schema
ContextURL
Its a request like w3c recommendation @ http://www.w3.org/TR/2005/REC-xop10-20050125/
(example 2)
In the schema, we only define:Base64 coded binary
But this seems to be wrong.
regards- Mike_Maher
So I will admit I am a bit new to XML, but here goes.
So it appears your problem is with this line in your request, the ASM thinks that xop:Include is an element, and since xop:Included is not a defined element in your schema attached to the XML Profile that is why you are getting blocked.
When I look at the information on http://www.w3.org/TR/SOAP-attachments I can see why it thinks that is an element as it matchs the format I am seeing in examples here. Based just upon this it would appear the correct format for this line should be.<sch:inhalt><xop:Include href="cid:file.pdf"/>sch:inhalt>
However considering what you are wanting to do with base64 encoding I am not sure that is entirely correct. Lastly from an ASM policy perspective you may want to make sure that Allow SOAP Attachments is turned on in your XML Profile. Hope this helps a little and I am not telling you what you already know. Mike<inhalt href="cid:file.pdf"/> - Tortisry, this doesn't work. :-(
base64 is used, because the file is allways base64-encoded. - Tortiok, the answer from support is: there is no mtom support @ASM v11.x, although it is recommended by w3c since 2007!
And the best is, SOAP 1.2 isn't fully supported @ ASM 11.2, although it is documented :-( really disappointing.
I close the this talk - J_LE_42749
Hello there,
I'm hitting the same issue with 11.3 version...
Torti => so finally what did you do to solve your problem? Did you disable XML parsing on this URL and applied HTTP profile only?
It would be also great if someone from the community knows about mtom support on ASM... any existing RFE for that?
Thanks Jérôme
- Torti
...one year later, there is no mtom support :-(
I did deactivate the blocking mode for the xml validation (3 violations in the list). So, the requests are parsed as xml traffic, although blocking is disabled. Its like parsing as normal http traffic, but the AV inspection for soap attachments seems to work.
- Torti
It is the best, that everybody with the same problem open a support case at f5. Then the problem would get a higher rating and they would fix it. If there is only one customer with this problem, the rating is to low and its not necessary to change something.
- J_LE_42749
Thank you for your feedback Torti - will open a SR with F5 and get (hopefully!) a RFE ID.
Do you mind giving me the SR that you opened a year ago? So that I can reference the same in my own SR.
Thanks
- Torti
SR C1234492, BugID 408155
