www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ed Harris <EHar...@LISTER2.LHL.UAB.EDU>
Subject RE: config/2534: Expected </Directory> but saw </Directory>
Date Thu, 02 Jul 1998 20:40:00 GMT
The following reply was made to PR config/2534; it has been noted by GNATS.

From: Ed Harris <EHarris@LISTER2.LHL.UAB.EDU>
To: "'coar@apache.org'" <coar@apache.org>
Cc: "'apbugs@Apache.Org'" <apbugs@Apache.Org>
Subject: RE: config/2534: Expected </Directory> but saw </Directory>
Date: Thu, 2 Jul 1998 15:27:45 -0500 

 This message is in MIME format. Since your mail reader does not understand
 this format, some or all of this message may not be legible.
 
 ------ =_NextPart_000_01BDA5F7.DF5DE13E
 Content-Type: text/plain
 
 Hi!
 I included a text lising, and the orig file as an attachment.
 I copied the 1.3.0 access.conf file from my linux 2.0.30 system, it
 gives the same error under aix 4.3 on PPC604e Quad CPU system.
 
 -----Original Message-----
 From: coar@apache.org [mailto:coar@apache.org]
 Sent: Thursday, July 02, 1998 5:51 AM
 To: apache-bugdb@apache.org; coar@apache.org; edharris@uab.edu
 Subject: Re: config/2534: Expected </Directory> but saw </Directory>
 
 
 [In order for any reply to be added to the PR database, ]
 [you need to include <apbugs@Apache.Org> in the Cc line ]
 [and leave the subject line UNCHANGED.  This is not done]
 [automatically because of the potential for mail loops. ]
 
 
 Synopsis: Expected </Directory> but saw </Directory>
 
 State-Changed-From-To: open-feedback
 State-Changed-By: coar
 State-Changed-When: Thu Jul  2 03:51:14 PDT 1998
 State-Changed-Why:
 
 Please examine the file carefully to make sure there aren't
 any embedded control characters or CRs; examine the error
 message just as carefully.  If you don't find any, please
 mail the offending access.conf file to me at
 <coar@Apache.Org> and use the same subject line as is on
 this message.
 
 
 ##
 ## access.conf -- Apache HTTP server configuration file
 ##
 
 # access.conf: Global access configuration
 # Online docs at http://www.apache.org/
 
 # This file defines server settings which affect which types of services
 # are allowed, and in what circumstances. 
 
 # Each directory to which Apache has access, can be configured with
 respect
 # to which services and features are allowed and/or disabled in that
 # directory (and its subdirectories). 
 
 # Originally by Rob McCool
 
 # First, we configure the "default" to be a very restrictive set of 
 # permissions.  
 ServerName Ovid1.lhl.uab.edu
 
 
 <Directory />
 	AllowOverride None
 </Directory>
 # Note that from this point forward you must specifically allow
 # particular features to be enabled - so if something's not working as
 # you might expect, make sure that you have specifically enabled it
 # below.
 
 # This should be changed to whatever you set DocumentRoot to.
 
 <Directory /home/apache/share/htdocs>
 
 # This may also be "None", "All", or any combination of "Indexes",
 # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
 
 # Note that "MultiViews" must be named *explicitly* --- "Options All"
 # doesn't give it to you.
 
 Options Indexes FollowSymLinks
 
 # This controls which options the .htaccess files in directories can
 # override. Can also be "All", or any combination of "Options",
 "FileInfo", 
 # "AuthConfig", and "Limit"
 
 AllowOverride None
 
 # Controls who can get stuff from this server.
 
 order allow,deny
 allow from all
 
 </Directory>
 
 # /home/apache/share/cgi-bin should be changed to whatever your
 ScriptAliased
 # CGI directory exists, if you have that configured.
 
 <Directory /home/apache/share/cgi-bin>
 AllowOverride None
 Options None
 </Directory>
 
 # Allow server status reports, with the URL of
 http://servername/server-status
 # Change the ".your_domain.com" to match your domain to enable.
 
 #<Location /server-status>
 #SetHandler server-status
 
 #order deny,allow
 #deny from all
 #allow from .your_domain.com
 #</Location>
 
 # There have been reports of people trying to abuse an old bug from
 pre-1.1
 # days.  This bug involved a CGI script distributed as a part of Apache.
 # By uncommenting these lines you can redirect these attacks to a
 logging 
 # script on phf.apache.org.  Or, you can record them yourself, using the
 script
 # support/phf_abuse_log.cgi.
 
 #<Location /cgi-bin/phf*>
 #deny from all
 #ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
 #</Location>
 
 # You may place any other directories or locations you wish to have
 # access information for after this one.
 
 
 
 ------ =_NextPart_000_01BDA5F7.DF5DE13E
 Content-Type: application/octet-stream;
 	name="access.conf.org"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: attachment;
 	filename="access.conf.org"
 
 ##=0A=
 ## access.conf -- Apache HTTP server configuration file=0A=
 ##=0A=
 =0A=
 # access.conf: Global access configuration=0A=
 # Online docs at http://www.apache.org/=0A=
 =0A=
 # This file defines server settings which affect which types of =
 services=0A=
 # are allowed, and in what circumstances. =0A=
 =0A=
 # Each directory to which Apache has access, can be configured with =
 respect=0A=
 # to which services and features are allowed and/or disabled in that=0A=
 # directory (and its subdirectories). =0A=
 =0A=
 # Originally by Rob McCool=0A=
 =0A=
 # First, we configure the "default" to be a very restrictive set of =0A=
 # permissions.  =0A=
 ServerName Ovid1.lhl.uab.edu=0A=
 =0A=
 =0A=
 <Directory />=0A=
 	AllowOverride None=0A=
 </Directory>=0A=
 # Note that from this point forward you must specifically allow=0A=
 # particular features to be enabled - so if something's not working =
 as=0A=
 # you might expect, make sure that you have specifically enabled it=0A=
 # below.=0A=
 =0A=
 # This should be changed to whatever you set DocumentRoot to.=0A=
 =0A=
 <Directory /home/apache/share/htdocs>=0A=
 =0A=
 # This may also be "None", "All", or any combination of "Indexes",=0A=
 # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".=0A=
 =0A=
 # Note that "MultiViews" must be named *explicitly* --- "Options =
 All"=0A=
 # doesn't give it to you.=0A=
 =0A=
 Options Indexes FollowSymLinks=0A=
 =0A=
 # This controls which options the .htaccess files in directories can=0A=
 # override. Can also be "All", or any combination of "Options", =
 "FileInfo", =0A=
 # "AuthConfig", and "Limit"=0A=
 =0A=
 AllowOverride None=0A=
 =0A=
 # Controls who can get stuff from this server.=0A=
 =0A=
 order allow,deny=0A=
 allow from all=0A=
 =0A=
 </Directory>=0A=
 =0A=
 # /home/apache/share/cgi-bin should be changed to whatever your =
 ScriptAliased=0A=
 # CGI directory exists, if you have that configured.=0A=
 =0A=
 <Directory /home/apache/share/cgi-bin>=0A=
 AllowOverride None=0A=
 Options None=0A=
 </Directory>=0A=
 =0A=
 # Allow server status reports, with the URL of =
 http://servername/server-status=0A=
 # Change the ".your_domain.com" to match your domain to enable.=0A=
 =0A=
 #<Location /server-status>=0A=
 #SetHandler server-status=0A=
 =0A=
 #order deny,allow=0A=
 #deny from all=0A=
 #allow from .your_domain.com=0A=
 #</Location>=0A=
 =0A=
 # There have been reports of people trying to abuse an old bug from =
 pre-1.1=0A=
 # days.  This bug involved a CGI script distributed as a part of =
 Apache.=0A=
 # By uncommenting these lines you can redirect these attacks to a =
 logging =0A=
 # script on phf.apache.org.  Or, you can record them yourself, using =
 the script=0A=
 # support/phf_abuse_log.cgi.=0A=
 =0A=
 #<Location /cgi-bin/phf*>=0A=
 #deny from all=0A=
 #ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi=0A=
 #</Location>=0A=
 =0A=
 # You may place any other directories or locations you wish to have=0A=
 # access information for after this one.=0A=
 =0A=
 
 ------ =_NextPart_000_01BDA5F7.DF5DE13E--

Mime
View raw message