Skip to content
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

Special Characters in Magnet Links Break the magnet #608

Closed
Endlesszombiez opened this issue May 4, 2018 · 7 comments
Closed

Special Characters in Magnet Links Break the magnet #608

Endlesszombiez opened this issue May 4, 2018 · 7 comments
Milestone

Comments

@Endlesszombiez
Copy link

I don't know if its a localized issue or a broad one; But for me if a magnet link has a special character particularly : or | then it will get stuck and never connect to peers even with 4k seeders, after a minute or so it will turn red and give the "Unable to save resume file" error or something along those lines. Editing the name of the file in the magnet link fixes this. Tried multiple different links and they all do the same.

I'm on Winx64 2.94

@vctls
Copy link

vctls commented May 31, 2018

Same here on Windows 10.
The problem seems to be that transmission is trying to create a file with the exact name included in the magnet, which fails when the name contains characters forbidden in Windows paths.
This probably won't affect Linux users.

@Endlesszombiez
Copy link
Author

Ahh so it is a broader issue than i assumed. You can manually edit/fix each link but that's very tedious. Could probably code Transmission to scan the file name for the characters to delete them.

@vctls
Copy link

vctls commented May 31, 2018

But only on windows, maybe?
Well, it wouldn't be much of a loss for Linux users to have a few characters removed from the .torrent or .resume files.
I don't know which is causing the problem, by the way.
Are there any logs?

@vctls
Copy link

vctls commented May 31, 2018

I think this is a duplicate of #61

@mikedld
Copy link
Member

mikedld commented May 5, 2020

This was probably fixed as part of #122 (see bb47410) where resume files naming was changed. Feel free to test current nightly and report back.

@Endlesszombiez
Copy link
Author

This was probably fixed as part of #122 (see bb47410) where resume files naming was changed. Feel free to test current nightly and report back.

Thank you for commenting! I got en email and decided to upgrade to the nightly to test it.
Looks like this issue is Fixed in 3.00+ (20119f0)!
Thank you!

@mikedld mikedld added this to the 3.00 milestone May 6, 2020
@mikedld
Copy link
Member

mikedld commented May 6, 2020

Closing then, thanks for testing!

@mikedld mikedld closed this as completed May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants