Errors on resumed downloads

[Degreane]

Hi sir.
i have to admit you have a nice software but still needs refining though.
if i start a download then i drop the download afterwards in the middle
i then do resume the download and not going through the cache then also have dropped the download . and afterwards i want to resume with the cache i get to wait till replicator downloads the missing chunk and afterwards it resumes from where i ordered it to .

example illustrated :
./http-replicator -p 8000 -r /tmp/Repli --daemon /tmp/Repli.log
24304
[fbanna@localhost replicator]$ export http_proxy=127.0.0.1:8000
[fbanna@localhost replicator]$ wget -S -c --delete-after 'http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz'
--2014-02-28 19:42:29-- http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz
Connecting to 127.0.0.1:8000... connected.
Proxy request sent, awaiting response...
HTTP/1.1 200 OK
Content-Length: 13767976
Accept-Ranges: bytes
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Server: nginx
Last-Modified: Thu, 19 Dec 2013 01:15:46 GMT
Connection: close
Cache-Control: max-age=315360000
Date: Fri, 28 Feb 2014 17:42:30 GMT
Content-Type: application/octet-stream
Length: 13767976 (13M) [application/octet-stream]
Saving to: ‘node-v0.10.24.tar.gz’

12% [===============> ] 1,782,504 26.0KB/s eta 5m 47s ^C
[fbanna@localhost replicator]$ wget -S -c --delete-after 'http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz' -Y off
--2014-02-28 19:43:28-- http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz
Resolving nodejs.org (nodejs.org)... 165.225.133.150
Connecting to nodejs.org (nodejs.org)|165.225.133.150|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 206 Partial Content
Server: nginx
Date: Fri, 28 Feb 2014 17:43:29 GMT
Content-Type: application/octet-stream
Content-Length: 11981128
Last-Modified: Thu, 19 Dec 2013 01:15:46 GMT
Connection: keep-alive
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Cache-Control: max-age=315360000
Content-Range: bytes 1786848-13767975/13767976
Length: 13767976 (13M), 11981128 (11M) remaining [application/octet-stream]
Saving to: ‘node-v0.10.24.tar.gz’

23% [++++++++++++++++============> ] 3,251,808 103KB/s eta 2m 35s ^C
[fbanna@localhost replicator]$ wget -S -c --delete-after 'http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz'
--2014-02-28 19:43:53-- http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz
Connecting to 127.0.0.1:8000... connected.
Proxy request sent, awaiting response...
HTTP/1.1 206 Partial Content
Content-Length: 10496432
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Content-Range: bytes 3271544-13767975/13767976
Server: nginx
Last-Modified: Thu, 19 Dec 2013 01:15:46 GMT
Connection: close
Cache-Control: max-age=315360000
Date: Fri, 28 Feb 2014 17:43:54 GMT
Content-Type: application/octet-stream
Length: 13767976 (13M), 10496432 (10M) remaining [application/octet-stream]
Saving to: ‘node-v0.10.24.tar.gz’

34% [++++++++++++++++++++++++++++++============> ] 4,726,368 49.5KB/s eta 6m 36s ^C

and in the log i get the following error

] Fri Feb 28 19:43:53 2014
0.00 Accepted request from 127.0.0.1:49370
0.00 Client sends GET http://nodejs.org/dist/v0.10.24/node-v0.10.24.tar.gz HTTP/1.1
0.00 Requesting resume of partial file in cache: 1789744 bytes, Thu, 19 Dec 2013 01:15:46 GMT
0.00 Connecting to 165.225.133.150:80
0.34 Server responds HTTP/1.1 206 Partial Content
0.34 Resuming partial file in cache at byte 1789744
0.34 Replicator responds HTTP/1.1 206 Partial Content
64.30 Traceback (most recent call last):
64.30 File "/home/fbanna/Desktop/DownLoads/Replicator/replicator/fiber.py", line 53, in step
64.30 state = self.__generator.next()
64.30 File "./http-replicator", line 52, in Replicator
64.30 response.send( client )
64.30 File "/home/fbanna/Desktop/DownLoads/Replicator/replicator/Response.py", line 102, in send
64.30 self.__pos += sock.send( chunk )
64.30 error: [Errno 32] Broken pipe
[ IDLE ] Fri Feb 28 19:44:58 2014
[ BUSY ] Fri Feb 28 19:45:04 2014

[Degreane]

you can duplicate the same issue if you use some download manager such as aria2c