Fixed a bug when handling non-cached range responses that aren't honored by the server.

[clangen]

Here's my use case: I'm playing music against a server that is unable to satisfy range requests. Instead, it returns an HTTP 200 and the full body. At this point, if the response is not in the cache, AndroidVideoCache ignores the offset and starts returning data from the beginning of the stream.

I realize this pull request may not be accepted because:

1. I'm not super familiar with the code base; the fix may be in the wrong spot.
2. I took a look at the test suite, but I'm not quite sure how to test this particular case. If you have an idea, let me know.

At any rate, I wanted you to be aware of the issue with a potential fix.