Closed tonesoutherland closed 1 year ago
Mitigated in BUGFIX/NonMTOMITI41Message581 branch. Xds Toolktit response to message contained in ITI-41-non-mtom.txt is now:
HTTP/1.1 200 Content-Type=multipart/related; boundary=MIMEBoundary112233445566778899; type="application/xop+xml"; start="doc0@ihexds.nist.gov"; start-info="application/soap+xml" Content-Length=991 Date=Tue, 02 May 2023 14:24:21 GMT Keep-Alive=timeout=20 Connection=keep-alive
--MIMEBoundary112233445566778899
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml" Content-Transfer-Encoding: binary Content-ID: doc0@ihexds.nist.gov
Expected [Multipart] Found [ SIMPLE Format] </fault:Text></fault:Reason></fault:Fault></S:Body></S:Envelope>
--MIMEBoundary112233445566778899--
BUGFIX/NonMTOMITI41Message581 merged to develop branch.
When sending a non-MTOM XDS/XDR ITI-41 request to the simulator a fault exception is returned with a stack trace that does not indicate what the issue is. The XDS simulator tool is behaving correctly since MTOM is required for XD* transactions, however the response needs to be more clear, indicating that the requester is sending a non-MTOM request.
This was discovered testing at the 2023 NA Connectathon in Austin.
See attached files.
ITI-41-non-mtom.txt ITI-41-non-mtom-fault-exceptoin.txt