Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 92AA27810 for ; Thu, 25 Aug 2011 20:16:07 +0000 (UTC) Received: (qmail 32068 invoked by uid 500); 25 Aug 2011 20:16:06 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31983 invoked by uid 500); 25 Aug 2011 20:16:06 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 31846 invoked by uid 99); 25 Aug 2011 20:16:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2011 20:16:05 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [72.167.82.82] (HELO p3plsmtpa01-02.prod.phx3.secureserver.net) (72.167.82.82) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 25 Aug 2011 20:15:58 +0000 Received: (qmail 1393 invoked from network); 25 Aug 2011 20:15:32 -0000 Received: from unknown (76.252.112.72) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 25 Aug 2011 20:15:32 -0000 Message-ID: <4E56AD5C.3060909@rowe-clan.net> Date: Thu, 25 Aug 2011 15:15:24 -0500 From: "William A. Rowe Jr." User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Fixing Ranges References: <20110824220643.17819937@baldur> <201108242316.18134.sf@sfritsch.de> <201108250138.49474.sf@sfritsch.de> <5F975753-6B14-4F38-A0DB-113733FCCCDC@jaguNET.com> <2E5823B2-807E-4949-B3FE-79F648C54A22@jaguNET.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 8/25/2011 3:05 PM, Jim Jagielski wrote: > For us to be able to control the number of overlaps, ranges, > etc will require an API bump to add an entry to server_rec. > > Are we sure we want to do that for 2.2 or save that for trunk? Let's -not- overload server_rec. First, it's per-dir... it would be entirely sensible for us to allow backwards-broken clients to access particular sorts of docs in bizzaro ways (.pdf for example), denying stupid ranges on all other documents (particularly generated/proxied content). And there are probably going to be few overrides... set it up globally and forget it, except for the edge cases. But I suggest instead of abusing core config, let's create one config section for byterange, which will not break binary ABI, and should be infrequently merged.