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.
