On 9/9/05, Forrest Aldrich <[EMAIL PROTECTED]> wrote: > Okay here's what happened. > > My config: > > > User www > Group www > ServerName forrie.com > DocumentRoot /home/test > Listen *:8091 > > <Directory /> > Options All > </Directory> > > ErrorLog /var/log/httpd-error.log > > If I do a "ln -s /usr/local/shares/forrie/files ." into the above > DocumentRoot, I get the proper symlink: > > files -> /usr/local/shares/forrie/files > > And I get this error: > > [Fri Sep 09 13:49:33 2005] [error] [client 192.168.1.99] Symbolic link not > allowed: /hom > e/test/files > > BUT... > > If I create a file "test2" in the ".." directory, containing "foo", then > "ln -s /home/test2 ." which gives me: > > test2 -> /home/test2 > > I can get to it via the browser. > > Now I'm suspicious of a filesystem item with FreeBSD-6.0 -- the symblic > link to "files" is on the second hard drive, whereas the first is on the > same disk. > > Other than that possibility, I'm at a loss here.
Ok. I think I've got it. Try this: mkdir /home/test2/test3/ echo hello > /home/test2/test3/index.txt ln -s /home/test2/test3/ /home/test/test3 chmod -x /home/test2 lynx http://localhost:8091/index.txt A similar setup gave me the error you found. The problem is the file permissions on the target of the symlink. One of the parent directories of the path leading to your file does not give search permissions. So this was a configuration issue all along, but was made difficult to diagnose by an innacurate error message in the error log. I believe the error message bug is reported here: http://issues.apache.org/bugzilla/show_bug.cgi?id=28515 Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL: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]
