On 6/12/06, Zakai Kinan <[EMAIL PROTECTED]> wrote:
I see. The way I used the filematch did not result in
any errors. Apache seems to simply ignore the
directive. The directory is already protected, but I
wanted to restrict access to one script to one user
within the directory. The user is par
I see. The way I used the filematch did not result in
any errors. Apache seems to simply ignore the
directive. The directory is already protected, but I
wanted to restrict access to one script to one user
within the directory. The user is part of the
authentication for the directory in the htpa
On 6/9/06, Zakai Kinan <[EMAIL PROTECTED]> wrote:
The idea of requiring a specific user to access a
script does not work. Secret is a perl script. The
restrictions on the directory work as expected.
Man oh man. Please banish the phrase "does not work" from your
vocabulary when you talk on a
The idea of requiring a specific user to access a
script does not work. Secret is a perl script. The
restrictions on the directory work as expected.
ZK
--- Joshua Slive <[EMAIL PROTECTED]> wrote:
> On 6/9/06, Zakai Kinan <[EMAIL PROTECTED]>
> wrote:
> > I have this directive
> >
> >r
On 6/9/06, Zakai Kinan <[EMAIL PROTECTED]> wrote:
I have this directive
require user "{Admin}"
in an htaccess file and it does not work. Does any
have any ideas. I have also tried it in httpd.conf
file.
Define exactly what "does not work" means. Does the require work if
it is not i
I have this directive
require user "{Admin}"
in an htaccess file and it does not work. Does any
have any ideas. I have also tried it in httpd.conf
file.
TIA
ZK
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection
