right.

[git.ikiwiki.info.git] / doc / bugs / redirect.mdwn

diff --git a/doc/bugs/redirect.mdwn b/doc/bugs/redirect.mdwn
index 5061a794063e563733ae329d5e0648f5dcfd2da1..6296c3df125565bfb7975eacfa71684f40a0ed9a 100644 (file)
--- a/doc/bugs/redirect.mdwn
+++ b/doc/bugs/redirect.mdwn
@@ -3,14 +3,24 @@ I suppose this isn't technically a bug, but whetever.
 I want symbolic links to be rendered as HTTP redirects. For example,
 if we do this,
 
 I want symbolic links to be rendered as HTTP redirects. For example,
 if we do this,
 

-```
-touch foo.mkdwn
-ln -s foo.mkdwn bar.mkdwn
-git push baz.branchable.com
-```
+    touch foo.mkdwn
+    ln -s foo.mkdwn bar.mkdwn
+    git push baz.branchable.com

 
 then the following command should print 302
 
 
 then the following command should print 302
 

-```
-curl -o /dev/null -s -w "%{http_code}" http://baz.thomaslevine.com/bar/
-```
+    curl -o /dev/null -s -w "%{http_code}" http://baz.thomaslevine.com/bar/
+
+> An interesting idea, but it conflicts somewhat with wanting symlinks to be
+> treated as the referenced file when it's safe to do so, which would be
+> great for [[todo/git-annex support]], and also good to avoid duplication
+> for files in system-wide underlays.
+>
+> Also, I don't think this is possible without help from the web server
+> configuration: for instance, under Apache, I believe the only way to get
+> an HTTP 302 redirect is via Apache-specific `.htaccess` files or
+> system-level Apache configuration.
+>
+> In current ikiwiki, you can get a broadly similar effect by either
+> using \[[!meta redir=foo]] (which does a HTML `<meta>` redirect)
+> or reconfiguring the web server. --[[smcv]]