On 24.09.13 11:51, Andreas Gohr wrote:
For blocking the whole wiki, yes absolutely. For blocking single namespaces it might not be possible.Is this because of the specific software? I mean, would be possible with Apache?Don't know about nginx, but with Apache you can control access to specific directories (!) with Allow/Deny directives.My doubts are not related to a specific webserver. The problem is that directory based protection won't work, because namespaces are not directories the webserver knows about.
Hmm. /My/ namespaces /are/ directories ;-) : # ls -1F /local/www/dokuwiki/data/pages/ archives/ archives.txt bcr.txt bio-it/ central_services/ central_services.txt computing/ computing.txt doc/ faq/ faq.txt locations.txt playground/ policies/ services/ services.txt sitemap.txt software/ software.txt start.txt wiki/ # ls -1F /local/www/dokuwiki/data/media bio-it/ computing/ configuration.jpg corp/ courses/ doc/ faq/ groups/ hosts/ locations_3rd_floor.png login.jpg network2.jpg network.jpg wiki/ #The <namespace.txt> files might have to be handled specially (but I said that this will become cumbersome).
So the only aproach would be URL based protection, but that might not work depending on the used
Allow/Deny (for Apache) only work for directories, not for URLs, and...
rewrite config and a namespace might also be passed in a POST parameter and not be reflected in the URL.
...trying to handle this with rewriting is probably even more complex and error prone.
Georg: What is the general goal of the IP ACLs in your case? frank -- DokuWiki mailing list - more info at http://www.dokuwiki.org/mailinglist