-
Notifications
You must be signed in to change notification settings - Fork 51
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
URL encoding issue #125
Comments
Hello :> Currently, the log does not decode URLs, because this can make debugging more difficult. If there is an issue with a HTTP-Client failing to access a file, then it is more useful to have the original request for exact analysis. But I realize that this can be an inconvenience for languages which are primarily non-ASCII, so maybe there should be a config option to decode URLs before displaying them in the log. Or, maybe it should always log both the original encoded URL and then also the decoded URL... I'll think about this, because it can be dangerous. On some platforms, decoding and displaying a malicious URL in a terminal can lead to RCE, so we must be careful: OSC9;7 For now, if you need to decode a specific URL, for example this:
...then you can do the following:
Let's keep this issue open so the auto-decode option can be considered 👍 |
Thank you for your reply. I roughly understand what you mean. I hope there will be a better solution to make copyparty more useful. |
Alright, copyparty will now decode and print URLs if they contain any percent-encoded characters:
I am not sure when the next release will be, so I have attached a beta: thank you for the idea, and please let me know if you encounter any further issues 👍 |
Thank you for your efforts, and we look forward to the early release of a complete and stable version! |
After testing it, it seems to work very well. At least the server-side logs can be read better. |
May I ask how to encode the URL in the image and display it as normal Chinese content? Thank you and I look forward to your reply!
The text was updated successfully, but these errors were encountered: