2 ms·

Sadly a lot of browser features are inaccessible from non-https contexts.

• jsheard 10mo ago
  Don't most (all?) browsers consider file:// and localhost to be secure for the sake of enabling those features? https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Secure_Contexts#potentially_trustworthy_origins https://developer.mozilla.org/en-US/docs/Web/Security/Defens...
  • mlok 10mo ago
    Unfortunately, no. CORS will block this on Chrome and Firefox. https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors/CORSRequestNotHttp https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/COR... The security risk : https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730 https://www.mozilla.org/en-US/security/advisories/mfsa2019-2... You need a local webserver. Or bundle everything in one html file.
    • deleted 10mo ago
      [deleted]
    • deleted 10mo ago
      [deleted]
    • Am4TIfIsER0ppos 10mo ago
      So that's why I have to keep booting a Windows 7 computer in order to use an html file I saved 10+ years ago? Some dumb shit android app.
• gabriela_c 10mo ago
  or you could use something like caddy (https reverse-proxy, local cert), and have a dedicated ws running in the background that serves your files