Hmm, I'm not sure what you mean - I have two virtual hosts at the moment, one setup with www.site and one with dev.site - both redirecting to the mongrel_cluster...
I'm going to be hosting many sites on this box so adding a location directive of / won't work as it will restrict access to everything, and the directory directive doesn't seem to get picked up before the redirect is implemented from the virtualhost directive. I think the virtualhost directive has a higher priority than the directory directive, so gets implemented before the directory directive... Its not really a problem, as I don't really need it right now, but it would be nice to know that it is possible with this type of setup. Save connecting via different method I'm not sure what else is possible. Any help would be greatly appreciated. Cheers On 13 May 2007, at 23:16, Sean Cribbs wrote: > Actually sounds like you need two virtual host. The "dev.mysite.com" > would have the added HTTP authentication, not a specific location or > directory. You could still proxy to the same Mongrels inside the > second virtual host. > > Sean > > On 5/13/07, Dominic <[EMAIL PROTECTED]> wrote: >> Thanks for the reply - I didn't - I was just using the directory >> directive ... I guess location has a higher priority as it gets >> picked up whereas directory doen't. >> >> I have pretty much left it closed for now as it hasn't been necessary >> to add. Although it would be a nice to allow the previewing of draft >> pages - whilst restricting access... >> >> Please forgive my ignorance, but I don't understand how restricting >> access to dev.site/path helps though, as people can still see >> dev.site/ - which is what I am trying to restrict... >> >> Are you redirecting everything to be accessed via /path and then >> restricting that? If so how are you doing that just for the dev. >> site? >> >> Thanks for your help - both of you. >> >> >> >> On 13 May 2007, at 20:20, Ryan Casey wrote: >> >>> This is a little late...but... >>> >>> Did you try using the location directive to restrict access? >>> >>> <Location /intranet> >>> AuthType Basic >>> AuthName "Intranet" >>> AuthUserFile /etc/httpd/conf/http.users >>> AuthGroupFile /etc/httpd/conf/http.group >>> Require group my_grp >>> </Location> >>> >>> This works for me with apache 2.0.x and mod_proxy. >>> >>> HTH, >>> -Ryan Casey >> >> >> _______________________________________________ >> Radiant mailing list >> Post: [email protected] >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
