Date: Fri, 5 Sep 2003 01:22:13 +0200 From: Clement Laforet <sheepkiller@cultdeadsheep.org> To: Thierry Thomas <thierry@pompo.net> Cc: ports@freebsd.org Subject: Re: Fetch: Requested Range Not Satisfiable Message-ID: <20030905012213.2bb07d83.sheepkiller@cultdeadsheep.org> In-Reply-To: <20030904223349.GA57845@graf.pompo.net> References: <20030904223349.GA57845@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Sep 2003 00:33:50 +0200 Thierry Thomas <thierry@pompo.net> wrote: Hi Thierry ! > What does it mean? This error is reported by fetch for grisbi at > <http://bento.freebsd.org/errorlogs/i386-4-latest/grisbi-0.4.1.log>. > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030905012213.2bb07d83.sheepkiller>