Changes between Initial Version and Version 1 of Ticket #9089, comment 1


Ignore:
Timestamp:
Jul 27, 2016, 11:31:01 PM (8 years ago)
Author:
Darcy

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9089, comment 1

    initial v1  
     1You seem to have reformatted your display in here, making my description harder to understand.  So I'll repost some of it here in code-block form, to preserve it.
     2
     3The example of the remote-server syntax expected in Novell's FTP implementation should be:
     4
     5{{{
     6cwd //server/volume/dir/subdir
     7}}}
     8
     9And later statements, similarly:
     10
     11{{{
     12But when FileZilla (3.7.3) sees such a syntax (through pwd output), or when you enter
     13a path into Filezilla's "remote site" field, such as "//server1/volume1/path/"
     14Filezilla often strips off the first '/' character.
     15}}}
     16
     17and
     18
     19{{{
     20Because of this, anytime Filezille wants to reference the absolute path in a command,
     21it references "/server1/..." instead of "//server1/...".
     22}}}
     23
     24and from the log section:
     25
     26{{{
     27Command: PWD
     28Response: 257 "//dp-sles11sp2/VOL1\sub2" is your current location
     29}}}
     30
    131Additional data about the log shown in the initial description:
    232
    3 This is a log of a quick connection session, where it logged in fine, and the session was put in home directory //dp-sles11sp2/VOL1/sub2.  Then I attempted to upload file "add5.pdf".  The rest of the commands shown were all automatically generated by Filezilla in it's attempts to upload that file, or to auto-recover from the failures happening.  Filezilla kept trying to use absolute paths beginning with /dp-sles11sp2 (which fail) instead of //dp-sles11sp2 (which would have succeeded).
     33This is a log of a quick connection session, where it logged in fine, and the session was put in home directory
     34
     35{{{
     36//dp-sles11sp2/VOL1/sub2
     37}}}
     38
     39Then I attempted to upload file "add5.pdf".  The rest of the commands shown were all automatically generated by Filezilla in it's attempts to upload that file, or to auto-recover from the failures happening.  Filezilla kept trying to use absolute paths beginning with /dp-sles11sp2 (which fail) instead of {{{//dp-sles11sp2}}} (which would have succeeded).
    440
    541I have also seen other Filezilla client installations (diff versions?) where it attempted "STOR /server1/vol1/path/file" which failed, when it could have succeeded with either:
    642
     43{{{
    744STOR //server1/vol1/path/file
     45}}}
    846or simply with:
     47{{{
    948STOR file
     49}}}
     50
    1051(This would work since the current directory was already at the desired path.  The redundancy of using absolute path isn't usually necessary.)