[twsocket] FTPClient and strange behaviour
>>> If authentication is required to issue a command the server should >>> send an error code, typically 530. >> Okay, will pay attention to it. Is there any short overview of the >> FTP-protocols available? Afaik the RFCs are a bit longish I fear. > > RFCs are the standards, there's no way around. Yes and no. I did hope that there is a simple chart where you can read out easily the required sequence for such simple tasks as mine. > >>> In order to set transfer mode you must set property BinaryMode to >>> TRUE as well as issue command TypeSet to send the transfer type >>> command to the server. Same when switching back to ascii except >>> property BinaryMode must be set to FALSE before issuing the TypeSet >>> command. >> Okay, didn't know that. Will try out that typeset command. But why has >> FtpCli a property for transfer mode then anyway? > > It's easier having a boolean instead of recalling parameters of > char 'I' and 'A'. Huh? I don't understand that. What I meant is, that it should set it automatically for the server if I can set it that way in the component. So I hadn't run into that trap of not sending the typeset command. > >>> Very unlikely, try to upload with FtpTst demo first. If that works >>> the problem should be in your code. >> I've tried that and the very same happens here! > > Is the server buggy? Which FTP server are you using? I'll report that, but' I'm on the wrong PC just now and have not much time right now. Greetings Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTPClient and strange behaviour
Markus Humm wrote: >> If authentication is required to issue a command the server should >> send an error code, typically 530. > > Okay, will pay attention to it. Is there any short overview of the > FTP-protocols available? Afaik the RFCs are a bit longish I fear. RFCs are the standards, there's no way around. >> In order to set transfer mode you must set property BinaryMode to >> TRUE as well as issue command TypeSet to send the transfer type >> command to the server. Same when switching back to ascii except >> property BinaryMode must be set to FALSE before issuing the TypeSet >> command. > > Okay, didn't know that. Will try out that typeset command. But why has > FtpCli a property for transfer mode then anyway? It's easier having a boolean instead of recalling parameters of char 'I' and 'A'. >> Very unlikely, try to upload with FtpTst demo first. If that works >> the problem should be in your code. > > I've tried that and the very same happens here! Is the server buggy? Which FTP server are you using? --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > I'll try the mentioned things above (might take some days) and report > back. > > Greetings > > Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] FTPClient and strange behaviour
Hello, > Markus Humm wrote: >> I've tried the FTPTst Application right now and found out that a PASS >> is required after a open, it will delete the file then. But why >> didn't the server tell me in my program and always claimed to have >> carried out my delete request? > > If authentication is required to issue a command the server should send > an error code, typically 530. Okay, will pay attention to it. Is there any short overview of the FTP-protocols available? Afaik the RFCs are a bit longish I fear. > >> Doesn't really matter, because the put still only works for the second >> time. > > No problem here using FtpTst demo and FileZilla server. > >> As I noticed he tries to open a binary connection although I >> left "binary mode" unchecked. > > In order to set transfer mode you must set property BinaryMode to TRUE > as well as issue command TypeSet to send the transfer type command to > the server. Same when switching back to ascii except property BinaryMode > must be set to FALSE before issuing the TypeSet command. Okay, didn't know that. Will try out that typeset command. But why has FtpCli a property for transfer mode then anyway? > >> What's happening here? I'll need a >> binary transfer later, but not at this time. >> >> Why the need of a 2nd put? Why does the first one fail? Is it my >> FTPServer? > > Very unlikely, try to upload with FtpTst demo first. If that works > the problem should be in your code. I've tried that and the very same happens here! I'll try the mentioned things above (might take some days) and report back. Greetings Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTPClient and strange behaviour
Markus Humm wrote: > > I've tried the FTPTst Application right now and found out that a PASS > is required after a open, it will delete the file then. But why > didn't the server tell me in my program and always claimed to have > carried out my delete request? If authentication is required to issue a command the server should send an error code, typically 530. > > Doesn't really matter, because the put still only works for the second > time. No problem here using FtpTst demo and FileZilla server. > As I noticed he tries to open a binary connection although I > left "binary mode" unchecked. In order to set transfer mode you must set property BinaryMode to TRUE as well as issue command TypeSet to send the transfer type command to the server. Same when switching back to ascii except property BinaryMode must be set to FALSE before issuing the TypeSet command. > What's happening here? I'll need a > binary transfer later, but not at this time. > > Why the need of a 2nd put? Why does the first one fail? Is it my > FTPServer? Very unlikely, try to upload with FtpTst demo first. If that works the problem should be in your code. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > Greetings > > Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] FTPClient and strange behaviour
> Message: 3 > Date: Sun, 2 Jul 2006 21:38:06 +0200 > From: "Arno Garrels" <[EMAIL PROTECTED]> > Subject: Re: [twsocket] FTPClient and strange behaviour > To: "ICS support mailing" > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Markus Humm wrote: > >> > When I try to delete the file I want to send first from the FTP server >> > it always says it has been deleted, but the file is still in the >> > directory of the server?! What's happening there? The statuscode sent >> > back by the server is 250. >> > >> > When I try to send my file to the server I need to 'put' it twice, the >> > first time it gives me a "425 Can't open data connection." (so >> > statuscode is 425) but the second time the file get's send okay. > > Are you able to reproduce the problem using the FTP demo, FtpTst.dpr? > > --- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html I've tried the FTPTst Application right now and found out that a PASS is required after a open, it will delete the file then. But why didn't the server tell me in my program and always claimed to have carried out my delete request? Doesn't really matter, because the put still only works for the second time. As I noticed he tries to open a binary connection although I left "binary mode" unchecked. What's happening here? I'll need a binary transfer later, but not at this time. Why the need of a 2nd put? Why does the first one fail? Is it my FTPServer? Greetings Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] FTPClient and strange behaviour
Markus Humm wrote: > When I try to delete the file I want to send first from the FTP server > it always says it has been deleted, but the file is still in the > directory of the server?! What's happening there? The statuscode sent > back by the server is 250. > > When I try to send my file to the server I need to 'put' it twice, the > first time it gives me a "425 Can't open data connection." (so > statuscode is 425) but the second time the file get's send okay. Are you able to reproduce the problem using the FTP demo, FtpTst.dpr? --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] FTPClient and strange behaviour
Hello, I'm using D2006, ICS 5 (from the Partner DVD) and Windows XP professional with a lightwight FTP-Server. I'm writing some application which is to be used to maintain a website later and for this a html-file is created on the local PC and should be transferred to the webserver using FTP. I can connect and disconnect without problems from the local FTP-Server used for development but deleting files and sending files gives me some irritations. When I try to delete the file I want to send first from the FTP server it always says it has been deleted, but the file is still in the directory of the server?! What's happening there? The statuscode sent back by the server is 250. When I try to send my file to the server I need to 'put' it twice, the first time it gives me a "425 Can't open data connection." (so statuscode is 425) but the second time the file get's send okay. As Transfermode I use text not binary, since I think that's okay for a html-file. What's happening here? Is this normal, or my little FTP-Server or does my application not yet comply to FTP-standards? Greetings Markus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
