You don't need "satisfy any" if you only use the "order allow,deny" or
"order deny,allow" directives.
I personally don't use .htaccess files as I think it makes management more
difficult.
Here's an example of a working configuration from an httpd.conf file.
Order deny,allow
Deny from all
Allow from 10.
AuthType Basic
AuthName "private"
AuthDBUserFile /path/to/dbuserfile
require valid-user
satisfy any
This allows anyone on an internal address to access the page without a
password prompt. If you want everyone to have to login, remove the third
line.
You may be getting a second prompt because your "AuthName" field doesn't
match for both directories. Without seeing your .htaccess files it's hard to
say.
-
Happy new Millennium - http://www.rog.nmm.ac.uk/mill/index.htm
John Airey
Internet Systems Support Officer, ITCSD, Royal National Institute for the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]
> -----Original Message-----
> From: D. Scott Davidson [mailto:[EMAIL PROTECTED]]
> Sent: 11 January 2001 18:30
> To: [EMAIL PROTECTED]
> Subject: Running secure and none-secure areas with mod-ssl
>
>
> Hello,
>
> I am trying to run mod-ssl just for the login, and then
> proceed to pages
> that do not need the SSL, put still need to be protected by
> the official
> login.
>
> The initial login works fine. I use an .htaccess file to
> prompt this. Next I
> try to
> go to pages that do not need SSL. I have set-up some
> directories so that
> they disable the SSL when called with a full pathname. I use
> sections like
> this in the config file for the main server to do this:
>
> <Directory "/www/htdocs/wells/HTML">
> order deny,allow
> allow from all
> Satisfy any
> </Directory>
>
>
> <Directory "/www/htdocs/wells/HTML/Owner">
> order deny,allow
> allow from all
> Satisfy any
> </Directory>
>
> But, when I get to the need for cgi-bin scripts, I get a repeat login
> prompt (after the initial login prompt was satified with
> SSL), before it lets
> me go onward.
>
> I have tried to use the same procedure for the cgi-bin directory:
>
> <Directory "/www/htdocs/wells/cgi-bin/">
> order deny,allow
> allow from all
> Satisfy any
> </Directory>
>
> But this causes server errors when the cgi-bin directory is
> accessed with
> the "Satisfy any" statement included.
>
> I am basically just looking for a good way to access pages
> without using SSL,
> put still keeping them password protected.
>
> Much thanks in advance.
>
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
