Bug 42410 - access.conf is not ignored if it contains valid/invalid directives
Summary: access.conf is not ignored if it contains valid/invalid directives
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-27 05:16 UTC by Henri Schlereth
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-27 05:16:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Henri Schlereth 2001-05-27 05:16:01 UTC
Description of Problem:
During the process of trouble shooting a virtual hosting problem I put access data in access.conf and
uncommented the location in /etc/httpd/conf/httpd.conf. When the test failed I re-commented out
access. conf and resatarted apache. It still read the data in the access.conf

How Reproducible:
Do something like I did.

Steps to Reproduce:
1. leave access.conf commented out in httpd.conf
2. enter any access directive in access.conf (e.g virtual hosting directives or user access) 
Best way is to put something invalid to see it cough up an error message.
3. restart httpd

Actual Results:
access.conf is read despite being commented out

Expected Results:
directives in access.conf should be ignore as access.conf is commented out

Additional Information:
I was originally researching why the virtual hosting stuff wasnt working. I have followed the documented
stuff in the apache manual and even downloaded the full blown version of linuxconf to set this up.
Both of us cant be wrong. But I better bugzilla this separately.

Comment 1 Nalin Dahyabhai 2001-07-24 20:16:47 UTC
This is the documented default behavior of Apache (see
/var/www/html/manual/mod/core.html#accessconfig for more detail).

Essentially, if no access configuration file is specified, it will read and
parse access.conf.  The default access.conf includes a note that it should not
be modified, and httpd.conf includes a note that disabling this behavior
requires setting the paths for these files to /dev/null.

Tagging as not a bug.

Note You need to log in before you can comment on or make changes to this bug.