> But in mod_deflate.c in deflate_out_filter(), there is a check that > removes the filter if a Content-Range header is found. Why is > mod_deflate not removed from the output filter chain? Or is it the > intended order of the filters that mod_deflate compresses first and > the byterange filter then cuts out the required ranges. If yes, why do
mod_deflate is not hooked in the (mod_)filter chain. It was configured by SetOutputFilter DEFLATE in this case. Just additional info, should that make any difference. So long, -- Igor Galić Tel: +43 (0) 699 122 96 338 Fax: +43(0) 1 91 333 41 Mail: [email protected] URL: http://brainsware.org/
