[Bug 1212372] Symbolic link not allowed or link target not accessible
https://bugzilla.suse.com/show_bug.cgi?id=1212372 https://bugzilla.suse.com/show_bug.cgi?id=1212372#c2 David Anes <david.anes@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.anes@suse.com Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from David Anes <david.anes@suse.com> --- (In reply to John Goutbeck from comment #1)
With my test sym link directory htd, added this to the default-server.conf --- # Make sure that symlink /srv/www does not make problems <Directory /srv/www> Options +FollowSymlinks </Directory> --- and now the browser displays ‘It Works!’
So why does the directory of one above need to be in the conf?
Because 'htd' is within '/srv/www' and because default configuration is NOT to follow symlinks, then 'htd' is not accessible. By setting the parent path '/srv/www' with FollowSymlinks, then 'htd' is reachable. This is clearly stated in the documentation: https://httpd.apache.org/docs/2.4/mod/core.html#directory
Enclose a group of directives that apply only to the named file-system directory, sub-directories, and their contents.
I'm closing this one as invalid, but feel free to reopen if you find any other issue. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com