Hi Tony,
I tried to reproduce your issue by using Fiddler as a reverse proxy for a web site dir.bg and opening it from a web browser and I succeeded. I did the following:
1. Added 127.0.0.1 dir.bg to my hosts file in C:\Windows\System32\drivers\etc
2. Added this inside the OnBeforeRequest handler:
Please, note that I do not need to bypass the gateway. If there are any proxies and firewalls in your organization they will stop Fiddler to forward the request to the server.
3. From Tools\Options HTTPS I checked the 'Ignore server certificate errors' option - this is because in the FiddlerScript we are overriding the host with an IP address and Fiddler will expect the server to authenticate with a certificate with a Subject CN = "194.145.63.12" but the server is authenticating with a Subject CN = "dir.bg"
4. Turned off the capturing to make sure that the browser will not use the proxy settings pointing to Fiddler listenning on the 8888 port.
5. Ran the command !listen 443 dir.bg
Then when I opened the website from the browser, Fiddler captured the HTTPS session. However, I have to mention that while I was testing I opened the website with Chrome without the setup and I believed that Chrome cached the IP of the site for some time because the session didn't show up. I had to use other browsers.
So maybe your node-JS app "knows" the IP of the server and does not respect the hosts file as well.
I hope I was helpful.
Regards,
Simeon
Progress Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items