The range transforms worked at for 3.0 but were broken for 3.2. This was masked by the addition of range acceleration but when that was determined to be too risky the original range transform issue was re-exposed. I'm currently trying to get some time to work on that, I see what the problem is, a fix has proven somewhat more difficult to discover.
https://issues.apache.org/jira/browse/TS-1776 Thursday, August 8, 2013, 1:56:11 PM, you wrote: > * the return code is set to 200 (instead of 206) > * the content-range header is omitted > * nevertheless the plugin only 'sees' the requested bytes
