When FTP servers send multi-line responses, there is a strict syntax it must obey (like with pretty much every FTP command and response).
All lines of the multi-line response, except the last, use a dash separator. The last uses a space as ''closing tag''. Example:
If your log is complete, and you didn't mix up multiple simultaneous connections, then the server started a multi-line response but never finished it. FileZilla expects further lines, then the server sends a different response. This violates and disturbs the challenge-response sequence and causes FileZilla to error out.
But as you can see from the log snippet I code-quoted above, the transfer of the PDF was successful. So, is the file on the server in one piece (size must be the same since it is binary)?
All lines of the multi-line response, except the last, use a dash separator. The last uses a space as ''closing tag''. Example:
Code:
226-First line
226-Second line
226-Third line
226 Last line
226-Second line
226-Third line
226 Last line
If your log is complete, and you didn't mix up multiple simultaneous connections, then the server started a multi-line response but never finished it. FileZilla expects further lines, then the server sends a different response. This violates and disturbs the challenge-response sequence and causes FileZilla to error out.
But as you can see from the log snippet I code-quoted above, the transfer of the PDF was successful. So, is the file on the server in one piece (size must be the same since it is binary)?
