As far as I understand Fiddler, it simply listens on localhost:8888 and changes the windows proxy settings to exactly that. So that every application that connects using that proxy sends the data through Fiddler.
The problem I'm having is that some applications don't care what the Windows proxy settings say and always try to connect directly.
So I was thinking.. shouldn't it be possible to just force specific processes to use a specific proxy?
And according to my research it actually seems to be possible. For example the application Proxifier claims to be able to do it.
So I installed it, created a new profile, added a new HTTPS proxy to it: "127.0.0.1:8888", added a rule for fiddler.exe to connect directly and added a global rule to force everything to connect through 127.0.0.1:8888.
But the traffic doesn't show up on my Fiddler. All that happens is that Fiddler opens lots of certificate errors like this:
And the HTTPS-requests end in NET::ERR_CERT_COMMON_NAME_INVALID.
Note that when I use Fiddler for HTTPS traffic without Proxifier, everything works just fine. In Chrome and in Firefox (even without the hook installed). So the Fiddler root certificate should be installed correctly... at least for the browsers?
So what am I doing wrong here? Any idea how to get this to work? Is there maybe alternative software? (Not to Fiddler, but to Proxifier, so please don't tell me to use Wireshark.)
