Re: FTP Successful completion

Thank you!






From: "Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxxxxxxxx
Date: 22/09/2023 11:42 AM
Subject: Re: FTP Successful completion
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



A quote from RFC 959, section 4.2:

Thus the format for multi-line replies is that the first line
will begin with the exact required reply code, followed
immediately by a Hyphen, "-" (also known as Minus), followed by
text. The last line will begin with the same code, followed
immediately by Space <SP>, optionally some text, and the Telnet
end-of-line code.

https://datatracker.ietf.org/doc/html/rfc959

On 9/21/2023 7:54 PM, Don Brown via MIDRANGE-L wrote:

Thanks Scott,

I checked the log again - see below.

I will have to read the RFC again as I did not see anything indicating

the

continuation using the hyphen.

So I am still thinking that if the first 4 characters are 226b where
b-Blank the transfer is successful.


226-Warning: client is in ASCII mode - Assuming data is plain text
226-File successfully transferred
226 0.027 seconds (measured here), 2.94 Mbytes per second
83220 bytes transferred in 0.060 seconds. Transfer rate 1397.005

KB/sec.

Thank you for the explanation.

Cheers

Don





From: "Scott Klement"<midrange-l@xxxxxxxxxxxxxxxx>
To: "Don Brown via MIDRANGE-L"<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 22/09/2023 10:19 AM
Subject: Re: FTP Successful completion
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



Don,

The - means that it's continued on the next line. For example:

226-Everything is great
226 Now it's done.



On 9/21/2023 4:39 PM, Don Brown via MIDRANGE-L wrote:

Thanks Charles,

Yes we do use FTPAPI and yes it does work great.

This was a support ticket at 5:30 pm and needed to be fixed.

I just added another constant to the list to check for successful
completion to get the problem solved.

But it seemed like a brute force and ignorance fix and led me to search
the FTP completion codes (
https://en.wikipedia.org/wiki/List_of_FTP_server_return_codes)

Which led me to my question.

And this was new - all FTP message logs I have seen always had a blank
after the code Eg 999b where b=blank this message was 226-

I do appreciate the response - tank you

Cheers

Don





From: "Charles Wilt"<charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 21/09/2023 11:45 PM
Subject: Re: FTP Successful completion
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



As Scott mentions in the intro to his FTPAPI tool..
https://www.scottklement.com/ftpapi/

"After attempting to write a few programs that send files in "batch"

mode,

I discovered that properly detecting errors in batch mode was not fun."

I'd highly recommend migrating to FTPAPI over trying to scan the log.
It's easy to use and reliable.

Charles

On Thu, Sep 21, 2023 at 3:21 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I just resolved a problem with a program using ftp to retrieve a file
where the log was read and was checking for more than just 226.

The program had constants for different completion messages like

226-File successfully transferred
226 Success
etcetera

The web pages I have looked at for ftp completion codes shows


226
Closing data connection. Requested file action successful (for

example,

file transfer or file abort).

So my question ...

Is checking the first 3 characters for 226 sufficient to indicate the

file

transfer was successful and processing of the retrieved data should
continue.

Thanks

Don



--
This email has been scanned for computer viruses. Although MSD has

taken

reasonable precautions to ensure no viruses are present in this email,

MSD

cannot accept responsibility for any loss or damage arising from the

use

of

this email or attachments..
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.