On Sun, 1 Feb 2015 17:45:14 -0500, you wrote:
>On Sun, Feb 1, 2015 at 5:21 PM, Steve Matzura wrote:
>> If it didn't match, wouldn't httpd -t kick it back as a mismatch? I
>
>No, it doesn't know at startup that no URL will be mapped below this directory.
Well here's the thing. This worked on the
On Sun, Feb 1, 2015 at 5:21 PM, Steve Matzura wrote:
> If it didn't match, wouldn't httpd -t kick it back as a mismatch? I
No, it doesn't know at startup that no URL will be mapped below this directory.
--
Eric Covener
cove...@gmail.com
-
On Sun, 1 Feb 2015 16:27:49 -0500, you wrote:
> either doesn't match or is overridden by a later
>configuration section (including Location)?
If it didn't match, wouldn't httpd -t kick it back as a mismatch? I
had that problem at first when I forgot to create the log directory
for the private are
either doesn't match or is overridden by a later
configuration section (including Location)?
On Sun, Feb 1, 2015 at 2:15 PM, Steve Matzura wrote:
> On Sun, 1 Feb 2015 12:25:52 -0500, you wrote:
>
>>Sounds like Satisfy has been set to "Any" somewhere previously. But in
>>2.4, you should skip Orde
On Sun, 1 Feb 2015 12:25:52 -0500, you wrote:
>Sounds like Satisfy has been set to "Any" somewhere previously. But in
>2.4, you should skip Order and Allow and just use Require.
I commented out both those directives and restarted. Same thing.
Anyone can get in, and no username or password is aske
Sounds like Satisfy has been set to "Any" somewhere previously. But in
2.4, you should skip Order and Allow and just use Require.
On Sun, Feb 1, 2015 at 11:55 AM, Steve Matzura wrote:
> Upon re-reading this message, I find there was something about which I
> was extremely unclear and ambiguous. I
Upon re-reading this message, I find there was something about which I
was extremely unclear and ambiguous. I said that the access to the
password-protected area wasn't working, but failed to specify just
what wasn't working. The problem is that Apache isn't asking for the
password, and letting any
I maintain a 2.2 server and am building a 2.4 one. I have a file in a
sites-enabled directory containing all the directives I need to define
security for my open and password-protected directories. There is an
"include" directive in the master configuration file
/etc/httpd/conf/httpd.conf. httpd -t
