HTTP can work if your "local" means strictly "on localhost domain". These days local can also mean that you are running a VM and accessing something that's runn

HTTP can work if your "local" means strictly "on localhost domain". These days local can also mean that you are running a VM and accessing something that's running there (docker-machine for example). In that case you wouldn't be able to use localhost very trivially (you can do port forwarding, but that's pretty annoying). So you then need to access non-localhost domain for local stuff and browsers don't like this. https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-powerful-features-on-insecure-origins https://sites.google.com/a/chromium.org/dev/Home/chromium-se...