s of sites and files), looking for something that
could be overriding this directive. I will let you know if i find out
something...
Thank you all again. And if anyone else have any idea, i will be grateful.
Joshua Slive escribió:
On 9/13/07, J.M. Castroagudin <[EMAIL PROTECTED]> wrote:
Er... I don`t want to look like I am desperate... but i am actually a
bit, hehe...
Anyone has any idea about this? am I doing something wrong?
any contribution will be welcome
Thank you all very much!
J.M. Castroagudin escribió:
Hmmm... I thought that "deny,allow", as I had, was
Perhaps this can help you:
http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts
There are some limitations about SSL and name-based virtualhosts.
It was a shok for me when I read that...
[EMAIL PROTECTED] escribió:
Hello,
I have this error after setup 2 virtualhost based on the same I
ny directives are evaluated before the Allow directives. Access is
allowed by default. Any client which does not match a deny directive or does
match an Allow directive will be allowed access to the server."
:)
-Original Message-
From: J.M. Castroagudin [mailto:[EMAIL PROTECTED]
Sent: Thur
Hi everybody,
I have been trying to limit access to certain 'directories' (inside a
https vhost) based on IP directives. Something like this:
SetEnvIf remote_addr W.X.Y.Z intranet
SetEnvIf Client-ip W.X.Y.Z intranet
DocumentRoot "/disc/html/https"
ServerName secure.foo.com
Order