Happy that you were able to fix your issue using the workaround mentioned!
I'm not sure about the environment and never tried this using CONNECT method. If you suspect this to be a bug and if you are a licensed user, please raise a ticket here - https://support.smartbear.com/product-list/
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others, Thanks. ↓↓↓
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?
nmrao : I don't think you can see it on readyapi. I used wireshark to dump it. It's a specific http method to join https servers trough proxies.
Samy : Ok, no support of the connect method thanks ! The second wireshark dump shows exactly what happened when readyapi trying a post to an https server with a proxy, I cut the proxy response. This attempt is a failure if it was the question.
The thing is I could see the expected User-Agent as posted earlier along with screen shot and could not reproduce the problem mentioned by you i.e., neither two User-Agents nor incorrect User-Agent value. All I can see the expected only using both http and https.
Looks it is different issue, and user is using soapUI OS, not ReadyAPI. Also the earlier one was closed. Follow new thread for further communication