mirror of
https://github.com/ilyakooo0/urbit.git
synced 2024-11-28 19:55:53 +03:00
27349c51ab
if a cert is configured and a secure port is live it will set the redirect flag in http-config.state. When it gets a ++request it will return a 301 redirect to https://[host]/[path] if: 1. not already secure 2. redirect flag set 3. secure port live 4. is not requesting /.well-known/acme-challenge/... 5. the host is in domains.state It will not happen if forwarded-secured, localhost, local loopback, ip addresses or domains not in domains.state. in ++load it checks the secure port is live and a cert is set and enables it if so (for people who already use in-urbit letencrypt) %rule %cert tasks also toggle it (only turning it on if secure port live) %live tasks also toggle it (only turning it on if cert set) Have tested with a couple of ships and seems to work fine. This is useful in combination with pyry's auto arvo.network dns config system - can finally get rid of reverse proxies entirely. |
||
|---|---|---|
| .. | ||
| arvo | ||
| base-dev | ||
| bitcoin | ||
| btc-wallet | ||
| docker-image | ||
| ent | ||
| garden | ||
| garden-dev | ||
| grid | ||
| herb | ||
| hs | ||
| interface | ||
| landscape | ||
| npm | ||
| urbit | ||
| urcrypt | ||
| webterm | ||
| symbolic-merge.sh | ||