[tor-bugs] #1149 [Polipo]: Impossible to download files bigger then 32MB

[Tor Bug Tracker & Wiki]

#1149: Impossible to download files bigger then 32MB
----------------------+-----------------------------------------------------
  Reporter:  doda     |       Owner:  loafier 
      Type:  defect   |      Status:  closed  
  Priority:  major    |   Milestone:          
 Component:  Polipo   |     Version:  0.2.1.20
Resolution:  wontfix  |    Keywords:          
    Parent:           |  
----------------------+-----------------------------------------------------
Changes (by phobos):

  * status:  assigned => closed
  * resolution:  None => wontfix


Old description:

> This is a bug in polipo not in tor, but since you included a 2 years
> abandoned app with knows bugs in a stable release of tor I will report it
> here in case you were unaware.
>
> Bug #1
> When downloading a file bigger then the chunkHighMark value in
> polipo.conf, currently set to 33554432 bytes, polipo stops sending output
> to the browser, but still continues to download the file from tor.
> When this happens the browser is unable to disconnect the download or
> retry it because polipo blocks the requests until the connection is
> terminated by the server side or through the tor network map.
>
> Bug #2
> When downloading a file if the connection is closed by the server side or
> through tor, polipo automatically generates a background request to
> download the file again, however the way it does this contains a bug that
> instead of downloading from the part where the download was cut, it
> starts at the beginning of the file again, the result is a waste of
> bandwidth, and a long wait while polipo catches up to where the download
> stopped and starts outputting data to the browser again.
>
> Bug #3
> When using a download manager that supports resuming, the download
> manager will usually resume by sending a http header like "Range:
> bytes=1000-" indicating that the server should start sending from byte
> 1000.
> However polipo strips this header from requests if the URL is one that
> has previously failed, meaning the download starts from 0 again.
> This can be tested by use a download manager like getright, and pause the
> download and then try to resume it.
>
> The combination of the 3 bugs above make it impossible to download a file
> larger then 32MB via tor, you cant download it, and cant resume it when
> it fails.
>
> For speeding up testing, you can remove the "socksParentProxy" line from
> polipo.conf to make it connect to the internet directly, making it much
> faster to download 32mb and observe the bugs.
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 This is a bug in polipo not in tor, but since you included a 2 years
 abandoned app with knows bugs in a stable release of tor I will report it
 here in case you were unaware.

 Bug #1
 When downloading a file bigger then the chunkHighMark value in
 polipo.conf, currently set to 33554432 bytes, polipo stops sending output
 to the browser, but still continues to download the file from tor.
 When this happens the browser is unable to disconnect the download or
 retry it because polipo blocks the requests until the connection is
 terminated by the server side or through the tor network map.

 Bug #2
 When downloading a file if the connection is closed by the server side or
 through tor, polipo automatically generates a background request to
 download the file again, however the way it does this contains a bug that
 instead of downloading from the part where the download was cut, it starts
 at the beginning of the file again, the result is a waste of bandwidth,
 and a long wait while polipo catches up to where the download stopped and
 starts outputting data to the browser again.

 Bug #3
 When using a download manager that supports resuming, the download manager
 will usually resume by sending a http header like "Range: bytes=1000-"
 indicating that the server should start sending from byte 1000.
 However polipo strips this header from requests if the URL is one that has
 previously failed, meaning the download starts from 0 again.
 This can be tested by use a download manager like getright, and pause the
 download and then try to resume it.

 The combination of the 3 bugs above make it impossible to download a file
 larger then 32MB via tor, you cant download it, and cant resume it when it
 fails.

 For speeding up testing, you can remove the "socksParentProxy" line from
 polipo.conf to make it connect to the internet directly, making it much
 faster to download 32mb and observe the bugs.

 [Automatically added by flyspray2trac: Operating System: All]

--

Comment:

 Juliusz has taken over polipo maintenance again.  He's asked the authors
 of existing bugs to email them to his mailing list at
 https://lists.sourceforge.net/lists/listinfo/polipo-users

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1149#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online