oh, we don't use comments here, do we?

[git.ikiwiki.info.git] / doc / todo / design_for_cross-linking_between_content_and_CGI.mdwn

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 c66126fd5f4b02de80a2d2ce2254e1246f884241..d8040bf3e31e18ba7e4961e9d0b0838cfbeb8981 100644 (file)
--- a/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn
+++ b/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn
@@ -119,18 +119,6 @@ variable is set once this is all working, since it's a bit slow.
 
 # 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
@@ -142,3 +130,5 @@ variable is set once this is all working, since it's a bit slow.
   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?
+
+* *(possibly incomplete, look for TODO and ??? in relativity.t)*