Start chrome.exe -host-rules="MAP * 127.0.0.1, EXCLUDE 66.227.46.190:443"Then, we'd save it as something like ChromeWSF.bat One thing you must never forget, is that, there's a pretty good chance that whatever service you'll access has more than one domain/sub-domains.Īnother thing to consider, is that, when using -host-rules, will not match, and vice-verse.Įither method you use, you'll have to find out which domains you'll have to off Rules are separated by commas, as you can see the example I gave for WSF. If WSF had any other sub-domains, then I could either add an additional rule or write *. instead. This profile can only connect to WSF, respective IP address and port 443. In the above example, I am mapping everything to localhost (127.0.0.1), which will make the connections fail, with an exception for To make it stricter, I've also mapped to its IP address and remote port 443 (which is for https). "C:\Program Files\Google Chrome\chrome.exe" -host-rules="MAP * 127.0.0.1, EXCLUDE 66.227.46.190:443" (the domain is together, but I had to separate it, otherwise it would transform it in an URL) You'd get a few example on how to achieve that goal.īut, I'll give a quick example with Wilderssecurity forum. Click to expand.Sorry, I forgot to mention you could search the forum for my nickname and host-rules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |