Forum Discussion

magnusep's avatar
magnusep
New Contributor
12 years ago

HTTP Monitor over SSL?

HTTP Monitor over HTTP works without issues, I see my requests being captured. But I can't seem to get HTTPS (testing against https://www.google.com) working - my browser just freezes. Any ideas on how I should configure soapUI to get this working?

EDIT: I should note that if I do proxying via Fiddler Im not seeing any issues with HTTPS requests.
  • magnusep's avatar
    magnusep
    New Contributor
    12 years ago
    Im monitoring for the purpose of recording HTTP requests, more or less like whats on http://www.soapui.org/SOAP-Recording/re ... affic.html, just not SOAP.

    No credentials or nothing of the sort is in use. Im issuing a GET request from the browser (works for http) but when switching over to HTTPS no traffic pops up in the monitoring window and the browser seems to just idle (probably waiting for a SSL handshake?).
  • magnusep's avatar
    magnusep
    New Contributor
    12 years ago
    I dont think there is an certificate that needs accepting since Im trying to proxy requests to https://www.google.com ... in the long run, yes, there are certificates that I need to add to a truststore but just as a proof of concept Im testing with a known site.

    Any input from SmartBear?
  • djangofan's avatar
    djangofan
    Contributor
    12 years ago
    I don't know if SoapUI does it but I have traced SSL packets before using Wireshark by loading your private key (not just the public key) into Wireshark and it will decrypt on the fly during the trace. So, if you have no other recourse, you could probably do it that way. Of course, you wont have a private key for Google. This method only works if you have physical access to the private key as well as the private key password I think.