You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/03/28 08:46:11 UTC
DO NOT REPLY [Bug 8014] -
Apache cannot handle NTFS Junctions (Symlinks)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8014>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8014
Apache cannot handle NTFS Junctions (Symlinks)
bugzilla@areallycool.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Component|All |Core
Resolution|FIXED |
Version|2.0.35 |2.0.44
------- Additional Comments From bugzilla@areallycool.com 2003-03-28 07:46 -------
The precise behavior noted in the original bug still occurs in 2.0.44 on UNC
(remote share) paths under Win2K Server or Win2K3RC2:
Alias /nas/junction/dir1/dir2/ "//192.168.0.10/nas/junction/dir1/dir2/"
<Directory "//192.168.0.10/nas/junction/dir1/dir2">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
[Thu Mar 27 22:24:03 2003] [error] [client 67.67.67.117]
Forbidden: //192.168.0.10/nas/junction doesn't point to a file or directory
If FollowSymLinks is turned off, then:
[Thu Mar 27 23:24:07 2003] [error] [client 67.67.67.117] Symbolic link not
allowed: //192.168.0.10/nas/junction
Either way, with indexing turned on and using the following mapping, Apache
browses the directory fine, and generates an index, but does not see ANY of
the junctions:
Alias /nas/ "//192.168.0.10/nas/"
<Directory "//192.168.0.10/nas">
Options Indexes FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
It sees regular folders and files just fine.
NFTS can create at least two common types of junctions. One is the MountVol
target format shown in Sam's bug report, and the other is a path reference as
created with "linkd.exe" from Win2K Resource Kit. The above behavior is
observed with BOTH types.
I have rated this as MAJOR because without fixing this, Apache cannot be used
to serve content from servers in a web farm that all work from a NAS server
that mounts many RAID arrays using the "MountVol" or "LinkD" method. While
the LinkD method is uncommon, the MountVol method is offered in default
Windows GUI Drive Management on volume creation, and is a common way to add
new volumes into an existing path structure.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org