httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8014] - Apache cannot handle NTFS mounted volumes
Date Thu, 18 Apr 2002 10:16:50 GMT
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 mounted volumes

sam@netcity.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From sam@netcity.co.uk  2002-04-18 10:16 -------
Reopening, with more information:

Snippet from httpd.conf:
   Alias /C "C:/"
   <Directory 
"C:/">
      Options Indexes FollowSymLinks MultiViews
      AllowOverride None
      Order 
allow,deny
      Allow from all
   </Directory>

Requesting 
http://localhost/C/Documents%20and%20Settings/ returns a listing
of the directory, but 
with the expected "Sam/" entry (C:\Documents and
Settings\Sam\ is actually a mount point) 
omitted. Instead, "[error] [client
127.0.0.1] symlink doesn't point to a file or directory: 
C:/Documents and
Settings/Sam" appears in the error log.

Requesting 
http://localhost/C/Documents%20and%20Settings/Sam/, or anything
inside of it, returns a 
403 error and likewise adds "[error] [client
127.0.0.1] symlink doesn't point to a file or 
directory: C:/Documents and
Settings/Sam" to the error log.

Requesting 
http://localhost/C/Documents%20and%20Settings/All%20Users/ or any
of the other links 
from the directory listing works as it should.

After doing some reading, it appears that what 
Apache calls symlinks on
Windows are actually NTFS Junctions; most junctions have a target of 
a
regular pathname (such as "C:\Target\"), but the mount point junctions
Windows uses have a 
target in the form of
"\\?\Volume{90b9a960-b928-11d5-bbf2-806d6172696f}\" (the classid is 
the
volume's unique identifier).

The error message suggests that Apache is checking the 
junction target to
see if it is a valid path (which the mount point junction target is not) 
and
throwing the error. So it seems the problem lies within the code that Apache uses to check
the 
symlink/juntion target.

Mime
View raw message