Comment 43 for bug 198646

> The problem, as I understand it currently, should have been covered by TruncatedMultipleRangeRequestHandler. I don't understand why it didn't catch it.

The difference is that it tests truncation between the boundary line and the content block, whereas this is occurring before the boundary line.