SSL issues on Fedora 18 and Windows about wiremock

[tomakehurst]

I get the same result as you do, and there's nothing wrong with your configuration as far as I can tell, so I'll investigate.

[yogurtearl]

Are you running on Java 7? I have run into SSL exceptions running on Java 7
on a mac, but it worked fine on Java 6.

I get the same result as you do, and there's nothing wrong with your
configuration as far as I can tell, so I'll investigate.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/62#issuecomment-26727481
.

[rossillingworth]

No, I get the same exception in 1.6.0.45 or 1.7.0.17

[tomakehurst]

I'm also seeing it with both versions.

[tomakehurst]

I've just realised that what you're trying to do isn't possible when using WireMock as a forward (i.e. browser) proxy for HTTPS. The reason is that HTTPS proxies don't attempt to decrypt the exchange, but make a CONNECT request to the destination and effectively become TCP tunnels. Although WireMock could be set up to mimic this behaviour, it'd be pointless because it couldn't read the (encrypted) request and hence map it to a suitable response.

[rossillingworth]

Sorry, I should have explained. I was simply using the browser as a test tool.

I am evaluating proxies for automation testing, but most of our traffic is SSL. Mostly I just want to inject 500s or 404s into the traffic SSL flow at controlled points, sometimes I will need more complex response modification, so I was looking for something extendable, ie: java.

I believe Wiremock is an SSL MITM capable debugging proxy that I can extend.

I believe I understand correctly that Wiremock does generate it's own certificates, and so can modify HTTPS response on the fly?
NB: I am quite happy adding a CA cert to the trusted list.

Does --enable-browser-proxying activate TCP tunneling rather than interception?

My apologies for the confusion, but I have been so busy evaluating everything out there that I had no time to read as much of the source code as I would like.

PS: just an FYI, did you know your proxy project is one of the very few that actually compiles out of the box.

[tomakehurst]

Any http client (browser or otherwise) will try to use CONNECT when requesting a page via a forward proxy, which is what WireMock is acting as with --enable-browser-proxying. Therefore the conversion will always stay encrypted and be unmodifyable.

However, configuring wiremock as a reverse proxy (either by setting the --proxy-all= param or adding a proxy stub mapping) will allow you to replace specific responses by adding stub mappings at higher priorities. The only catch is that you will need to point your browser directly at wiremock I.e. no proxy settings.