4 ms·
> My preferred setup is to have an unencrypted service running on 127.0.0.1 (so not publicly available), Don't forget that JS from any webpage can access your
by simiones 4y ago
> My preferred setup is to have an unencrypted service running on 127.0.0.1 (so not publicly available),
Don't forget that JS from any webpage can access your 127.0.0.1 to various degrees. Depending on what types of requests exactly the server accepts, it may be somewhat unsafe for a machine with a browser.
- mort96 4y agoOh, that was for a server. So the process which serves e.g my pastebin (https://sr.ht/~mort/coffeepaste/ https://sr.ht/~mort/coffeepaste/) runs an unecrypted HTTP server on 127.0.0.1 on some high port, then an nginx reverse proxy handles HTTPS on port 443. On a machine with a browser, local servers are dangerous, HTTPS or not.