-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fix BEP34 bad parsing, fixes #294 #296
Fix BEP34 bad parsing, fixes #294 #296
Conversation
Dns record content is being wrapped in quotes
Thanks for the PR! This probably broke on a dnspython upgrade |
复现
随后为 本来这个功能有bug,没有正常起效果的时候是正常的,他把这个bug修复了后导致bug开始出现了 |
Yes, because it checks https first. But is it changing the url to https even if https isn't available? Because if available its preferable rather than http, but if not it's a bug. |
太好了,你理解了我在说什么,在https不可用的情况下,他依旧被错误改成https,这是一个bug,如果你有域名,可以用域名添加来进行测试 |
应该检测到内容为 TCP:1337s 才修改成https |
反馈过几次了不去修复,看来今天更新了 #304 |
很不幸经过我的测试,#304 并没有修复问题,提交tracker依旧会被修改成https,没有使用我提供的方法去更新,自然依旧有bug |
Description
Currently, there’s a bug that some people have reported regarding BP34 processing, which makes the system completely ignore whatever is in the DNS record.
This happens because the DNS resolve response returns the contents of the record wrapped in double quotes. As a result, the content string never starts with
BITTORRENT
since the first character is"
, and proceeds tracking the tracker.For example, the record text
example.com. 300 IN TXT "BITTORRENT"
is parsed as"BITTORRENT"
, which is interpreted as not valid according to BEP34 rules.Just removing trailing quotes will fix the problem.
Affects
Both of these issues are mentioned on the webpage in the FAQ section regarding tracker management, but currently, this information is not true.