Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 10533 invoked by uid 500); 21 May 2002 15:03:06 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 10522 invoked from network); 21 May 2002 15:03:06 -0000 Received: from wolff.to (66.92.219.49) by daedalus.apache.org with SMTP; 21 May 2002 15:03:06 -0000 Received: (qmail 19143 invoked by uid 500); 21 May 2002 15:06:51 -0000 Date: Tue, 21 May 2002 10:06:51 -0500 From: Bruno Wolff III To: users@httpd.apache.org Subject: Re: 2.0.36 range header with cgi script problem Message-ID: <20020521150651.GA19104@wolff.to> Mail-Followup-To: users@httpd.apache.org References: <20020521140257.GA18309@wolff.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, May 21, 2002 at 07:29:55 -0700, Joshua Slive wrote: > > On Tue, 21 May 2002, Bruno Wolff III wrote: > > > After upgrading to apache 2.0.36 I started seeing 416 errors in my logs. > > This is a known bug and will be fixed in the next version. Is there somewhere I can grab a patch for this? I have one person who I want to be able to get these files and would prefer not to go back to 1.3.x or set up a temporary work around that requires work on his end. I tried doing a: BrowserMatch "SmartDownload" downgrade-1.0 force-response-1.0 to discourage SmartDownload from adding Range headers but that didn't work. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org