compare yours with mine - and tell me if the fixed version would work.
At 04:11 8-6-2005, you wrote:
> -Original Message-
> From: Joshua Slive [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 05, 2005 9:52 PM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] Missing User-Agent:
>
>
> On 6/5/05, Michael D. Berger <[EMAIL PROTECTED]> wrote:
> > > On 6/4/05, Michael D. Berger <[EMAIL PROTECTED]> wrote:
> > > > I notice that Apache 2.0 rejects, with a 403,
> > > > a GET that does not have a User-Agent header,
> > > > and I to get some of these.
> > > >
> > > > Why do I get them?
> > > > Why are they rejected?
> > >
> > > Apache 2 certainly does not do this by default. There must be
> > > someplace in your config that your are restricting based on
> > > User-Agent.
> > >
> > > Joshua.
> >
> > cd /etc/httpd/conf
> > vi httpd.conf
> > :set ignorecase
> > /user
> > /agent
> >
> > I find nothing in the config file that suggests this.
>
> What about Include'd config files?
>
> Other than that, you haven't mentioned the relevant error log and
> access log messages. You also haven't mentioned if you are running a
> proxy in front of apache, or if apache is proxying to another server,
> etc.
>
> As I said, apache doesn't do this by default.
>
> Joshua.
I am using the configuration supplied with RH-E-W-3, with a few changes,
inclusing a virtual host and blocking of directory listing. As you can
see from the log lines below, the block of directory listing is involved.
It is as if when a User-Agent is not supplied, it tries to list the
direcory, even though there is an index.html. Why would this be? I
don't know about the Include'd config files -- whatever RH set up.
Sorry for the long silence.
Mike.
halls-129-31-65-108.hor.ic.ac.uk - - [07/Jun/2005:09:42:01 -0400] "GET /
HTTP/1.1" 200 808 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB;
rv:1.7.8) Gecko/20050511 Firefox/1.0.4"
adsl-68-72-134-32.dsl.chcgil.ameritech.net - - [07/Jun/2005:13:52:47 -0400]
"GET / HTTP/1.0" 403 202 "-" "-"
[Tue Jun 07 13:52:47 2005] [error] [client 68.72.134.32] Directory index
forbidden by rule: /var/www/html/
--
Michael D. Berger
[EMAIL PROTECTED]
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs-2.0/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/minister/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#LockFile logs/accept.lock
#
# ScoreBoardFile: File used to store internal server process information.
# If unspecified (the default), the scoreboard will be stored in an