httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53581] New: FollowSymlinks doesn't work with DirectoryMatch and Alias
Date Sat, 21 Jul 2012 22:40:18 GMT

          Priority: P2
            Bug ID: 53581
           Summary: FollowSymlinks doesn't work with DirectoryMatch and
          Severity: normal
    Classification: Unclassified
                OS: All
          Hardware: All
            Status: NEW
           Version: 2.2.16
         Component: All
           Product: Apache httpd-2


I found a strange issue...
What I have is about the following:

        Alias /icinga/images/icinga/favicon.ico



#some stuff adding authorization control

                Options +symLinksIfOwnerMatch

In /srv/www/external/virtual-hosts/
there is a symlink, pointing to the favicon.ico.

So the idea is the following:
A user accesses /icinga/images/icinga/favicon.ico which is aliased to
which is a symlink to some other place.

The first DirectoryMatch matches some other dirs and the dir where I'm aliasing
to (without the subdir classic).... and adds some general rules (mainly

The second DirectoryMatch matches only:
and subdirs (except classic) thereof.

I'd have expected that access is granted (due to the Options
+symLinksIfOwnerMatch) but I get a forbidden and:
[Sun Jul 22 00:26:36 2012] [error] [client] Symbolic link not allowed
or link target not accessible:
in the error log.

Actually the above thing exactly works if I replace the 2nd DirectoryMatch
                Options +symLinksIfOwnerMatch
which is however not a real solution, as I don't want to match the classic

Changing to +followSymlinks doesn't change.

It somehow seems as if followSymlinks/symLinksIfOwnerMatch don't work in
DirectoryMatch blocks.

Any ideas?


You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message