From owner-freebsd-current@FreeBSD.ORG  Thu Jan 30 11:07:27 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id DCED9B7A
 for <freebsd-current@freebsd.org>; Thu, 30 Jan 2014 11:07:27 +0000 (UTC)
Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9F2FE1FE0
 for <freebsd-current@freebsd.org>; Thu, 30 Jan 2014 11:07:27 +0000 (UTC)
Received: from 0x20.net (0x20.net [217.69.76.212]) (Authenticated sender: lala)
 by mail.0x20.net (Postfix) with ESMTPA id 392076A600A
 for <freebsd-current@freebsd.org>; Thu, 30 Jan 2014 12:07:26 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 30 Jan 2014 12:07:26 +0100
From: Lars Engels <lars.engels@0x20.net>
To: freebsd-current@freebsd.org
Subject: Re: freebsd-update
In-Reply-To: <52E977FB.8020105@freebsd.org>
References: <lblts0$9o1$1@ger.gmane.org>
 <CAJ5UdcO6V_YnyoJSA=JRL_D7vFzZ8yXcKnh2QcjNQDskbpE98w@mail.gmail.com>
 <5F09668C-0DEA-4074-A06C-BC4D29F92368@FreeBSD.org>
 <201401211149.45793.jhb@freebsd.org>
 <CAN6yY1uiNcWPuJL=O6osDhZci_YBXe7tRW0Nt_cUy25cCTbALQ@mail.gmail.com>
 <52E2C1BC.10202@allanjude.com> <20140125113236.GX86491@e-new.0x20.net>
 <1390662664.13404.75208481.39F16B29@webmail.messagingengine.com>
 <20140129205157.GB86491@e-new.0x20.net> <52E977FB.8020105@freebsd.org>
Message-ID: <a83ebdead80178a1431c401e0cbc83bf@mail.0x20.net>
X-Sender: lars.engels@0x20.net
User-Agent: Roundcube Webmail/0.7
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 11:07:27 -0000

Am 2014-01-29 22:51, schrieb Colin Percival:
> On 01/29/14 12:51, Lars Engels wrote:
>> On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
>>> On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
>>>> Also using freebsd-update behind a proxy is really slow. Even with a
>>>> very fast internet connection (normally download rates ca. 3 MBytes 
>>>> /
>>>> s) downloading all the tiny binary diff files took more than 8 
>>>> hours.
>>>> Maybe freebsd-update's backend could create a tarball of all those
>>>> diffs and provide this?
>>> 
>>> Even streaming the tar instead of waiting for the freebsd-update 
>>> server
>>> to produce the tarball would be an improvement. I have no experience
>>> doing that over a WAN but I don't see why it would be unreliable.
>> 
>> Colin, what do you think? Is it possible?
> 
> Anything is *possible*, but given that the number of patches available 
> is
> typically at least 10x the number being fetched this doesn't seem like 
> it
> would be very efficient.
> 
> FWIW, the performance problems with proxies are limited to HTTP proxies
> which don't speak HTTP/1.1.

Are you sure?
I just tried it manually with telnet:

# telnet proxyserver 8080
Trying <IP Address>...
Connected to proxyserver.
CONNECT www.heise.de:80 HTTP/1.1
Proxy-Authorization:Basic blahblahblahbase64

HTTP/1.1 200 Connection established

GET / HTTP/1.1

HTTP/1.1 400 Bad Request


IIUC the proxy itself supports HTTP/1.1 but not the webserver behind the 
proxy?

That's the same proxy that takes hours to download the patches with 
httpget.