Bug 52043 - Directories ".", "..", and "/" do not work correctly with "ls" command
Summary: Directories ".", "..", and "/" do not work correctly with "ls" command
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_ftp (show other bugs)
Version: 2.2.21
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-10-17 18:24 UTC by Philip Pickett
Modified: 2018-11-07 21:09 UTC (History)
2 users (show)

Patch file to address shortcomings in mod_ftp "ls" command handling (454 bytes, patch)
2011-10-17 18:24 UTC, Philip Pickett
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Pickett 2011-10-17 18:24:05 UTC
Created attachment 27799 [details]
Patch file to address shortcomings in mod_ftp "ls" command handling

The FTP client commands "ls .", "ls ..", and "ls /" do not work in a way consistent with the unix shell commands.

From the top-level FTP directory, a "550" status "No such file or directory" is returned for each of these.  From a subdirectory one-level deep on the FTP server, the "ls ." shows the contents of the current directory while "ls .." and "ls /" still return the 550 status.  From a subdirectory two or more levels deep, "ls ." and "ls .." work but "ls /" returns a 550.

With the attached patch incorporated and built, the commands "ls .", "ls ..", "ls /", as well as  "ls ./<someDirectory>", "ls ../<someDirectory>", "ls /<someDirectory>", and ls <someDirectory> work in a way consistent with the linux/unix shell "ls" command for the testing I've done.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:03 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.