]> sipb.mit.edu Git - ikiwiki.git/blob - doc/forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https/comment_1_ef4be9e70bd6d8c970fd8982f525d2d0._comment
Merge branch 'ready/trail-sort'
[ikiwiki.git] / doc / forum / Using_reverse_proxy__59___base_URL_is_http_instead_of_https / comment_1_ef4be9e70bd6d8c970fd8982f525d2d0._comment
1 [[!comment format=mdwn
2  username="http://smcv.pseudorandom.co.uk/"
3  nickname="smcv"
4  subject="comment 1"
5  date="2013-12-20T09:54:51Z"
6  content="""
7 One way to solve this would be a new `$config{hard_code_urls}`
8 option whose semantics are \"you're behind a reverse proxy, hard-code
9 `$config{cgiurl}` and `${url}` in output rather than using the
10 address from the HTTP request\" (in other words, selectively undo some
11 of the automatic self-referential URL detection).
12
13 Another possibility would be to avoid using `<base>`, and when producing
14 CGI pages, make all links look like `/sandbox/` or
15 `/cgi-bin/ikiwiki.cgi?...`; but that can only work if your content and
16 CGI are on the same domain, and is likely to be more complex.
17
18 The `<base href>` is required to be an absolute URI (including the
19 protocol and domain name) so the CGI output can't avoid doing a certain
20 amount of hard-coding, unfortunately.
21 """]]