Menu ▾ ▴

#676 ftp::List problem on Windows

open
Gerald W. Lester
ftp (55)
5
2005-09-30
2005-09-29
Christophe De Clercq
No

When connection to a windows server
whith ftp::Open ...

Then:
ftp::List $h "filename-which-does-not-exists"
--> error error | E: Error receiving list!

When I add try with "x*" no problem.
An empty string is returned: meaning no file starting
with x.

When I connect to a Solaris server:
ftp::List $h "filename-which-does-not-exists"
works fine (without adding the *)

Discussion

  • Andreas Kupries

    Andreas Kupries - 2005-09-30
    • labels: --> ftp
     

  • Andreas Kupries

    Andreas Kupries - 2005-09-30
    • assigned_to: nobody --> gwlester
     

  • Andreas Kupries

    Andreas Kupries - 2006-10-02

    Logged In: YES
    user_id=75003

    So the Windows and Solaris ftp server generate different
    outputs in response to the request, right ?

    Please try to capture the commands sent by the package, and
    responses received, and attach the resulting log to this report.

    Note: We recently fixed a problem in NLIst regarding the
    handling of 'spaces' in filenames. Could this be a similar
    problem ?

    I.e. not a true difference between the windows/solaris
    servers, just filenames with spaces in them returneed by the
    windows server ? This can be tested by creating some files
    with spaces in their name on solaris and making sure that
    the solaris server sees them ... I think.

     

  • Christophe De Clercq

    Christophe De Clercq - 2006-10-03

    example and output (failing and success example)

     
    list_problem.tcl

  • Christophe De Clercq

    Christophe De Clercq - 2006-10-03

    Logged In: YES
    user_id=617750

    I do not think it has anything todo with the 'spaces' problem.

    I noticed in the output that the return-code with the ftp
    list command was
    226 on solaris - Closing data connection. Requested file
    action successful (file transfer, abort, etc.).

    550 on IIS - Requested action not taken. File unavailable
    (e.g., file not found, no access).

    Thanks for the effort!

     

  • Andreas Kupries

    Andreas Kupries - 2006-10-03

    Logged In: YES
    user_id=75003

    Uh. In other words, the windows server sends a failure
    status code when you try to list non-existing files, whereas
    the solaris server is happy to report that it is happy, the
    list of matching files is simply empty.

    And the ftp package in turn is not happy with the failure
    status reported by windows. :(

    I had hoped it was something quickly fixed for the release.
    Now I am not sure. Ok, no fix for this release.