Changing torrent name takes effect on webseed url

letchik · July 23, 2010

Hello, everybody.

I mentioned some problem with uTorrent webseeds with multiply files torrent.

For example:

1) webseed url: "http://website.com/content/";

2) root directory name from .torrent: "Root";

3) torrent title in uTorrent: "Root";

4) download directory: "Root"

5) files: filename1.pdf,filename2.pdf etc.

uTorrent compose url for GET request like this:

1) http://website.com/content/Root/filename1.pdf

2) http://website.com/content/Root/filename2.pdf etc.

Changing download directory takes no effect, but changing torrent title in uTorrent changes composed webseed url.

If I change torrent title in uTorrent to "AnotherRoot" webseed url became like this

http://website.com/content/AnotherRoot/filename1.pdf

As on website location of data didn't changed i'll take a 404 error from webserver and peer ban in uTorrent.

I think that is not right. Root directory should be from .torrent file description and nothing else and changing description in uTorrent should takes no effect on downloading,

Firon · July 23, 2010

What version of µTorrent?

paintball9 · July 23, 2010

Just tried it out on 2.03 beta (20501) and this problem did not exist. I changed the name of the torrent and stopped/started it again, it reconnected and continued right on.

Not sure what the earliest version this works properly on is but it has been fixed.

Firon · July 23, 2010

Fantastic. And 2.0.3 is stable now. 20501 is old.

rafi · July 24, 2010

Is 20664 (latest in the changelog) "old" as well ? I've noticed 20683 is now being downloaded...

letchik · July 25, 2010

I've tried on 2.0.3 (20664) right now, problem still exists. Torrent title from list has been used to compose webseed url.

letchik · August 13, 2010

Is there any ideas for this bug? checked on 2.2 beta (build 21145) - problem still exists. I can make a screencast, if it will help you to understand what i mean.

paintball9 · August 13, 2010

Sure but I've already tried it out successfully, I'm guessing its a problem unique to you.

letchik · August 16, 2010

Ok, here is a screencast of this bug

paintball9 · August 16, 2010

That is very interesting

See here what happens on mine

[2010-08-15 23:02:03] 93.183.204.162:80(sr-aftd.iso): HTTP Connecting to: http://www.ex.ua/get/680777

[2010-08-15 23:02:04] 93.183.204.162:80(sr-aftd.iso): [nginx/0.7.67 (100.0)]: Disconnect: redirecting (1)

[2010-08-15 23:02:04] 192.168.1.101:57423(sr-aftd.iso): Connecting: source: L

[2010-08-15 23:02:04] 77.120.115.150:80(sr-aftd.iso): HTTP Connecting to: http://fs20.www.ex.ua/get/680777/sr-aftd.iso

[2010-08-15 23:02:04] 216.55.204.137:57423(sr-aftd.iso): Connecting: source: T

[2010-08-15 23:02:04] Incoming connection from 192.168.1.101:52804

[2010-08-15 23:02:04] Incoming connection from 192.168.1.1:52806

[2010-08-15 23:02:04] 192.168.1.101:52804(sr-aftd.iso): Disconnect: Same ID

[2010-08-15 23:02:04] 192.168.1.101:57423(sr-aftd.iso): Disconnect: Connection closed

[2010-08-15 23:02:04] 192.168.1.1:52806(sr-aftd.iso): Disconnect: Same ID

[2010-08-15 23:02:04] 216.55.204.137:57423(sr-aftd.iso): Disconnect: Connection closed

[2010-08-15 23:02:05] 216.55.204.137:57423(sr-aftd.iso): Connecting: source: T

[2010-08-15 23:02:05] Incoming connection from 192.168.1.1:52807

[2010-08-15 23:02:05] 192.168.1.1:52807(sr-aftd.iso): Disconnect: Banned

[2010-08-15 23:02:05] 216.55.204.137:57423(sr-aftd.iso): Disconnect: Connection closed

[2010-08-15 23:03:11] 77.120.115.150:80(sr-aftd285324.iso): HTTP Connecting to: http://fs20.www.ex.ua/get/680777/sr-aftd.iso

[2010-08-15 23:03:11] 216.55.204.137:57423(sr-aftd285324.iso): Connecting: source: T

[2010-08-15 23:03:11] Incoming connection from 192.168.1.1:52881

[2010-08-15 23:03:12] 192.168.1.1:52881(sr-aftd285324.iso): Disconnect: Banned

[2010-08-15 23:03:12] 216.55.204.137:57423(sr-aftd285324.iso): Disconnect: Connection closed

[2010-08-15 23:03:12] 216.55.204.137:57423(sr-aftd285324.iso): Connecting: source: T

[2010-08-15 23:03:12] Incoming connection from 192.168.1.1:52882

[2010-08-15 23:03:12] 192.168.1.1:52882(sr-aftd285324.iso): Disconnect: Banned

[2010-08-15 23:03:12] 216.55.204.137:57423(sr-aftd285324.iso): Disconnect: Connection closed

[2010-08-15 23:04:04] Incoming connection from 189.105.39.213:60984

You can see where I changed the name and it still connected to the server the same way

Could be this line here though

[2010-08-15 23:02:04] 93.183.204.162:80(sr-aftd.iso): [nginx/0.7.67 (100.0)]: Disconnect: redirecting (1)

It seems to redirect to a second server which stays in cache memory as the webseed file. Not sure how long it would take to clear this cache and make it load again, but from what I saw on your video, I'm guessing it would cause the same problem as yours if this didn't happen.

Before name change

[2010-08-15 23:02:04] 77.120.115.150:80(sr-aftd.iso): HTTP Connecting to: http://fs20.www.ex.ua/get/680777/sr-aftd.iso

After

[2010-08-15 23:03:11] 77.120.115.150:80(sr-aftd285324.iso): HTTP Connecting to: http://fs20.www.ex.ua/get/680777/sr-aftd.iso

This is the webseed link, Basically the same format as yours

http://www.ex.ua/get/680777

I guess it depends on the server setup whether or not this will happen.

Edit

Here I cleared the webseed list and It seemed to clear out the cache. I get the invalid URL first and then it tries again from the first server (the webseed url) Maybe nginx has some sort of special torrent redirect software built in that uses a hash rather than the name?

[2010-08-15 23:12:18] sr-aftd285324.iso: HTTP invalid URL:

[2010-08-15 23:12:24] 93.183.204.162:80(sr-aftd285324.iso): HTTP Connecting to: http://www.ex.ua/get/680777

[2010-08-15 23:12:25] 93.183.204.162:80(sr-aftd285324.iso): [nginx/0.7.67 (100.0)]: Disconnect: redirecting (1)

[2010-08-15 23:12:25] 77.120.115.150:80(sr-aftd285324.iso): HTTP Connecting to: http://fs20.www.ex.ua/get/680777/sr-aftd.iso

Either way, I agree with you now, this is definitely a bug in uTorrent. It was only this server's responses that prevented it from happening in my situation as well.

letchik · August 16, 2010

I have to notice: problem appears only for multifiles torrent. In this case uTorrent adds folder name to webseed link and it depends on title. Please try for multifiles torrent, as I see you tried on single file.

P.S. I hope it not depends on localization.

GTHK · August 16, 2010

I can confirm this, tested using http://127.0.0.1/pieman

C:\Documents and Settings\Kitsoran>nc -l -n -vv -p 80
listening on [any] 80 ...
connect to [127.0.0.1] from (UNKNOWN) [127.0.0.1] 2685
GET /pieman/ED/DVD1_packed/production/lib/textures/proog.tar.gz HTTP/1.1
Host: 127.0.0.1
User-Agent: BTWebClient/2030
Connection: keep-alive
Range: bytes=409166043-411263194
GET /pieman/ED/DVD2_packed/production/08_emo_creates.tar.gz HTTP/1.1
Host: 127.0.0.1
User-Agent: BTWebClient/2030
Connection: keep-alive
Range: bytes=19469505-21566656
sent 0, rcvd 356
C:\Documents and Settings\Kitsoran>nc -l -n -vv -p 80
listening on [any] 80 ...
connect to [127.0.0.1] from (UNKNOWN) [127.0.0.1] 2688
GET /pieman/I%20CHANGED%20THE%20GODDAMN%20NAME/DVD1_packed/production/lib/machine.tar.gz HTTP/1.1
Host: 127.0.0.1
User-Agent: BTWebClient/2030
Connection: keep-alive
Range: bytes=14791076-16888227
GET /pieman/I%20CHANGED%20THE%20GODDAMN%20NAME/DVD2_packed/production/07_emo_flips_out.tar.gz HTTP/1.1
Host: 127.0.0.1
User-Agent: BTWebClient/2030
Connection: keep-alive
Range: bytes=51249930-53347081
sent 0, rcvd 413

paintball9 · August 16, 2010

If I come across a multifile I'll give it a try, AFAIK that site doesn't host any, they have some sort of auto uploader that only does files over a certain size.

letchik · August 16, 2010

I can confirm this, tested using http://127.0.0.1/pieman

Ok, thanks. Now I sure it's not only my problem and i'm not insane at all

Maybe nginx has some sort of special torrent redirect software built in that uses a hash rather than the name?

Web-server gets only url and nothing more. According to logs utorrent just sends get request with range headers of sequential pieces emulates downloading pieces by bittorrent protocol

moogly · August 23, 2010

Any news from the devs concerning this bug?

letchik · September 24, 2010

Dear developers, pay attention for this bug, please.

Firon · September 24, 2010

We actually fixed this already, it's just not in a released build yet. The next 3.0 will have the fix.

We may backport this to 2.2.

letchik · September 27, 2010

It would be great if you could provide the utorrent 2.2 with this fix

Firon · October 5, 2010

This fix will not be backported to 2.2. Maybe the next release (2.3?).

It's in 3.0 at least, which is surprisingly stable right now.

Changing torrent name takes effect on webseed url

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Archived