I'm playing around w/ ap_set_byterange() for the merging and detection part, but that should not hold up release with the optimized code…
I can do a 2.2.10 release with the byte range stuff once we agree on the back port and confirm it fixes the problem...
