Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 33209 invoked by uid 500); 20 Jan 2001 00:20:04 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 33195 invoked from network); 20 Jan 2001 00:20:04 -0000 Date: Sat, 20 Jan 2001 00:19:44 +0000 From: Tony Finch To: new-httpd@apache.org Subject: Re: 1.3.15 byte ranges Message-ID: <20010120001944.A706@hand.dotat.at> References: <200101160039.TAA25937@devsys.jaguNET.com> <20010116004717.L61248@hand.dotat.at> <001d01c07fd4$17ff8570$e4421b09@raleigh.ibm.com> <20010116200205.U61248@hand.dotat.at> <3A675B31.386BE6E6@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A675B31.386BE6E6@pobox.com> Organization: Covalent Technologies, Inc X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Paul Marquis wrote: >For multiple byte ranges, it seems Apache inserts an extra CR/LF >before the first range separator is printed. Is this a problem or am >I being pedantic? This turns out not to be a problem. See section 19.2 of RFC 2616: 1) Additional CRLFs may precede the first boundary string in the entity. (this is related to the optional preamble and epilogue sections in a MIME multipart message) And it's a complete bugger to avoid sending them so I think the code can stay as it is. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "And remember my friend, future events such as these will affect you in the future."