On Aug 26, 2011, at 8:46 AM, Plüm, Rüdiger, VF-Group wrote: > > >> -----Original Message----- >> From: Jim Jagielski [mailto:j...@jagunet.com] >> Sent: Freitag, 26. August 2011 14:38 >> To: dev@httpd.apache.org >> Subject: Re: svn commit: r1161661 - >> /httpd/httpd/trunk/modules/http/byterange_filter.c >> >> >> On Aug 26, 2011, at 8:31 AM, Jim Jagielski wrote: >>> >>> Agreed... The issue is that to merge, you need to parse... We could have >>> ap_set_byterange() also return a set of start/stop points (in an >>> array), so that the filter can work with that and not >> bother with rereading >>> r->range. In fact, I think that makes the most sense... That >> is, adjust >>> ap_set_byterange() to create the modified, parsed r->range, >> a return status >>> and the start/stop array. The filter then goes thru that array. >> >> So ap_set_byterange(request_rec *r, apr_off_t clen, >> apr_array_header_t *indexes) > > What is clen? >
The content length… we need to know for ranges like 100- and -99
