From 32f7307d404690a99d570854e4e43b1cf4df89d1 Mon Sep 17 00:00:00 2001 From: smcv Date: Sun, 5 Oct 2014 11:09:27 -0400 Subject: [PATCH] remaining bugs after fixing some of the easier situations --- ...cross-linking_between_content_and_CGI.mdwn | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn b/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn index 7c920f01f..c66126fd5 100644 --- a/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn +++ b/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn @@ -116,3 +116,29 @@ I've added a regression test in `t/relativity.t`. We might want to consider dropping some of it or skipping it unless a special environment variable is set once this is all working, since it's a bit slow. --[[smcv]] + +# Remaining bugs + +## Definitely a bug + +* Configure url: "http://example.com/wiki/", + cgiurl: "https://example.com/cgi-bin/ikiwiki.cgi" and access the + CGI via https://example.com (the "NetBSD wiki" use-case). + The static content should be loaded from https://example.com + to avoid mixed-content, but it is loaded from http://example.com. + +* Put IkiWiki behind a reverse-proxy so the web server tells the CGI + that it is being accessed via http://localhost or http://127.0.0.1 + or something. Links should not point to http://localhost. + +## Arguable + +* Configure the url and cgiurl to both be https, then access the + CGI via a non-https address. The stylesheet is loaded from the http + version of the static site, but maybe it should be forced to https? + +* Configure url = "http://static.example.com/", + cgiurl = "http://cgi.example.com/ikiwiki.cgi" and access the + CGI via staging.example.net. Self-referential links to the + CGI point to cgi.example.com, but maybe they should point to + staging.example.net? -- 2.39.2