Why doesn't my Web Api proxy receive https requests when set as browser proxy, but can normally?

Asked Jan 31 '13 at 17:48

Active Feb 01 '13 at 15:41

Viewed 400 times

I have written a http proxy using WebApi.

I have it registered on port 4443, and if I enter https://localhost:4443 into a browser, and set a breakpoint in my DelegatingHandler, it will be hit (and I get an SSL warning).

If I then set it to be the firefox proxy (see image), for SSL requests, and browse to https://somesite.com it is not hit - Web Api appears not to handle the call at all.

enter image description here

What is the browser doing differently when it uses a proxy as opposed to when it makes direct calls that causes Web Api to not handle the call?

edited Feb 01 '13 at 15:41

asked Jan 31 '13 at 17:48

mcintyre321

12,996
8
66
103

Did you mean to say 4443? https uses 443 by default. – Darrel Miller Jan 31 '13 at 19:05
443 is used for my IIS installation, I'm trying to create a browser proxy. – mcintyre321 Feb 01 '13 at 15:39
Ahh, didn't realize you had changed the port on the SSL proxy too. I don't see any reason why this is not working. – Darrel Miller Feb 01 '13 at 15:51

Why doesn't my Web Api proxy receive https requests when set as browser proxy, but can normally?

0 Answers0