aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorhttp://anastigmatix.net/ <http://anastigmatix.net/@web>2014-10-20 19:58:54 -0400
committeradmin <admin@branchable.com>2014-10-20 19:58:54 -0400
commit34e7fe13e4f60c79de4ee38d6b2d60b08ad411a9 (patch)
tree041f31a4b18921cf96e903d2bc3f9d50e80b3c38 /doc
parent8d7ad8c3456d6cba7c122943f04ededf9bfbce44 (diff)
downloadikiwiki-34e7fe13e4f60c79de4ee38d6b2d60b08ad411a9.tar
ikiwiki-34e7fe13e4f60c79de4ee38d6b2d60b08ad411a9.tar.gz
Hadn't listed any drawbacks for the FastCGI Authorizer idea.
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Zoned_ikiwiki.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/todo/Zoned_ikiwiki.mdwn b/doc/todo/Zoned_ikiwiki.mdwn
index 24fe22133..6b562215a 100644
--- a/doc/todo/Zoned_ikiwiki.mdwn
+++ b/doc/todo/Zoned_ikiwiki.mdwn
@@ -107,6 +107,12 @@ that header might not be needed in the request, and care may be needed to config
the server to emit other necessary response headers to discourage caching of
content from a private zone.
+*Drawbacks:* Not yet implemented, someone would have to do it.
+It's not clear [[what code changes fastcgi|todo/fastcgi or modperl installation instructions]]
+would require in ikiwiki. An Authorizer seems like a good place to start because of its
+limited, simple functionality--but as it could make use of any ikiwiki-supported auth method,
+evaluate `PageSpec`s, and the like, it could still run a non-trivial amount of the code.
+
## Obstacles
A number of ikiwiki features aren't (yet) designed with zoning in mind,