Forum Discussion

bpcemat's avatar
bpcemat
Occasional Contributor
9 years ago
Solved

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/SoapUI-Open-Source/User-Agent-option-issue/m-p/108121#U108121). Setting User-Agent in the global options or adding an header property in the soap request does not change behaviour.

 

Here are the raw header in SoapUI NG when i want to change User-Agent :

POST https://xxx.xxx.xxx/Authentification HTTP/1.1
Accept-Encoding: gzip,deflate
User-Agent: SoapUI-metier
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
Host: xxx.xxx.xxx

Proxy-Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

 

And here a network dump of the headers :

CONNECT xxx.xxx.xxx:443 HTTP/1.1

Host: xxx.xxx.xxx

Proxy-Connection: Keep-Alive

User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

 

Is there any work-around to get the user-agent option working ?

 

Thanks.

Mathieu.

  • 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

17 Replies

  • nmrao's avatar
    nmrao
    Champion Level 3

    See if this helps.

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

     

    preferences.png

    • bpcemat's avatar
      bpcemat
      Occasional Contributor

      :( 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

        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.