From owner-freebsd-ports@FreeBSD.ORG Fri Feb 22 22:17:04 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1A0116A474 for ; Fri, 22 Feb 2008 22:17:04 +0000 (UTC) (envelope-from fbsd06+TL=8887b65f@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id BEE8213C442 for ; Fri, 22 Feb 2008 22:17:04 +0000 (UTC) (envelope-from fbsd06+TL=8887b65f@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id 22EEB16448D for ; Fri, 22 Feb 2008 16:59:43 -0500 (EST) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id A46B523E496 for ; Fri, 22 Feb 2008 16:59:41 -0500 (EST) Date: Fri, 22 Feb 2008 21:59:38 +0000 From: RW To: freebsd-ports@freebsd.org Message-ID: <20080222215938.554c9459@gumby.homeunix.com.> In-Reply-To: <20080222172210.GA31869@lordcow.org> References: <20080222172210.GA31869@lordcow.org> X-Mailer: Claws Mail 3.3.0 (GTK+ 2.12.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: caching problems X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2008 22:17:05 -0000 On Fri, 22 Feb 2008 19:22:10 +0200 gareth wrote: > hey guys, our proxy is caching extremely old copies of the ports index > and portaudit databases from freebsd.org. our admins claim that they > cache the following files i need normally: > > http://www.FreeBSD.org/ports/auditfile.tbz > http://www.FreeBSD.org/ports/INDEX-6.bz2 > > since they have no no-cache pragma directives, and our admins won't > budge on their 'policy'. is the freebsd site breaking standards in > this way? No, these these files *should* be cachable, but a properly configured cache shouldn't cache then for very long since their last-modified headers are usually very recent (and since they have that header they can be revalidated cheaply). You don't say how old "ancient" is, but bear in mind that the auditfile.tbz is only fetched every three days when it's done from periodic scripts. Have you tried using curl to prefetch the relevant files, IIRC it adds a header that asks for a refetch or revalidation. That may cause the cache to update its copy, depending on whether their policy complies with standards.