-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extra end of line in (M)LIST potentially breaks clients #64
Labels
Comments
I can'n find a description of the LIST output format.... But proftpd does't add CRLF to the end of LIST-response. [Need more research] |
I'm looking at RFC3659 and the examples of MLST/MLSD responses look like this:
and the spec says:
and that seems to also indicate that there should be no extra |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
goftp
to do aLIST
on the sampleftpserver
(both with the versions on tip), I discovered that these extraCRLF
s result in parsing errors (also on L152 for MLIST):https://github.com/fclairamb/ftpserver/blob/e240d7906ab840a805aabde615025b56ffbb4cf7/server/handle_dirs.go#L144
Unsure what the standard says — if this is something that the client should accept or if this should be fixed here?
Repro
yields
The text was updated successfully, but these errors were encountered: