From owner-freebsd-current@FreeBSD.ORG Thu Jan 30 12:34:58 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E6CEF37 for ; Thu, 30 Jan 2014 12:34:58 +0000 (UTC) Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B269916E2 for ; Thu, 30 Jan 2014 12:34:57 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id l18so6008884wgh.11 for ; Thu, 30 Jan 2014 04:34:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=dlJrKLPURRN0UQ3RvToeArxJcSIqNlmBZfIIqAfavao=; b=oK1ueQgsvVp9MfKljXzn6gO0ToPiArGFXfVDrWdQQuotxqSmJGkRLCS9N9VDkbRNFM 9ZX0bKPeFPiOTRh9Pdrf2EVGmsKxe89TaEnEiDFibyv/Meqj3T1kk+Y0UTD1NRLMKQG1 B2vHmtpGSQ2FKawuPDRahNgj9r5DP6snyTF7SSvgf3biPd6txu3RYPHbpP5sT60j+p6K u0u1zgdb34Iqs/9mgWR/m/0FPcFgv8AcbeOXuRZGWS2oJ9gKqFWee7bbpGpnKCXfbGM/ LHYMajEQzPz01NifOgOh6DeZOwF2Vc+4megR6gtAx3cL/FZRN9iiLPe/SZNBcP4E18lJ rCAg== X-Received: by 10.180.105.65 with SMTP id gk1mr23514972wib.12.1391085295974; Thu, 30 Jan 2014 04:34:55 -0800 (PST) Received: from gumby.homeunix.com (87-194-112-13.bethere.co.uk. [87.194.112.13]) by mx.google.com with ESMTPSA id h13sm12004309wjr.22.2014.01.30.04.34.54 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 30 Jan 2014 04:34:55 -0800 (PST) Date: Thu, 30 Jan 2014 12:34:54 +0000 From: RW To: freebsd-current@freebsd.org Subject: Re: freebsd-update Message-ID: <20140130123454.588a92f2@gumby.homeunix.com> In-Reply-To: References: <5F09668C-0DEA-4074-A06C-BC4D29F92368@FreeBSD.org> <201401211149.45793.jhb@freebsd.org> <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> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 12:34:58 -0000 On Thu, 30 Jan 2014 12:07:26 +0100 Lars Engels wrote: > > 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: > ... > 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. Proxy support for HTTP/1.1 on the client side doesn't imply that it supports full end-to-end pipelining. The proxy can advertise 1.1 without supporting pipelining. Even if it does that doesn't necessarily imply that it has full end-to-end pipelining. I'm not sure what the current state of squid is, but for years it translated client side HTTP 1.1 pipelining into individual HTTP 1.0 requests on the server side. I don't use freebsd-update myself, but from a quick look at the manpage I think it could benefit by extending the cron command to allow fetching a new release automatically.