I just created a content 'directory listing' on a windows XP system with a path of C:\ which had the following problem as a result (the directory listing itself looks fine):

Clicking on any entry causes a 404 error. I can only assume that it has to do with an additional unneeded slash (/), e.g "http://localhost/?q=C:\/boot.ini" instead of "http://localhost/?q=C:\boot.ini". Currently the file itself is not displayed, for example I would expect the adobe reader to open when clicking on a PDF file within the directory.

Also, when browsing into subdirectories, there is no way to get up one level again (by using a .. e.g.). Currently I can only use the back button of the browser.

Comments

Anonymous’s picture

Anonymous (not verified) commented

Also, when browsing into subdirectories, there is no way to get up one level again (by using a .. e.g.). Currently I can only use the back button of the browser.

Use the breadcrumbs instead with an appropriate theme.

FrankT’s picture

FrankT commented

OK, I'm not too deep into breadcrumbs but I will check it.

What about the wrong slashes? If it is intended to open files within a directory listing, then this has to bee fixed (at least for windows systems)!

Okami-1’s picture

Okami-1 commented
Version: 6.x-2.0-beta2 » 6.x-1.4
Assigned: Unassigned » Okami-1
Priority: Normal » Critical

Having the exact same problem on mine as well:

Page not found
The requested page could not be found.

http://www.mysite.com/drupal/?q=C%3A\root\my%20music/demo.mp3

and that the url path it gives

clean urls is not on and nor do i want it on, and im not sure there is another 6.x compatible file share out there that will work with a mobile theme aswell like this one........

Susurrus’s picture

Susurrus commented
Status: Active » Closed (won't fix)

Alright, the path you need to enter into the nodes is relative to the home directory for your Drupal installation. I have my drupal installation in "C:\Apache2\drupal6". To access the C:\ drive I then have to enter "../../" as my path to show the contents of the C:\ directory. As of right now, private downloads have not been implemented, so accessing the actual files in those paths will not work.

This is something I will be exploring shortly, but access to any files outside of the webserver root (in my case "C:\Apache2") is not guaranteed to be possible and I would say it will always be unsupported by this module. What you'd want to do is create a link to whatever directory you want to link to within the webserver root (on *NIX it's called an alias) that you could then use as a gateway to those otherwise inaccessible files.

Since I don't plan to support this feature except by using the workaround mentioned above (which is the normal way to deal with this situation), I'm labeling this a won't fix.