4 ms·
Browsers deal with this by considering localhost a "secure context", and anything that "requires https" actually requires a secure context. [1] You can debug ne
by jefftk 3y ago
Browsers deal with this by considering localhost a "secure context", and anything that "requires https" actually requires a secure context. [1] You can debug new web features like the Audio Output API that require a secure context [2] with http://localhost http://localhost urls, and use multiple ports if you need multiple hosts. ActivityPub could do this too.
[1] https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts https://developer.mozilla.org/en-US/docs/Web/Security/Secure...
[2] https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts https://developer.mozilla.org/en-US/docs/Web/Security/Secure...
- pimterry 3y ago> Browsers deal with this by considering localhost a "secure context" Broadly yes, except Safari which still sometimes doesn't: https://bugs.webkit.org/show_bug.cgi?id=171934 https://bugs.webkit.org/show_bug.cgi?id=171934 (Not relevant to this case, but eugh it's a very annoying exception)
- jefftk 3y agoYes, that's not great. But at least it doesn't bite you if you're running an all-localhost dev environment.