Opened 12 years ago

Closed 12 years ago

#2869 closed Enhancement (invalid)

More descriptive tracker announce/scrape error messages

Reported by: gn0s1s Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.83
Severity: Normal Keywords: tracker, error, announce, scrape


When an announce or scrape fails, it would be useful to know why. Right now some announces/scrapes time out because the domain didn't resolve, others because the tracker is too busy and can't respond. Knowing exactly at which step of the process Transmission was when the error occurred will help the user get rid of dead trackers (thus saving Transmission from trying to connect fruitlessly to them) and/or help users and developers understand exactly what's happening in that specific case.

So something like: Announce timed out. vs. Tracker domain does not resolve. (Along with other useful messages if there are other ways in which the announce can fail.)

Thanks again for all your work!

Change History (3)

comment:1 Changed 12 years ago by gn0s1s

s/"Tracker domain does not resolve."/"Tracker hostname does not resolve."

comment:2 Changed 12 years ago by gn0s1s

Another tracker resolved but returned the message "Invalid Request" within the <title> tags, might be worth passing through.

comment:3 Changed 12 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

Actually the more I look into this the less I think it might actually be useful. DNS servers often return some nonsense IP address for unresolvable hostnames, so even if we do try to provide helpful DNS error messages, a lot of the errors are going to slip through the cracks. That's what I got when I tried a rough draft of code for this feature.

Note: See TracTickets for help on using tickets.