> For WebRTC, browsers could block local addresses.
That would defeat a huge selling point of WebRTC, the ability to create in-browser p2p connections over the user's local network.
That would defeat a huge selling point of WebRTC, the ability to create in-browser p2p connections over the user's local network.
You'd want to use it any time you want a high-speed network connection with another user. For example, a multiplayer game or video teleconference.
Others have pointed out this behavior has changed in Chrome 48. You don't get the local IP unless the page asks for access to the mic/camera which the user has to give permission for.