permacomputing

commit 2cbdc63b094c1c9d414321081a3d1a1f2c94abe7
parent ec9418f3159308710a9ec67514ed72d26a241871
Author: ugrnm <ugrnm@web>
Date:   Tue, 10 Sep 2024 18:08:43 +0200

empty web commit

Diffstat:
M
eik.mdwn
 | 
6
++++++

1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/eik.mdwn b/eik.mdwn
@@ -8,6 +8,12 @@ We leave the visitor the option to `http` or `https`. This is done in `nginx` wi
     listen 80;
     listen 443 ssl;
 
+However when authentication is required we force `https` like this:
+
+    location /supercoolauth.cgi {
+        return 301 https://$http_host$request_uri;
+    }
+
 We use `acme.sh` for handling certs, however expanding certs with new domain is still not supported. The workaround is to recreate a whole new cert with all the domains. For instance:
 
     acme.sh --issue --nginx \