Re: FTP strangeness

Thanks for that info, I have passed it on to the SmartFTP support (without
names!) to see if that helps them sort this out for VMS.

Cheers

<david20@xxxxxxxxxxxxxxxx> wrote in message
news:eejp7r$ps9$1@xxxxxxxxxxxxxxxxxxxx
In article <12gmuf2rbaj5d4@xxxxxxxxxxxxxxxxxx>, "Gremlin"
<not-here@xxxxxxxx> writes:
My reading of the RFC, possibly flawed, is that for the LIST command, 550
is
not one of the "valid" returns from the server (OVMS). Have I misread or
misunderstood this?


What permanent error reply-code (ie 5xx number) do the manufacturers of
SmartFTP suggest an ftp server should send ?

Also note that RFC 959 is NOT the final word on all things to do with FTP.
Please see RFC 1123 which states :-



"
4.1.2.11 FTP Replies: RFC-959 Section 4.2, Page 35


A Server-FTP MUST send only correctly formatted replies on
the control connection. Note that RFC-959 (unlike earlier
versions of the FTP spec) contains no provision for a
"spontaneous" reply message.



A Server-FTP SHOULD use the reply codes defined in RFC-959
whenever they apply. However, a server-FTP MAY use a
different reply code when needed, as long as the general
rules of Section 4.2 are followed. When the implementor has
a choice between a 4xx and 5xx reply code, a Server-FTP
SHOULD send a 4xx (temporary failure) code when there is any
reasonable possibility that a failed FTP will succeed a few
hours later.

"

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

is a valid RFC 959 section 4.2 reply-code and hence MAY be used when
needed.
The fact it is not listed against the LIST command in section 5.4 of rfc
959
would appear to be overridden by the above statement in RFC 1123.


David Webb
Security team leader
CCSS
Middlesex University




"Cluster-Karl" <karl.rohwedder@xxxxxx> wrote in message
news:1158316788.056323.186190@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Here is part of RFC 959:0

RFC 959 October
1985
File Transfer Protocol
550 Requested action not taken.
File unavailable (e.g., file not found, no access).

Btw. also the HGFTP client sends a 550 error.

regards Kalle





.

Relevant Pages

  • Re: FTP strangeness
    ... So, it looks like SmartFTP is off the list as a client for VMS, Cerberus ... As demonstrated more than just VMS ftp servers do the latter - for situations ... In any case an FTP client should comply with the robustness principle of RFC ... A Server-FTP SHOULD use the reply codes defined in RFC-959 ...
    (comp.os.vms)
  • Re: FTP strangeness
    ... So, it looks like SmartFTP is off the list as a client for VMS, Cerberus ... SmartFTP suggest an ftp server should send? ... Please see RFC 1123 which states:- ... A Server-FTP SHOULD use the reply codes defined in RFC-959 ...
    (comp.os.vms)
  • Re: FTP strangeness
    ... What permanent error reply-code do the manufacturers of ... Also note that RFC 959 is NOT the final word on all things to do with FTP. ... A Server-FTP SHOULD use the reply codes defined in RFC-959 ...
    (comp.os.vms)
  • Re: FTP strangeness
    ... What permanent error reply-code do the manufacturers of ... SmartFTP suggest an ftp server should send? ... A Server-FTP SHOULD use the reply codes defined in RFC-959 ... is a valid RFC 959 section 4.2 reply-code and hence MAY be used when needed. ...
    (comp.os.vms)