[ZCM] [ZC] 1624/ 1 Request "FTP RNFR should not succeed if the resource does not exist"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1624 Update (Request) "FTP RNFR should not succeed if the resource does not exist"
 Status Pending, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1624

==============================================================
= Request - Entry #1 by Anonymous User on Dec 16, 2004 4:30 am

The FTP interface always returns a success status (350) on a RNFR, deferring the actual decision on wether the rename is going to succeed to the RNTO that usually follows. DreamWeaver, however, uses the RNFR command to test wether the target resource actually exists, and since this always returns success, goes into an infinite loop trying to find a non-existant name for a new resource to create. Using RNFR to test for existance is a pretty good apprach given that FTP doesn't offer all that much functionality in this regard; the only other way I see to test for existance is parsing the output of LIST (which most other clients do) and (mis)using RNFR this way is more robust. Having RNFR return 550 for non-existant resourced would solve this issue, and seems in line with the FTP RFC, although I must admit it's a bit vague on what would be expected from the server in this particular instance.
==============================================================