Fossil SCM
Added some named anchors to www/server/any/stunnel.md
Commit
ce4b4bae311ac87026f7efa4ec5de9c763dda09a0b8bd3350ae9fb352c114cc3
Parent
53b2e866e1632ad…
1 file changed
+2
-2
+2
-2
| --- www/server/any/stunnel.md | ||
| +++ www/server/any/stunnel.md | ||
| @@ -10,11 +10,11 @@ | ||
| 10 | 10 | You can run `stunnel` in one of two modes: socket activation — much like |
| 11 | 11 | in our [`inetd` doc](./inetd.md) — and as an HTTP reverse proxy. We’ll |
| 12 | 12 | cover both cases here, separately. |
| 13 | 13 | |
| 14 | 14 | |
| 15 | -## Socket Activation | |
| 15 | +## S<a name="sa"></a>ocket Activation | |
| 16 | 16 | |
| 17 | 17 | The following `stunnel.conf` configuration configures it to run Fossil |
| 18 | 18 | in socket activation mode, launching Fossil only when an HTTPS hit comes |
| 19 | 19 | in, then shutting it back down as soon as the transaction is complete: |
| 20 | 20 | |
| @@ -47,11 +47,11 @@ | ||
| 47 | 47 | configuration include the `--https` option to let Fossil know to use |
| 48 | 48 | “`https://`” instead of “`http://`” in generated hyperlinks. |
| 49 | 49 | |
| 50 | 50 | |
| 51 | 51 | |
| 52 | -## Reverse Proxy | |
| 52 | +## <a name="proxy"></a>Reverse Proxy | |
| 53 | 53 | |
| 54 | 54 | You can instead have Fossil running in the background in [standalone |
| 55 | 55 | HTTP server mode](./none.md), bound to a high random TCP port number on |
| 56 | 56 | localhost via the `--localhost` and `--port` flags, then configure |
| 57 | 57 | `stunnel` to reverse proxy public HTTPS connections down to it via HTTP. |
| 58 | 58 |
| --- www/server/any/stunnel.md | |
| +++ www/server/any/stunnel.md | |
| @@ -10,11 +10,11 @@ | |
| 10 | You can run `stunnel` in one of two modes: socket activation — much like |
| 11 | in our [`inetd` doc](./inetd.md) — and as an HTTP reverse proxy. We’ll |
| 12 | cover both cases here, separately. |
| 13 | |
| 14 | |
| 15 | ## Socket Activation |
| 16 | |
| 17 | The following `stunnel.conf` configuration configures it to run Fossil |
| 18 | in socket activation mode, launching Fossil only when an HTTPS hit comes |
| 19 | in, then shutting it back down as soon as the transaction is complete: |
| 20 | |
| @@ -47,11 +47,11 @@ | |
| 47 | configuration include the `--https` option to let Fossil know to use |
| 48 | “`https://`” instead of “`http://`” in generated hyperlinks. |
| 49 | |
| 50 | |
| 51 | |
| 52 | ## Reverse Proxy |
| 53 | |
| 54 | You can instead have Fossil running in the background in [standalone |
| 55 | HTTP server mode](./none.md), bound to a high random TCP port number on |
| 56 | localhost via the `--localhost` and `--port` flags, then configure |
| 57 | `stunnel` to reverse proxy public HTTPS connections down to it via HTTP. |
| 58 |
| --- www/server/any/stunnel.md | |
| +++ www/server/any/stunnel.md | |
| @@ -10,11 +10,11 @@ | |
| 10 | You can run `stunnel` in one of two modes: socket activation — much like |
| 11 | in our [`inetd` doc](./inetd.md) — and as an HTTP reverse proxy. We’ll |
| 12 | cover both cases here, separately. |
| 13 | |
| 14 | |
| 15 | ## S<a name="sa"></a>ocket Activation |
| 16 | |
| 17 | The following `stunnel.conf` configuration configures it to run Fossil |
| 18 | in socket activation mode, launching Fossil only when an HTTPS hit comes |
| 19 | in, then shutting it back down as soon as the transaction is complete: |
| 20 | |
| @@ -47,11 +47,11 @@ | |
| 47 | configuration include the `--https` option to let Fossil know to use |
| 48 | “`https://`” instead of “`http://`” in generated hyperlinks. |
| 49 | |
| 50 | |
| 51 | |
| 52 | ## <a name="proxy"></a>Reverse Proxy |
| 53 | |
| 54 | You can instead have Fossil running in the background in [standalone |
| 55 | HTTP server mode](./none.md), bound to a high random TCP port number on |
| 56 | localhost via the `--localhost` and `--port` flags, then configure |
| 57 | `stunnel` to reverse proxy public HTTPS connections down to it via HTTP. |
| 58 |