Fossil SCM

Fixed a Markdown-ism in previous

wyoung 2019-01-22 03:02 trunk
Commit 485eda766431c97e5697684306184da7ad03ef1e77dec7cee5530e1e5e5788de
1 file changed +2 -2
+2 -2
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -216,12 +216,12 @@
216216
old setting allows multiple ways of defeating it.
217217
218218
<b id="rloop">WARNING:</b> Enabling HTTPS redirects at the Fossil repo
219219
level while running Fossil behind an HTTPS proxy can result in an
220220
infinite redirect loop. It happens when the proxy mechanism presents
221
-"`http`" URIs to Fossil, so Fossil issues a redirect, so the browser
222
-fetches the page again, causing Fossil to see an "`http`" URI again, so
221
+"<tt>http</tt>" URIs to Fossil, so Fossil issues a redirect, so the browser
222
+fetches the page again, causing Fossil to see an "<tt>http</tt>" URI again, so
223223
it issues a redirect...'round and 'round it goes until the web browser
224224
detects it's in a redirect loop and gives up. This problem prevents you
225225
from getting back into the Admin UI to fix it, but there are several
226226
ways to fix it:
227227
228228
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -216,12 +216,12 @@
216 old setting allows multiple ways of defeating it.
217
218 <b id="rloop">WARNING:</b> Enabling HTTPS redirects at the Fossil repo
219 level while running Fossil behind an HTTPS proxy can result in an
220 infinite redirect loop. It happens when the proxy mechanism presents
221 "`http`" URIs to Fossil, so Fossil issues a redirect, so the browser
222 fetches the page again, causing Fossil to see an "`http`" URI again, so
223 it issues a redirect...'round and 'round it goes until the web browser
224 detects it's in a redirect loop and gives up. This problem prevents you
225 from getting back into the Admin UI to fix it, but there are several
226 ways to fix it:
227
228
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -216,12 +216,12 @@
216 old setting allows multiple ways of defeating it.
217
218 <b id="rloop">WARNING:</b> Enabling HTTPS redirects at the Fossil repo
219 level while running Fossil behind an HTTPS proxy can result in an
220 infinite redirect loop. It happens when the proxy mechanism presents
221 "<tt>http</tt>" URIs to Fossil, so Fossil issues a redirect, so the browser
222 fetches the page again, causing Fossil to see an "<tt>http</tt>" URI again, so
223 it issues a redirect...'round and 'round it goes until the web browser
224 detects it's in a redirect loop and gives up. This problem prevents you
225 from getting back into the Admin UI to fix it, but there are several
226 ways to fix it:
227
228

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button