Forum Discussion

Rishabhwal's avatar
Rishabhwal
Occasional Contributor
7 years ago

Soap UI Pro sends a URL with Junk values

Hi All,

 

I have a request XML defined but when I try to execute it, the tool adds "{}" and "/" to url in action tag (highlighted in bold below). Due to this I am getting error in response. I have also attached the settings of the project.

Version: 5.1.2, cant update it due to restrictions org wise.

 

Req XML:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:vh="http://XXXX/soap/header/v-header-v1-8.xsd" xmlns:evt="http://XXXX/soap/header/ev-test-header-v1-1.xsd">
<soapenv:Header>
<wsse:Security>
<wsse:UsernameToken>
<wsse:Username>ABC</wsse:Username>
<wsse:Password>XYZ</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<wsa:To>URL</wsa:To>
<wsa:MessageID>urn:123456</wsa:MessageID>
<vh:MemberCode>ABCD</vh:MemberCode>
<vh:BranchCode>1234</vh:BranchCode>
<wsa:Action>http://HOST/Verify</wsa:Action></soapenv:Header>

 

On execution the request changes to:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:vh="http://XXXX/soap/header/v-header-v1-8.xsd" xmlns:evt="http://XXXX/soap/header/ev-test-header-v1-1.xsd">

<soapenv:Header>

<wsse:Security>

<wsse:UsernameToken>

<wsse:Username>ABC</wsse:Username>

<wsse:Password>XYZ</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

<wsa:To>URL</wsa:To>

<wsa:MessageID>urn:123456</wsa:MessageID>

<vh:MemberCode>ABCD</vh:MemberCode>

<vh:BranchCode>1234</vh:BranchCode>

<wsa:Action>{http://schemas.xmlsoap.org/wsdl/http/}//HOST/Verify

  • Rishabhwal's avatar
    Rishabhwal
    7 years ago

    This has been resolved by setting the "WS-Addressing" property to False.

  • Rishabhwal's avatar
    Rishabhwal
    Occasional Contributor
    7 years ago

    This has been resolved by setting the "WS-Addressing" property to False.

    • Rishabhwal's avatar
      Rishabhwal
      Occasional Contributor
      7 years ago

      Radford:Yes I just tried that but no luck. Although the action was also sent as part of header earlier which now isnt, but Action URL is still part of request body.

       

      I even tried to delete the action url but then too it was sent as part of request.

    • Rishabhwal's avatar
      Rishabhwal
      Occasional Contributor
      7 years ago
      Radford wrote:

      The following documentation:

       

      https://support.smartbear.com/readyapi/docs/projects/ui/request-properties/soap.html

       

      with regard to the "Skip SOAP Action" property states "If true, excludes the action value from the request header". From your screenshot it looks like it's available in you rather old version of SOAP UI Pro, have you tried setting this property?

       

       

       


      Radford:Yes I just tried that but no luck. Although the action was also sent as part of header earlier which now isnt, but Action URL is still part of request body.

       

      I even tried to delete the action url but then too it was sent as part of request.

  • richie's avatar
    richie
    Community Hero
    7 years ago

    Hi Rishabhwal

     

    Probably a stupid question - but are you sure you haven't paramaterised the contents of your <wsa:Action> tag in some way?

     

    can you post the 'Raw', 'Form' and 'Outline' tabs of both your request and response?  Just want to confirm the contents of the tag is not dynamic.

     

    I've seen namespace proliferation before when the tag value was blank, so the xml parser populates the value with the relevant namespace pointer or adds in the namespace pointer as an attribute of the tag - but the value populated isn't even the correct namespace in your example.

     

    cheers.

     

    rich

     

     

    • Rishabhwal's avatar
      Rishabhwal
      Occasional Contributor
      7 years ago

      richie: No I havent parameterised the action tag also content of the tag are not dynamic as its just a URL.

      Posting the content would be difficult as it contains sensitive data.

       

      I even tried to delete the action url but then too it was sent as part of request.

  • Rishabhwal's avatar
    Rishabhwal
    Occasional Contributor
    7 years ago

    This has been resolved by setting the "WS-Addressing" property to False.