From 2d90e4ede4da06adc38fbf704b6bb29a76c75575 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 25 Feb 2008 18:16:59 -0500 Subject: web commit by http://brian.may.myopenid.com/: work around not solution --- doc/bugs/relative_links.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/bugs') diff --git a/doc/bugs/relative_links.mdwn b/doc/bugs/relative_links.mdwn index 13194737f..8e6556fda 100644 --- a/doc/bugs/relative_links.mdwn +++ b/doc/bugs/relative_links.mdwn @@ -19,4 +19,4 @@ 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. -- cgit v1.2.3