Skip to content

Ftp algs command#573

Open
JPeterMugaas wants to merge 2 commits intoIndySockets:masterfrom
JPeterMugaas:ftp_algs_command
Open

Ftp algs command#573
JPeterMugaas wants to merge 2 commits intoIndySockets:masterfrom
JPeterMugaas:ftp_algs_command

Conversation

@JPeterMugaas
Copy link
Contributor

Command specified by:
https://www.rfc-editor.org/rfc/rfc6384.html#section-11

FTP servers (as opposed
to ALGs) MUST NOT perform any actions upon receiving the ALGS
command. However, FTP servers MUST still send a response. If FTP
servers recognize the ALGS command, the best course of action would
be to return a 202 response:

  202 Command not implemented, superfluous at this site

@rlebeau rlebeau added Type: Enhancement Issue is proposing a new feature/enhancement Element: FTP Issues related to FTP handling, TIdFTP and TIdFTPServer, etc Status: Reported Issue has been reported for review labels Dec 16, 2024
@rlebeau
Copy link
Member

rlebeau commented Dec 16, 2024

Is this really needed? That same RFC says:

However, there is no reason for FTP servers to specifically recognize this command; returning any 50x response that is normally returned when commands are not recognized is appropriate.

Which is exactly what TIdFTPServer already does. By default, it will send a 500 'ALGS': command not understood reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Element: FTP Issues related to FTP handling, TIdFTP and TIdFTPServer, etc Status: Reported Issue has been reported for review Type: Enhancement Issue is proposing a new feature/enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants