Jump to content

Webseed (HTTP) always stops after first piece


Recommended Posts

It's a little bit complicated to produce this bug.

I used Webseed a few times sucessfully now, but this time it does not to work.

I downloaded an www.onlinetvrecorder.com file by browser.

(it's hard to get the URL and continue to download this URL in another software without breaking any session info. So I often start like this)

As always, this download failed at maybe half of the file.

Now, I simple copy the file to my uTorrent data direcory, fetch the torrent of the file.

uTorrent should be able to fetch the remaining data by the torrent protocol.

But....usually there is not any seed. So now I have to get a HTTP URL from any of the mirrors somehow.

This time I got one from http://otr.datenkeller.at/

Now, whenever I add the URL to uTorrent, it will download a single piece.

With some experimenting, I found out how to max out the throughput:

Open the Webseeds tab,. then add 6 times the same URL. Wait for the download to complete, and add again. From time to time I clear the webseeds list, and start over.

I made 2 interesting observations, which make me think of a bug.

This is the URL I use:


Now the log says:

[2010-05-13 21:40:03] Straehl_Ein_Bulle_am_Abgrund_10.04.20_00-25_zdf_80_TVOON_DE.mpg.HQ.avi.otrkey: HTTP invalid URL:


[2010-05-13 21:40:16] Banned %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 (0 B downloaded, 0 B bad)


[2010-05-13 21:41:17] Banned %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 (1.00 MB downloaded, 0 B bad)


while "..." means: several times the same message.

See? The URL seems bad, everything 0x00.

On the "Pieces" tab the availability count went up to 180 until now, which means the non working webseeds are still somewhere.

I believe it should be possible to reproduce this bug by downloading any file from the otr.datenkeller.at mirror.

Maybe try this file:


Or create a www.onlinetvrecorder.com account for yourself.

Mh... you will need the torrent.

Maybe try this:

uTorrent 2.0.1. build 19248

Link to comment
Share on other sites

Yepp, I know that. I am not a noob.

The details I provided made me think this is a bug in uTorrent.

If you do not want to fix the bug, then forget about this report.

I am not sure if I understood correctly: You want me to search for a solution to my problem or for a guide what info to report?

Link to comment
Share on other sites

Since the interface between client and server is narrow, it should be easy to guess if the problem is on server or client side.

The difference between a regular request and one from uTorrent is

- uTorrent sends a range FROM-TO

- uTorrent sends two HTTP GET within a single TCP packet, the second GET is not processed by the server. You could detect this problem and send a seperate GET request.

- Server answers with "503 max connection count reached" after 6 parallel connections. You might wait for the other connections to close?!

The rest seems OK

GET (url) HTTP/1.0

Range: bytes=1381099306-

User-Agent: Wget/1.11.4

Accept: */*


Connection: Keep-Alive

GET (url) HTTP/1.1

Host: dl17-mg-hq.lastverteiler.net

User-Agent: BTWebClient/2010

Connection: keep-alive

Range: bytes=1368391680-1369440255

Do with this info whatever you want.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...