Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1692 closed Bug (invalid)

Troubles with trackers without scrape features

Reported by: NatanFrei Owned by:
Priority: High Milestone: None Set
Component: Transmission Version: 1.42
Severity: Major Keywords: scrape
Cc:

Description

Good <part of day>!

I've seen mass trouble with Transmission with private popular trackers, which have no scrape feature. It means: announce/announce.php exists, but scrape/scrape.php absent.

Trouble when scrape absent(blank file for example):

IP - - [13/Jan/2009:05:12:57 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 5 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:05:12:57 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 5 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:09:29:16 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 5 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:09:29:16 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 5 "-" "Transmission/1.42 (7494)"

Tracker have no announce requests

No troubles when scrape exists and works:

IP - - [13/Jan/2009:18:01:34 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:01:35 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:07:56 +0300] "GET /announce.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94&peer_id=-TR1420-3flosc95dpyr&port=51413&uploaded=0&downloaded=579544621&corrupt=0&left=810139648&compact=1&numwant=80&key=jfds3fi4fx HTTP/1.1" 200 121 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:16:43 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:16:50 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:20:30 +0300] "GET /announce.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E&peer_id=-TR1420-m3ka7h1un59x&port=51413&uploaded=0&downloaded=0&corrupt=0&left=2058797056&compact=1&numwant=80&key=upkk9wfvmc HTTP/1.1" 200 121 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:31:57 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:32:00 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:43:30 +0300] "GET /announce.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94&peer_id=-TR1420-3flosc95dpyr&port=51413&uploaded=0&downloaded=602512829&corrupt=0&left=787169280&compact=1&numwant=80&key=jfds3fi4fx HTTP/1.1" 200 121 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:47:07 +0300] "GET /scrape.php?info_hash=%5C%D8%2C%1A%3D%84%FDC%99%FD%DCMV%17%F8Jm%FB%E8%5E HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"
IP - - [13/Jan/2009:18:47:16 +0300] "GET /scrape.php?info_hash=%B8%E7%CE2%5E%B9%87%90%ACY%C4%9DMmn%05%8C4%5D%94 HTTP/1.1" 200 93 "-" "Transmission/1.42 (7494)"

I can see scrape and announce requests

As I can understand this situation, scrape required for normal working Transmission. But in real world it is not so.

I have seen #765 about it. May be is it possible to add new functionality like "Disable Scrape"?

I know only russian links with mass discussion of this trouble :(

Change History (5)

comment:1 Changed 13 years ago by charles

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

The trackers are not following the BitTorrent? spec and need to fix their software. The spec details out how a tracker can specify, via how they form their announce URL, whether or not the tracker supports scrape.

http://wiki.theory.org/BitTorrentSpecification#Tracker_.27scrape.27_Convention

comment:2 follow-up: Changed 13 years ago by NatanFrei

I understand that. But as U can see at URL with specification:

By convention most trackers support another form of request, which queries the state of a given torrent (or all torrents) that the tracker is managing.

Most not all.

I understand, that U want prepare "true" software, but most torrents clients can work perfectly without scrape, because there are trackers without scrape in real life, and people want use it, because these trackers are very popular.

Currents situation: MacOS users need torrent client for these popular trackers. I think U interested in more Transmission users, and it will be so, if U will add feature as "Disable scrape"

comment:3 Changed 13 years ago by livings124

I'm not going to say I understand that reply completely, but charles is correct: the BitTorrent? specs state how I tracker has to form its url if it supports/does not support scrapes, and Transmission follows these rules. You should be reporting your bug to the tracker, no here.

comment:4 Changed 13 years ago by charles

  • Milestone changed from 1.50 to None Set

comment:5 in reply to: ↑ 2 Changed 13 years ago by charles

Replying to NatanFrei:

I understand that. But as U can see at URL with specification:

By convention most trackers support another form of request, which queries the state of a given torrent (or all torrents) that the tracker is managing.

Most not all.

You're selectively quoting the spec. The part you quote goes on to say:

If the text immediately following that "/" isn't "announce" it will be taken as a sign that that tracker doesn't support the scrape convention. If it does, substitute "scrape" for "announce" to find the scrape page.

Note: See TracTickets for help on using tickets.