I see two recent threads in this regard: http://lists.radiantcms.org/pipermail/radiant/2007... http://lists.radiantcms.org/pipermail/radiant/2007... The recommendation in the first thread is to use Apache .htaccess. What I cannot understand, and what wasn't resolved, is that .htaccess resides in a filesystem, whereas the pages served up by Radiant are virtual. Am I mistaken? What I'd like to do is to have the main page being public, and a subtree of the site being password protected. I suppose a compromise would be to have the password protected site being a separate tree altogether :-( Hmm.... I suppose this might be possible with: http://dev.radiantcms.org/radiant/wiki/HowToHostMu... Using this and Apache mod_proxy, it might be simpler to have: Site Root | + radiantpoweredpublicsite.com | + radiantpoweredpasswordsite.com And maybe somehow convince Apache to password protect the 2nd site. Earl
on 2007-06-05 04:23
on 2007-06-05 04:29
> http://lists.radiantcms.org/pipermail/radiant/2007... > http://lists.radiantcms.org/pipermail/radiant/2007... > > The recommendation in the first thread is to use Apache > .htaccess. What > I cannot > understand, and what wasn't resolved, is that .htaccess resides in a > filesystem, whereas > the pages served up by Radiant are virtual. The part you're missing is apache's <Location> and <LocationMatch> options. <Location /monkeys> Deny from all </Location should prevent access to your monkeys. Dan.