title: How to enable crypto.subtle for unsecure origins in Chrome?
body: <p>In Chrome 60, they added a <em>feature</em> that disables <code>crypto.subtle</code> for non-TLS connections. Our product needs to run a local server and forward some secure remote connections to <code>localhost</code> for security reasons. Because <code>localhost</code> isn't technically a named domain, we cannot use TLS--effectively making <code>crypto.subtle</code> unusable in Chrome (and chromium-based browsers like Opera), and forcing us to use a less secure shim like <em>asmCrypto.js</em>. Is there any way to tell Chrome to enable <code>crypto.subtle</code> through headers? Is there any way to disable the new <em>feature</em> in the settings that we can tell users about (worst case scenario)?</p>