Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Noted the fact that Fossil 2.9+ remembers the HTTPS URI in sync when accessed via an HTTP to HTTPS redirect. |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
6b472ae172549d3fa5759ff728ef5f68 |
User & Date: | wyoung 2020-11-16 02:48:22 |
Context
2020-11-18
| ||
08:01 | Moved the section on backups in the Email Alerts doc into the new backup doc, and expanded on the coverage of config backups there, since this splits the prior section. ... (check-in: 2b1c5bc8 user: wyoung tags: trunk) | |
2020-11-17
| ||
18:46 | Merge-in trunk ... (check-in: f4a75745 user: george tags: wiki-history) | |
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: 6b472ae1 user: wyoung tags: trunk) | |
02:45 | Linking to the new TLS info from the generic SSL doc ... (check-in: 08c52c35 user: wyoung tags: trunk) | |
Changes
Changes to www/ssl.wiki.
︙ | ︙ | |||
244 245 246 247 248 249 250 251 252 253 254 255 256 257 | 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 to serve the repository via both HTTP and HTTPS, it's easy to accidentally use unencrypted HTTP if you forget the all-important 's'. As of Fossil 2.8, there is a setting in the Fossil UI under Admin → Access called "Redirect to HTTPS," which is set to "Off" by default. Changing this only affects web UI access to the Fossil repository. It doesn't affect clones and syncs done via the <tt>http</tt> URI scheme. In Fossil 2.7 and earlier, there was a much weaker form of this setting affecting the <tt>/login</tt> page only. If you're using this setting, | > > > > > > | 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 | 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 to serve the repository via both HTTP and HTTPS, it's easy to accidentally use unencrypted HTTP if you forget the all-important 's'. As of Fossil 2.9, using an <tt>http://</tt> URI with <tt>fossil clone</tt> or <tt>sync</tt> on a site that forwards to HTTPS will cause Fossil to remember the secure URL. However, there's a [https://en.wikipedia.org/wiki/Trust_on_first_use | TOFU problem] with this: it's still better to use <tt>https://</tt> from the start. As of Fossil 2.8, there is a setting in the Fossil UI under Admin → Access called "Redirect to HTTPS," which is set to "Off" by default. Changing this only affects web UI access to the Fossil repository. It doesn't affect clones and syncs done via the <tt>http</tt> URI scheme. In Fossil 2.7 and earlier, there was a much weaker form of this setting affecting the <tt>/login</tt> page only. If you're using this setting, |
︙ | ︙ |