3 ms·
(Update) Ok, so apparently there is a security exception: "localhost" is blocked but "127.0.0.1" is treated as a secure origin [1] - but only if you cantact it
by xg15 9y ago
(Update)
Ok, so apparently there is a security exception: "localhost" is blocked but "127.0.0.1" is treated as a secure origin [1] - but only if you cantact it via http, not via websocket. (though they might allow websocket in the future too) [2]
(A related chrome bug even specifically mentions the "people installing local root certs" workaround as a reason they are doing this. [3])
This still seems like an enormous mess but it's good to see the use-case is acknowledged and someone at Mozilla cares about it.
So I guess Blizzard could have avoided the whole scare if they had just used "127.0.0.1" instead of "localbattle.net"
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=903966 https://bugzilla.mozilla.org/show_bug.cgi?id=903966
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1376309 https://bugzilla.mozilla.org/show_bug.cgi?id=1376309
[3] https://chromium.googlesource.com/chromium/src.git/+/130ee686fa00b617bfc001ceb3bb49782da2cb4e https://chromium.googlesource.com/chromium/src.git/+/130ee68...