Forum Discussion

marcelcasado's avatar
marcelcasado
Occasional Contributor
17 years ago

MTOM/XOP request attachments seems broken on 3.0 and 3.0.1

Hi,

I started trying to use soapUI 3.0 and 3.01 on Mac (both dmg & zip) and seems that the MTOM/XOP upload attachments in a request is broken. It works just fine on 2.5 but when importing the project in 3.0 or 3.01 it sends just a blank request. Looking to the raw view for the same project and test step :

In 3.0 :

POST http://weather.aero/nnew/fy09/fhs/DataT ... ingService HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:Thresholding"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: weather.aero
Content-Length: 0



in 2.5.1 :

POST http://weather.aero/nnew/fy09/fhs/DataT ... ingService HTTP/1.1
Accept-Encoding: gzip,deflate
SOAPAction: "urn:Thresholding"
Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_46_1837057228.1252698533323"
MIME-Version: 1.0
User-Agent: Jakarta Commons-HttpClient/3.1
Host: weather.aero
Content-Length: 687106


------=_Part_46_1837057228.1252698533323
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: 8bit
Content-ID:


   

   
     
         
           
               urn:fdc:ncar.ucar.edu:Dataset:Turbulence
               COVERAGE
               
                 
                     0
                     
                     
                       
                           MAX_VALUE
                           <=
                           0.38
                       

                     

                     0
                     green
                 

                 
                     1
                     
                     
                       
                           MIN_VALUE
                           >
                           0.38
                       

                       
                           MAX_VALUE
                           <=
                           0.63
                       

                     

                     1
                     yelow
                 

                 
                     2
                     
                     
                       
                           MIN_VALUE
                           >
                           0.63
                       

                     

                     2
                     red
                 

               

               
                  Turbulence_SIGMET_AIRMET
                 
               

             
           

           
         

     

   

------=_Part_46_1837057228.1252698533323
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <402060121515>

âHDF

8 Replies

  • marcelcasado's avatar
    marcelcasado
    Occasional Contributor
      I sent an email to support@eviware.com with the project attached and some instructions.

      Thanks for looking into it . Please let me know about the resolution.

    -Marcel
  • marcelcasado's avatar
    marcelcasado
    Occasional Contributor
      Hi Ole,

      It looks much better but I think there is still a problem with the encoding of the data since my service fails when handles the data. Comparing version 2.5.1 and 3.0.1 nightly build requests there is a difference on content-length size for the same request and file attachment.

    With SopaUI 2.5.1 :

    POST /nnew/fy09/fhs/DataThresholdingService HTTP/1.1

    Accept-Encoding: gzip,deflate

    SOAPAction: "urn:Thresholding"

    Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_9_1366323247.1252965592223"

    MIME-Version: 1.0

    User-Agent: Jakarta Commons-HttpClient/3.1

    Host: weather.aero:8094

    Content-Length: 687103



    ------=_Part_9_1366323247.1252965592223

    Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"

    Content-Transfer-Encoding: 8bit

    Content-ID:







    ------=_Part_9_1366323247.1252965592223

    Content-Type: application/octet-stream

    Content-Transfer-Encoding: binary

    Content-ID: <402060121515>




    With SoapUI 3.0.1 nightly build


    POST /nnew/fy09/fhs/DataThresholdingService HTTP/1.1

    Accept-Encoding: gzip,deflate

    SOAPAction: "urn:Thresholding"

    Content-Type: multipart/related; type="application/xop+xml"; start=""; start-info="text/xml"; boundary="----=_Part_45_1981619958.1252965655025"

    MIME-Version: 1.0

    User-Agent: Jakarta Commons-HttpClient/3.1

    Host: weather.aero:8099

    Content-Length: 687157


    ------=_Part_45_1981619958.1252965655025

    Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"

    Content-Transfer-Encoding: 8bit

    Content-ID:







    ------=_Part_45_1981619958.1252965655025

    Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"

    Content-Transfer-Encoding: 8bit

    Content-ID:



    Thanks,

    -Marcel
  • Hi,
    I am using SoapUI Pro 3.0.1 and facing a similar issue.
    My Scenario: Send soap request which is MTOM enabled with WS-Security for Signature and Encryption.

    When I send the MTOM enabled request with WS-Security for Encryption, then following soap fault is received in the soap response:-

    MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of the 'type' parameter  of the 'Content-Type' header of the MIME message is not equal to 'application/xop+xml'

    On debugging, I found that the soap request that is sent by SoapUI contains the Content-Type as "application/soap+xml"

    This content Type should have been "application/xop+xml" for MTOM enabled soap request.

    Please refer to the below excerpts from the request sent bu SoapUI: -

    ------=_Part_41_25519477.1262942422094
    Content-Type: application/soap+xml; charset=UTF-8
    Content-Transfer-Encoding: 8bit
    Content-ID:


    Please provide your feedback on this issue.

    Thanks,
    Vaibhav
  • Hi Ole,
    I have installed the latest nightly build (soapUI 3.0.2) and still found the same issue regarding the content type shown in soap Request:

    ------=_Part_0_13591483.1263555168940
    Content-Type: application/soap+xml; charset=UTF-8
    Content-Transfer-Encoding: 8bit
    Content-ID:

    Regards,
    Vaibhav
  • Thanks, I'll have a look into this.. there might be differences here in how different environments expect this to be (ie .NET vs not .Net)..

    I'll let you know..

    regards,

    /Ole
    eviware.com