2 ms·

Not just to localhost, but to most of the IANA reserved space, including 192.168.0.0/16 and 10.0.0.0/8: http://code.metager.de/source/xref/chromium/net/base/ne

• easytiger 12y ago
  How the hell do you access your router's admin page then?
  • jorangreef 12y ago
    That will still be possible. The issue is about blocking access to secure websocket on localhost from public web pages. Routers don't generally use websocket, and if they do, probably not secure websocket.
  • detaro 12y ago
    By going there directly. It is only about sub-ressources in pages (so if you go to badsite.com it can't trigger a request to your router, which given the security track record of your average home router is a good thing)
  • wwarren 12y ago
    Seems like it only limits OTHER sites/pages from being able to access localhost or 192.168.x.x I think you'll still be able to access those pages directly yourself
    • easytiger 12y ago
      thanks, misunderstood