Skip to content

Conversation

stehpancar
Copy link

fixed: No successful transfers were found as the text returned by FileZilla server changed for the "226" status code. (was "Transfer OK" now is "Successfully transferred")
fixed: By now FileZilla_Server (0_9_54) produces utf-8 log files. Decoding

Somwhere between FileZilla_Server-0_9_24 and FileZilla_Server-0_9_54 a status
message changed from "226 Transfer OK" to "226 Successfully transferred".
See ControlSocket.cpp of FileZilla_Server.
Now successful transfers are found again.
@Stunner
Copy link
Owner

Stunner commented Jan 14, 2016

Thanks for the pull request! I am wondering if opening the log files with utf-8 encoding will work for log files generated by older versions of FileZilla Server.

@stehpancar
Copy link
Author

This depends on the encoding FileZilla Server used back then. If it used plain US-ASCII for storing assuming utf-8 when opening should work. I believe the same is true for latin1 (aka "ISO 8859-1"). https://en.wikipedia.org/wiki/ISO/IEC_8859-1

If it used the system encoding of windows. Things will be tricky. https://en.wikipedia.org/wiki/Mojibake
I think there is no simple solution. A work around would be to add a command line switch that a user can use to specify the encoding that was used when the file was stored. Guessing would always be problematic.

@github-staff github-staff deleted a comment from maulanaayub May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants