Apache-1.3.19 and Aliasing NOT WORKING!!!

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Alex Kamalo » Sat, 03 Mar 2001 09:03:19



Guys, this is very frustrating for me. I had to alias
/usr/local/netstaint/share directory and I did put in Alias files in
httpd.conf file but it's not working! I did every possible combination of
Alias entry (with and without trailing '/') but it is still pointing to a
DocumentRoot directory no matter what I do! Here is my httpd.conf file,
please take a look if you find anything unusual. This what I get from
error_log:

# tail -f ./error_log

Thu Mar  1 18:27:57 2001] [error] [client 192.168.1.2] File does not exist:
/opt/web/Internal2/adm/htdocs/netsaint
[Thu Mar  1 18:28:16 2001] [error] [client 192.168.1.2] File does not exist:
/opt/web/Internal2/adm/htdocs/netsaint

This is my httpd.conf file:

##
## httpd.conf -- Apache HTTP server configuration file
##

#
# 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 <URL:http://www.apache.org/docs/> 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.
#
# After this file is processed, the server will look for and process
# /opt/web/Internal2/adm/conf/srm.conf and then
/opt/web/Internal2/adm/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# 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/apache" will be interpreted by the
# server as "/usr/local/apache/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.
#

#
# ServerType is either inetd, or standalone.  Inetd mode is only supported
on
# Unix platforms.
#
ServerType standalone

#
# 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 <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/opt/web/Internal2/adm"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#
#LockFile /opt/web/Internal2/adm/logs/httpd.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /opt/web/Internal2/adm/logs/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this.  But if yours does (you'll know
because
# this file will be  created when you run Apache) then you *must* ensure
that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile /opt/web/Internal2/adm/logs/httpd.scoreboard

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order.  The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults.  You can have
the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Server-pool size regulation.  Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request.  If there are fewer than MinSpareServers, it creates
# a new spare.  If there are more than MaxSpareServers, some of the
# spares die off.  The default values are probably OK for most sites.
#
MinSpareServers 5
MaxSpareServers 10

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 5

#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 150

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies.  The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources.  On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
#       request per connection. For example, if a child process handles
#       an initial request and 10 subsequent "keptalive" requests, it
#       would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

#
# BindAddress: You can support virtual hosts with this option. This
directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#
#BindAddress *

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO
you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Please read the file README.DSO in the Apache 1.3 distribution for more
# details about the DSO mechanism and run `httpd -l' for the list of already
# built-in (statically linked and thus always available) modules in your
httpd
# binary.
#
# Note: The order in which modules are loaded is important.  Don't change
# the order below without expert advice.
#
# Example:
# LoadModule foo_module libexec/mod_foo.so

#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# If your ServerType directive (set earlier in the 'Global Environment'
# section) is set to "inetd", the next few directives don't have any
# effect since their settings are defined by the inetd configuration.
# Skip ahead to the ServerAdmin directive.
#

#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 80

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
#  . On SCO (ODT 3) use "User nouser" and "Group nogroup".
#  .
...

read more »

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Joshua Sliv » Sat, 03 Mar 2001 09:28:32



> Guys, this is very frustrating for me. I had to alias
> /usr/local/netstaint/share directory and I did put in Alias files in
> httpd.conf file but it's not working! I did every possible combination of
> Alias entry (with and without trailing '/') but it is still pointing to a
> DocumentRoot directory no matter what I do! Here is my httpd.conf file,
> please take a look if you find anything unusual. This what I get from
> error_log:
> # tail -f ./error_log
> Thu Mar  1 18:27:57 2001] [error] [client 192.168.1.2] File does not exist:
> /opt/web/Internal2/adm/htdocs/netsaint
> [Thu Mar  1 18:28:16 2001] [error] [client 192.168.1.2] File does not exist:
> /opt/web/Internal2/adm/htdocs/netsaint
> This is my httpd.conf file:

Posting the whole httpd.conf is a huge waste of bandwidth and time for
people trying to help.  Please post only the relevant parts.

The Alias directive looks right (without the trailing slash!).  Here
are a few things to think about:

1. Did you restart Apache after making the change?

2. Are you sure you are editing the same httpd.conf file
that Apache is reading?  (Putting in an obvious syntax error
and trying to restart should tell you.)

3. Are you sure that mod_alias is present? (Try httpd -l or try
putting the directives outside the <IfModule> section and see
if you get a syntax error.)

--
Joshua Slive

http://slive.ca/

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by David Efflan » Sat, 03 Mar 2001 09:48:05



>Guys, this is very frustrating for me. I had to alias
>/usr/local/netstaint/share directory and I did put in Alias files in
>httpd.conf file but it's not working! I did every possible combination of
>Alias entry (with and without trailing '/') but it is still pointing to a
>DocumentRoot directory no matter what I do! Here is my httpd.conf file,
>please take a look if you find anything unusual. This what I get from
>error_log:

># tail -f ./error_log

>Thu Mar  1 18:27:57 2001] [error] [client 192.168.1.2] File does not exist:
>/opt/web/Internal2/adm/htdocs/netsaint
>[Thu Mar  1 18:28:16 2001] [error] [client 192.168.1.2] File does not exist:
>/opt/web/Internal2/adm/htdocs/netsaint

Nothing jumps out at me from your httpd.conf other than some quotes where
not really required.

Do all directories in DocumentRoot path or alias paths have at least 701
permission?

Did you restart apache (or at least send it a -HUP signal) after making
changes to httpd.conf?

--

http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Alex Kamalo » Sat, 03 Mar 2001 10:30:20


Sorry Josh! Thank you  for replying. I just wanted to get this Alias thing
running so bad. Yes, I  did restart httpd. I know that  mod_alias.c compiles
by default, and so far no errors reported. It's still not working!

Alex



> > Guys, this is very frustrating for me. I had to alias
> > /usr/local/netstaint/share directory and I did put in Alias files in
> > httpd.conf file but it's not working! I did every possible combination
of
> > Alias entry (with and without trailing '/') but it is still pointing to
a
> > DocumentRoot directory no matter what I do! Here is my httpd.conf file,
> > please take a look if you find anything unusual. This what I get from
> > error_log:

> > # tail -f ./error_log

> > Thu Mar  1 18:27:57 2001] [error] [client 192.168.1.2] File does not
exist:
> > /opt/web/Internal2/adm/htdocs/netsaint
> > [Thu Mar  1 18:28:16 2001] [error] [client 192.168.1.2] File does not
exist:
> > /opt/web/Internal2/adm/htdocs/netsaint

> > This is my httpd.conf file:

> Posting the whole httpd.conf is a huge waste of bandwidth and time for
> people trying to help.  Please post only the relevant parts.

> The Alias directive looks right (without the trailing slash!).  Here
> are a few things to think about:

> 1. Did you restart Apache after making the change?

> 2. Are you sure you are editing the same httpd.conf file
> that Apache is reading?  (Putting in an obvious syntax error
> and trying to restart should tell you.)

> 3. Are you sure that mod_alias is present? (Try httpd -l or try
> putting the directives outside the <IfModule> section and see
> if you get a syntax error.)

> --
> Joshua Slive

> http://slive.ca/

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Alex Kamalo » Sat, 03 Mar 2001 10:27:57


Thank you very much for replying! Yes I did restart apache after each
modification, but so far no avail.

Thank You.

Alex


> >Guys, this is very frustrating for me. I had to alias
> >/usr/local/netstaint/share directory and I did put in Alias files in
> >httpd.conf file but it's not working! I did every possible combination of
> >Alias entry (with and without trailing '/') but it is still pointing to a
> >DocumentRoot directory no matter what I do! Here is my httpd.conf file,
> >please take a look if you find anything unusual. This what I get from
> >error_log:

> ># tail -f ./error_log

> >Thu Mar  1 18:27:57 2001] [error] [client 192.168.1.2] File does not
exist:
> >/opt/web/Internal2/adm/htdocs/netsaint
> >[Thu Mar  1 18:28:16 2001] [error] [client 192.168.1.2] File does not
exist:
> >/opt/web/Internal2/adm/htdocs/netsaint

> Nothing jumps out at me from your httpd.conf other than some quotes where
> not really required.

> Do all directories in DocumentRoot path or alias paths have at least 701
> permission?

> Did you restart apache (or at least send it a -HUP signal) after making
> changes to httpd.conf?

> --

> http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
> http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Joshua Sliv » Sat, 03 Mar 2001 10:49:40



> Sorry Josh! Thank you  for replying. I just wanted to get this Alias thing
> running so bad. Yes, I  did restart httpd. I know that  mod_alias.c compiles
> by default, and so far no errors reported. It's still not working!

Please look again at 2 and 3 below which you have not fully answered.
Just because mod_alias is a default module doesn't mean you didn't
accidentally disable it.
Quote:>> 1. Did you restart Apache after making the change?

>> 2. Are you sure you are editing the same httpd.conf file
>> that Apache is reading?  (Putting in an obvious syntax error
>> and trying to restart should tell you.)

>> 3. Are you sure that mod_alias is present? (Try httpd -l or try
>> putting the directives outside the <IfModule> section and see
>> if you get a syntax error.)

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Alex Kamalo » Sat, 03 Mar 2001 11:33:27


Problem solved. Sorry for incovenience. It was a typo. Stupid me!!!

Thanks for everyone.

Alex

 
 
 

Apache-1.3.19 and Aliasing NOT WORKING!!!

Post by Max Dittric » Sat, 03 Mar 2001 20:13:35



> Problem solved. Sorry for incovenience. It was a typo. Stupid me!!!

youre funny (not really).

...max

ps. toUppercase( message.subject ); message.subject += "!!!!!!";
message.appFullQuote( inReply );

 
 
 

1. probs building apache-1.3.19 on solaris 8

I run ./configure with no problems, but when building, make fails with
the following:

===> src/main
gcc -c  -I../os/unix -I../include -I/usr/local/ssl/include   -DSOLARIS2=280 -DTARGET=\"httpsd\" -DDEV_RANDOM=efgbvmu -DAPACHE_SSL `../apaci` -DAPACHE_SSL alloc.c
alloc.c: In function `spawn_child_core':
alloc.c:2291: `STDOUT_FILENO' undeclared (first use in this function)
alloc.c:2291: (Each undeclared identifier is reported only once
alloc.c:2291: for each function it appears in.)
alloc.c:2297: `STDIN_FILENO' undeclared (first use in this function)
alloc.c:2303: `STDERR_FILENO' undeclared (first use in this function)
make[3]: *** [alloc.o] Error 1
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory `/appl/apache/src/apache_1.3.19/src'
make[1]: *** [build-std] Error 2
make[1]: Leaving directory `/appl/apache/src/apache_1.3.19'
make: *** [build] Error 2
#

The above is when building with apache-ssl, the same happens without
any modules at all, also. And also when trying to build apache-1.3.14.

Am I missing any packages? Which?

Thanks in advance,

-- Ole Michaelsen

XFUT: comp.unix.solaris

2. Delete Key in Bash? Any way with Termcap?

3. PHP-4.0.4p11 + GD + apache-1.3.19

4. Obvious: parport_serial depends on PCI.

5. apache-1.3.19 and FreeBSD 4.3 Beta #1

6. Help: Change video port from RGB to vga-15pin on 7012

7. Is it possible with Apache 3.19 for users to run scripts through /~username?

8. problem: lilo w/ hda(linux) & sda(win95)

9. Problems with CustomLogFormat with Apache v1.3.19

10. BASH Frequently-Asked Questions (FAQ version 3.19)

11. RST packet Apache_1.3.19 mod_ssl

12. mod_ssl-2.8.1 + mod_perl-1.25 + apache_1.3.19 compile problem

13. linux1.3.19 tunnelling compile errors