Closed Wiilf closed 3 years ago
Confirmed, this change alone has my private torrents connecting with no problems! I suggest the above changes to the main repo, due to the fact that a lot of trackers are using reverse-DNS (Cloudflare, FreeDNS(afraid.org), DynDNS, etc).
I've used this as well
httpClient.DefaultRequestHeaders.ConnectionClose = false;
Not sure why you use different httpClient everytime. I've updated the repo but with the same httpClient, let me know if that is causing any issues
Following your existing code. With those changes, although should be called with a procedure imo broke user agent reporting. NULL.
I've revised and separated some logic. Working as expected.
*Additionally, and separately - this codebase needs to see uploading capability right away. This is a grand staple of BitTorrent.
We will work to see this implemented, will not be easy I think due to limited skill in this particular language.
@Wiilf, I find it difficult to understand you. So, with the current implementation user agent is not working?
"I've revised and separated some logic. Working as expected."
So you had to do some changes to fix it and if yes can you create PR or share the fix?
"*Additionally, and separately - this codebase needs to see uploading capability right away. This is a grand staple of BitTorrent."
You mean that uploading/seeding is important to implement? I agree, however that requires time effort that I currently don't have.
Added some options our other downloader classes uses, transfers work fine. May need tuning. C#9
Tracker.cs
using System.Security.Authentication;