Proxomitron Reborn

[mizzmona]

(Apr. 26, 2019 02:47 AM)whenever Wrote:  

(Apr. 25, 2019 12:14 PM)amy Wrote:  You asked it to bypass connections matching the host 'local.ptron:443', so it does exactly as you asked and you get the same result as trying to visit https://local.ptron in a browser without Proxomitron, i.e. it will attempt to resolve the hostname and connect to port 443. It's behaving like a bypass should, so I would not consider it to be a bug.

I wouldn't disagree but isn't local.ptron a special hostname to Proxomitron?

Well, there seems to be some confusion here. Certainly, local.ptron is a special hostname, but the point is that the Bypass list isn't a blocklist to kill connections, it's a list to deactivate filtering. These are two different things. Local.ptron should still be accessible if included on the Bypass list, just as it should be accessible when the Proxomitron itself is placed in bypass mode.

I'm dying to find some solid time to play with this new version myself, though. Whenever, you lucky dog...

Thank you, amy! This is just sooo awesome.