X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/15222d87254f48db7943b065b96ae3e626090ef0..2d90e4ede4da06adc38fbf704b6bb29a76c75575:/doc/bugs/relative_links.mdwn?ds=inline

diff --git a/doc/bugs/relative_links.mdwn b/doc/bugs/relative_links.mdwn
index 824632ed0..8e6556fda 100644
--- a/doc/bugs/relative_links.mdwn
+++ b/doc/bugs/relative_links.mdwn
@@ -14,3 +14,9 @@ It would be good if relative paths could be used instead, so the transport metho
 
 >> The problem is within the CGI script. The links within the HTML page are all absolute, including links to the css file.
 >> Having a http links within a HTML page retrieved using https upset most browsers (I think). Also if I push cancel on the edit page in https, I end up at at http page. -- Brian May
+
+>>> Ikiwiki does not hardcode http links anywhere. If you don't want
+>>> it to use such links, change your configuration to use https
+>>> consistently. --[[Joey]]
+
+Errr... That is not a solution, that is a work around. ikiwiki does not hard code the absolute paths, but absolute paths are hard coded in the configuration file. If you want to serve your website so that the majority of users can see it as http, including in rss feeds (this allows proxy caches to cache the contents and has reduced load requirements), but editing is done via https for increased security, it is not possible. I have some ideas how this can be implemented (as ikiwiki has the absolute path to the CGI script and the absolute path to the destination, it should be possible to generate a relative path from one to the other), although some minor issues still need to be resolved.