response

[ikiwiki.git] / doc / bugs / relative_links.mdwn

diff --git a/doc/bugs/relative_links.mdwn b/doc/bugs/relative_links.mdwn
index 13194737f4a6d2cb5e093ca383fbb3289a764ef7..a1dc8f3736e41041663884b0454e53d96b5e9530 100644 (file)
--- a/doc/bugs/relative_links.mdwn
+++ b/doc/bugs/relative_links.mdwn
@@ -19,4 +19,9 @@ It would be good if relative paths could be used instead, so the transport metho
 >>> it to use such links, change your configuration to use https
 >>> consistently. --[[Joey]]
 
-[[tag done]]
+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. -- Brian May
+
+I noticed the links to the images on <http://ikiwiki.info/recentchanges/> are also absolute, that is <http://ikiwiki.info/wikiicons/diff.png>; this seems surprising, as the change.tmpl file uses &lt;TMPL_VAR BASEURL&gt;
+which seems to do the right thing in page.tmpl, but not for change.tmpl. Where is BASEURL set? -- Brian May
+
+> The use of an absolute baseurl in change.tmpl is a special case. --[[Joey]]