Closed antonio-gil closed 6 years ago
I forgot to mention:
This is because, as far as I've experienced, having the 'localhost' blocked affects to locally deployed web-servers, including the IIS Express used in Visual Studio (where I first noticed such behavior), and the native (included?) Python web-server.
Also this is meant to only affects to the "localhost" entry and not the "localhost(dot)something" entries, to avoid some unwanted unblocking (in my tests this worked as intended, but if you found any improvement on the implementation, that could be great).
Regards.
Hey there! Sorry for my totally delayed reply, I'm travelling right now till mid January, that's why I didn't check my mails at all.
I'll have a look to your suggestion by mid January when I'm back home, ok?
When "localhost" is added to the whitelist it will be handled properly by the patching process. This because as being a "one word address" its overlooked by the normal process and therefore isn't patched.
(This doesn't apply to localhost.localdomain)