Quick question, is the proxy handling byte-range, or is the up-stream
server handling it? If the proxy module is handling it, then I believe
that the answer is to stop having the proxy handle it. If the up-stream
server is doing the work, then +1 for this patch.
Ryan
On Mon, 16 Apr 2001, Graham Leggett wrote:
> Graham Leggett wrote:
>
> > + if ((ct = apr_table_get(r->headers_in, "Content-Type")) &&
> > + (!strncasecmp(ct, "multipart/byteranges", 20) ||
> > + !strncasecmp(ct, "multipart/x-byteranges", 22))) {
> > + return 0;
>
> Oo-er! This is only half the story - single byte ranges must also be
> covered. Also, header_in should be headers_out...
>
> Regards,
> Graham
> --
> -----------------------------------------
> [EMAIL PROTECTED] "There's a moon
> over Bourbon Street
> tonight..."
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
