Chrome will limit access to private networks, citing security reasons
therecord.media
therecord.media
- segregated Enterprise Network
- Home Network with custom subnetting for kid-friendly use.
- get blocked from configuring WiFi access points
- Unable to distinguish between a client on Internal versus the same client homed in via a tunnel.
That’s just the beginning of various use cases.
Although, it is trying to shift the onus to the interior server(s) to do the selective acceptance, it is not the way to go for enterprise network.
- Somehow, I get the feeling that such a button will be foisted using chrome:// or made accessible using JavaScript … by the Chrome development team.
My understanding is that this will only stop public web pages from making requests to private servers via scripts, iframes, images, etc.
It won't prevent you from opening a private web page in a browser.
It won't prevent a private web page from talking to another private server either.
So there is nothing here keeping you from opening your router's admin page in Chrome - however, it will stop some script at evil.com from spoofing requests of that admin page.
Why waste time with all that; just provide a static button on browser for private uses and be done with.
With the current update, 99% of private sites will keep working as before, while some people who fall into the edge cases will have to add a header.
With your proposal, you'd have to jump through UI hoops to view any site in a local network, wouldn't you?