From owner-freebsd-ports@FreeBSD.ORG Thu Sep 4 16:22:16 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7AD716A4BF for ; Thu, 4 Sep 2003 16:22:16 -0700 (PDT) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 343B443FDF for ; Thu, 4 Sep 2003 16:22:14 -0700 (PDT) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 55052 invoked by uid 85); 5 Sep 2003 01:22:12 +0200 Received: from sheepkiller@cultdeadsheep.org by goofy.cultdeadsheep.org by uid 82 with qmail-scanner-1.20rc2 (: ???. Clear:RC:1:. Processed in 0.041194 secs); 04 Sep 2003 23:22:12 -0000 Received: from unknown (HELO lucifer.cultdeadsheep.org) (192.168.0.2) by goofy.cultdeadsheep.org with SMTP; 5 Sep 2003 01:22:11 +0200 Date: Fri, 5 Sep 2003 01:22:13 +0200 From: Clement Laforet To: Thierry Thomas Message-Id: <20030905012213.2bb07d83.sheepkiller@cultdeadsheep.org> In-Reply-To: <20030904223349.GA57845@graf.pompo.net> References: <20030904223349.GA57845@graf.pompo.net> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd5.1) X-Face: ._cVVRDn#-2((lnfi^P7CoD4htI$4+#G/G)!w|,}H5yK~%(3-C.JlEYbOjJGFwJkt*7N^%z jYeu[;}]}F"3}l5R'l"X0HbvT^D\Q&%deCo)MayY`);TO Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: ports@freebsd.org Subject: Re: Fetch: Requested Range Not Satisfiable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2003 23:22:17 -0000 On Fri, 5 Sep 2003 00:33:50 +0200 Thierry Thomas wrote: Hi Thierry ! > What does it mean? This error is reported by fetch for grisbi at > . > > When I try to retrieve it manually, it works... Requested Range Not Satisfiable is the 416 HTTP error, surely due to Content-Range header in libfetch. But don't ask me why fetch failed on gohan14 ;-) According to RFC 2616: 10.4.17. 416 Requested Range Not Satisfiable A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.) When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type. clem