Forum Discussion

bpcemat's avatar
bpcemat
Occasional Contributor
10 years ago

User-Agent issue with SoapUI NG (trial)

Hi,   A have an issue setting the user-agent in my soap requests with SoapUI (5.2.1) then I tried to use Ready!/SoapUI NG (1.4.1), but the problem is identical (http://community.smartbear.com/t5/So...
  • kondasamy's avatar
    kondasamy
    10 years ago

    Agree! Ready! API doesn't support CONNECT method at all!

     

     bpcemat: In the screenshots shared, I hope the wireshark dump of second instance is a mismatched one. Is it?

     

    Thanks,

    Samy

nmrao's avatar
nmrao
Champion Level 3
10 years ago

See if this helps.

go to File -> Preferences -> Http Settings -> User-Agent Header, provide value.

 

preferences.png

  • bpcemat's avatar
    bpcemat
    Occasional Contributor
    10 years ago

    :( I allready tried that. It is why I've got 2 User-Agent header in my raw data.

    I suppose SoapUI does not remove de default User-Agent of the Apache Library and erase my own settings when generating requests.

     

    Thanks.

    • nmrao's avatar
      nmrao
      Champion Level 3
      10 years ago

      Some how I could see what I have as user-agent value in preferences, Tried on  SoapUI 4.x, 5.x

       

      POST http://10.0.0.1:8080/eml/services/router HTTP/1.1
Connection: close
Accept-Encoding: gzip,deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
Content-Type: text/xml;charset=UTF-8
SOAPAction: "RecordAction"
Authorization: Basic YWRtaW46YWRtaW4=
Content-Length: 6491
Host: 10.0.0.1:8080

      Could not reproduce, somehow. Could not try on ReadyAPI though.

      This is for soap request only.

      • bpcemat's avatar
        bpcemat
        Occasional Contributor
        10 years ago

        Thanks for your test, you gave me an idea, I'm progressing.

         

         

        I'm in an enterprise network and use a proxy to connect soap sites. My problem occurs when SoapUI orders the proxy to connect an SLL soap server. The CONNECT request does not have the defined User-Agent (and that's my problem), maybe the soap requests inside the SSL tunnel will have it but i can't tell.

         

        I'm looking for a work-around, but I'm not optimistic.

         

         

        Best regards.