www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tilghman Lesher <Tilghman.Les...@vanderbilt.edu>
Subject config/2540: apache signals error on symlink in path
Date Wed, 01 Jul 1998 22:05:57 GMT

>Number:         2540
>Category:       config
>Synopsis:       apache signals error on symlink in path
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jul  1 15:10:01 PDT 1998
>Originator:     Tilghman.Lesher@vanderbilt.edu
>Release:        1.3.0
Solaris 2.5.1 with all 2.5.1 Recommended patches, latest version of gcc
SunOS mahal 5.5.1 Generic sun4u sparc SUNW,Ultra-1
gcc version
Currently, /usr/local is a symlink to /export/home/usr/local; this
was done for a number of reasons, such as the fact that this machine
is a demo machine and my manager isn't keen on relying on it for core
network functions.  Hence, the machine cannot be expanded for financial
Apache httpd signals an invalid symlink in the logfile and sends 403
to any client attempting to access /index.html

If the base path contains no symlinks (such as pointing to
/export/home/usr/local/apache instead of /usr/local/apache ), this
problem does not surface.  However, this is more of a workaround than
a fix to a bug.
[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. ]

View raw message