Hello I had a look at the code, and I think I have to turn simpler my transfer rules concerning current directory server side... I won't change directory, it's not necessary since the STOR command can accept full pathnames So what are the naming conventions client side ? For example, if I set the homedirectory to D:/ server side, what argument should be set for STOR command at the end to be the most standard possible ? - D:/aaa/destFolder/destFile ? - /aaa/destFolder/destFile ? - aaa/destFolder/desFile ? And if someone wants to transfer a file to C:/bbb/destFolder/destFile, does the server prevent from doing that ?
Thank you -----Message d'origine----- De : Niklas Gustavsson [mailto:[EMAIL PROTECTED] Envoyé : lundi 21 avril 2008 21:22 À : Gerard Frederic Cc : [email protected] Objet : Re: homedirectory on Unix and Windows Hi On Mon, Apr 21, 2008 at 5:30 PM, Gerard Frederic <[EMAIL PROTECTED]> wrote: > First, i saw your logo :) maybe that the presence of arrows (near the > feather), reminding transfers, would be nice ? My limitations when it comes to graphics would show to much :-) I'll be happy if someone took a stab at making a proposal. > 15:18:06,715 DEBUG filesystem.NativeFileSystemView pool-2-thread-1 - > directory is </d:/testGEN/D:/apps/Secure-GEN> <<<<<<<< the problem Could you please provide a test case for this? Either if you can make it as a JUnit test like those in core src/test/java/org/apache/ftpserver/clienttests or provide a step-by-step description of how to replicate the issue? Feel free to open a JIRA issue so that we track it. > I would like to transfer file to any "device:/...." windows directory, so i > wonder if i can set homedirectory to "/" in properties for genuser to feel > more free about destinations devices ?? No, I don't believe we support that. /niklas Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
