On 6/9/06, Jason McCarty <address@hidden> wrote:
No, but a while back a had a problem that looks like the same root
cause. This was with larch, however, not tla. I'll quote an old message
of mine, written June 22, 2003 to the old
address@hidden
list, message-id address@hidden :
[...]
I think this is because Microsoft's FTP server has a buggy NLST
command:
Client: NLST /bclg/wwwiup/{archives}/test
Server: /bclg/wwwiup/{archives}/test\=meta-info
First, it doesn't include dotfiles in its output. Second, it uses a
backslash as the final path delimiter.
[...]
I can't offer you access to my account, but perhaps Stefan can confirm
if this is the problem via tcpdump or otherwise. Probably other FTP
clients have a workaround for this problem we could employ. I recall
NcFTP in particular as being able to list those files (though NcFTP is
under some artistic license, not GPL).
Thank you very much for the information. I hope Stefan can verify if this is indeed the problem (and it seems likely).
If so, then it is time to explore working around the wonderful world of Microsoft FTP...