Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Linking to the new TLS info from the generic SSL doc |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
08c52c35bada38803b45ef6ed89d23c4 |
| User & Date: | wyoung 2020-11-16 02:45:04.838 |
Context
|
2020-11-16
| ||
| 02:48 | Noted the fact that Fossil 2.9+ remembers the HTTPS URI in sync when accessed via an HTTP to HTTPS redirect. ... (check-in: 6b472ae172 user: wyoung tags: trunk) | |
| 02:45 | Linking to the new TLS info from the generic SSL doc ... (check-in: 08c52c35ba user: wyoung tags: trunk) | |
| 02:42 | Small tweaks to the Debian nginx doc. ... (check-in: 14406b7ca2 user: wyoung tags: trunk) | |
Changes
Changes to www/ssl.wiki.
| ︙ | ︙ | |||
233 234 235 236 237 238 239 | Fossil to OpenSSL. To serve a Fossil repository via HTTPS, you must put it behind some kind of HTTPS proxy. We have a number of documents elsewhere in this repository that cover your options for [./server/ | serving Fossil repositories]. A few of the most useful of these are: * <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a> * <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a> | | | 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 | Fossil to OpenSSL. To serve a Fossil repository via HTTPS, you must put it behind some kind of HTTPS proxy. We have a number of documents elsewhere in this repository that cover your options for [./server/ | serving Fossil repositories]. A few of the most useful of these are: * <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a> * <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a> * <a id="nginx" href="./server/debian/nginx.md#tls">Serving via SCGI with nginx on Debian</a> <h2 id="enforcing">Enforcing TLS Access</h2> To use TLS encryption in cloning and syncing to a remote Fossil repository, be sure to use the <tt>https:</tt> URI scheme in <tt>clone</tt> and <tt>sync</tt> commands. If your server is configured |
| ︙ | ︙ |