From 2015f2305299fe18ec22dcfeeebd6a7e985d104b Mon Sep 17 00:00:00 2001 From: klml Date: Mon, 16 Apr 2012 15:57:20 -0400 Subject: [PATCH] Added a comment --- ..._563040aa099c9366dc5701eb4bc9c10d._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment diff --git a/doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment b/doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment new file mode 100644 index 000000000..75b9d49bc --- /dev/null +++ b/doc/forum/access_restrictions:_for_extranet/comment_2_563040aa099c9366dc5701eb4bc9c10d._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="klml" + ip="188.174.93.195" + subject="comment 2" + date="2012-04-16T19:57:20Z" + content=""" +hi smcv, + +> when a page is viewed, the web server serves the compiled HTML without IkiWiki being involved. + +yes you are right, but I still think its a feature ;) + +> The best way to integrate access control into IkiWiki would probably be to have a CGI user interface for .htaccess or equivalent - but you'd still have to be careful, because, for instance, if a user can edit public pages, then they can insert a \[[!include]] directive to make the content of a private page public. + +My usecase is a website with an small internal area, its just for not \"so public\" files, no private files. And I only have some trusted users. + +thx +klml + +"""]] -- 2.32.0.93.g670b81a890