# large publicly accessible HTTP archive?

2 messages from 2008-10-31 to 2008-10-31. Participants: Bryan Larsen, Daniel Stenberg.
Thread: https://gitlist.dev/t/16111

## Bryan Larsen, 2008-10-31 17:07

Subject: large publicly accessible HTTP archive?
Message-ID: <490B3B35.60508@larsen.st>
URL: https://gitlist.dev/e/490B3B35.60508%40larsen.st
In-Reply-To: <S1751776AbYJaQ5O/20081031165714Z+111@vger.kernel.org>

```
Hello,

I'm one of the maintainers of MacPorts git port.

A long time ago, we had problems pulling extremely large archives over 
HTTP on PowerPC machines.  By large, I mean on the order of 500 
megabytes: I was testing using an embedded Linux distribution.

We "fixed" the problem by turning off CURL_MULTI and ignored the 
problem.  Yes, bad form, I know.

Our problems were against curl 7.16.2.

However, in recent git's, CURL_MULTI is required to do an HTTP push, so 
we've had users complaining.

Curl is up to 7.19.0, they may have fixed our problem.  Unfortunately, 
the distribution I used for testing is gone now.  Putting up a local 
archive doesn't exhibit the problem either.

Is anybody aware of a very large HTTP accessible repository that 
wouldn't mind me doing a few test pulls from?  By large, I mean >500 
megabytes of network traffic for a single pull.

thanks,
Bryan

```

## Daniel Stenberg, 2008-10-31 19:01

Subject: Re: large publicly accessible HTTP archive?
Message-ID: <alpine.LRH.1.10.0810311959330.17280@yvahk3.pbagnpgbe.fr>
URL: https://gitlist.dev/e/alpine.LRH.1.10.0810311959330.17280%40yvahk3.pbagnpgbe.fr
In-Reply-To: <490B3B35.60508@larsen.st>

```
On Fri, 31 Oct 2008, Bryan Larsen wrote:

> We "fixed" the problem by turning off CURL_MULTI and ignored the problem. 
>
> Our problems were against curl 7.16.2.

Right, libcurl has had 8 releases since with perhaps an average of 30 bugfixes 
per release so...

I'm not aware of any current known libcurl bugs with the multi interface and 
"simple" HTTP transfers such as this.

-- 

  / daniel.haxx.se - libcurl hacker

```
