From 5c9822f948e4da1337c52a1177757a8b6147408f Mon Sep 17 00:00:00 2001
From: smcv <smcv@web>
Date: Sun, 5 Oct 2014 18:54:07 -0400
Subject: [PATCH] Added a comment

---
 ..._6_e61899aa5ad8798b864dc295102e44f7._comment | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 doc/forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https/comment_6_e61899aa5ad8798b864dc295102e44f7._comment

diff --git a/doc/forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https/comment_6_e61899aa5ad8798b864dc295102e44f7._comment b/doc/forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https/comment_6_e61899aa5ad8798b864dc295102e44f7._comment
new file mode 100644
index 000000000..ba1896d27
--- /dev/null
+++ b/doc/forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https/comment_6_e61899aa5ad8798b864dc295102e44f7._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="smcv"
+ ip="81.100.115.242"
+ subject="comment 6"
+ date="2014-10-05T22:54:06Z"
+ content="""
+> One way to solve this would be a new `$config{hard_code_urls}` option
+
+I have added basically this in git master. It isn't in a release yet,
+and I renamed it to `$config{reverse_proxy}`.
+
+Also in git master, if `$config{html5} = 1` then the `<base>` URL
+will usually be host-relative or protocol-relative (`/wiki/` or
+`//example.com/wiki/`) which reduces the need for that option.
+
+These are still subject to change, for now.
+"""]]
-- 
2.39.5