I'm still having problems even with script below; 
Please verify my portion of access.conf for httpf access:
*******************************************
<Directory /home/httpd/html>
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".

# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.

Options Indexes Includes FollowSymLinks

# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo", 
# "AuthConfig", and "Limit"

AllowOverride None

<Limit GET POST>
order allow,deny
deny from all
Allow from 888.888.888.888 777.777.777.777.777
</Limit> 
</Directory>

**************************************

Can you see any errors?
What is the syntax between IP number's ???

Also, should the following 2 lines be included???
Options Indexes Includes FollowSymLinks
AllowOverride None

Thanks.


 

-----Original Message-----
From: Gavin Grabias [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 30, 1999 11:55 AM
To: [EMAIL PROTECTED]
Subject: Re: [newbie] ACCESS.CONF syntax for restricting IP's


On Thu, 30 Sep 1999, you wrote:
> How does one control(limit) the httpd web-server access to only dozen IP's
> that are not in the same subnet.
> 
> for example: If I wanted to restrict only the following users to my
intranet
> web-server,
> 888.888.888.888, 777.777.777.777, 666.666.666.666, 555.555.555.555.
> 
> exactly what would the script appear as?


<Directory /home/httpd/html>
<Limit GET POST>
        Order Deny, Allow
        Deny from ALL
        Allow from 888.888.888.888 777.777.777.777 ... 
</Limit>
</Directory>
##Gavin##

> 
> 
> (httpd is not in my inet.d)
> 
> Thanks.
-- 

Regards,
   Gavin ([EMAIL PROTECTED])
********************************************************************
      ENTER.NET - "The Road to the Internet Starts Here!" (tm)
  (610) 437-2221 * http://www.enter.net/ * email:[EMAIL PROTECTED]
********************************************************************

Reply via email to