Currently, in some unit tests in ImageResourceTest returns shorter range response than requested, e.g.
For a request with "range: bytes=0-2047" request header (a placeholder request),
a partial response with ~300 bytes is served, while the whole file would be less than 2048 bytes and thus we can serve the full response.

To make this consistent, we might consider to create and use JPEG file >2048 bytes instead, and serve its first 2048 bytes for "range: bytes=0-2047" request.

See comments in https://codereview.chromium.org/2648073002/
(#28, #30, #34, #35) for discussion.

This is a low priority issue, as currently the (in)consistency between range request/response doesn't affect what we want to test in these tests.
Temporarily assigned to me but feel free to take if someone is interested.