You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Noctua-in-AWS runs as both HTTP and HTTPS (initial intentions).
We now understand a little more about how this will have to work practically and want to ensure that the apache proxies do HTTPS-only, with HTTP forwarding to appropriate scheme (as is usual for most sites).
The text was updated successfully, but these errors were encountered:
It looks like @mugitty has gotten most of them, but I just noticed that http://3.226.81.154/ at barista runs in the clear. We'll need to clear this one up too.
Currently, Noctua-in-AWS runs as both HTTP and HTTPS (initial intentions).
We now understand a little more about how this will have to work practically and want to ensure that the apache proxies do HTTPS-only, with HTTP forwarding to appropriate scheme (as is usual for most sites).
The text was updated successfully, but these errors were encountered: