You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm assigned to perform #213, which asks for a FTP endpoint implementation.
Design wise, I believe all we need to do is within the s3auth-relay module. Our architecture is coherent enough to separate the protocol communications in s3auth-relay to the actual resource access in s3auth-hosts. Basically, all the FTP support needs to be in s3auth-relay, is this right?
A more important question to me is what is the "minimum" that we need to implement so that we can say that we "support" FTP, if not fully? I'm not very familiar to the internals of the FTP protocol so some guidance on this matter would be of great assistance.
The text was updated successfully, but these errors were encountered:
You're right, we have to implement it inside s3auth-relay. I would start with a test.. Create a test that will use a real FTP client and will try to do a few basic FTP commands, in this order:
OPEN ftp://maven.s3auth.com
USER s3auth s3auth
CD apidocs
LIST
GET index.html
QUIT
Actually, that's all we need to support: OPEN, USER, CD, LIST, GET, QUIT
I'm assigned to perform #213, which asks for a FTP endpoint implementation.
Design wise, I believe all we need to do is within the
s3auth-relay
module. Our architecture is coherent enough to separate the protocol communications ins3auth-relay
to the actual resource access ins3auth-hosts
. Basically, all the FTP support needs to be ins3auth-relay
, is this right?A more important question to me is what is the "minimum" that we need to implement so that we can say that we "support" FTP, if not fully? I'm not very familiar to the internals of the FTP protocol so some guidance on this matter would be of great assistance.
The text was updated successfully, but these errors were encountered: