Data not cached when gzip content-encoding is combined with chunked transfer-encoding. about httpresponsecache HOT 5 OPEN

+1 this solves issue #32. Do we need to open a bug with Google and get this committed upstream? I had the same issues using the HttpResponseCache built in to Jelly Bean.

from httpresponsecache.

Do it! ^^

But I am not 100% convinced that this is a proper fix. Because we could create an IOException when reading ahead. So a proper fix probably needs to be a bit more sophisticated.

In a project I am working on right now I fixed this issue by moving the "read ahead" step into the close() method. Ignoring all exceptions. Not sure if this is any better.

Well, would not hurt to report this to Google, I guess. So please go ahead, if that is OK with you. I would not really know where to go.. ^^

dl

from httpresponsecache.

I have a feeling that a more complex fix is the right way to go, but this works for now for development.

@candrews thoughts?

from httpresponsecache.

A bug should definitely be opened with the Android project about this.

@swankjesse can you chime in? You wrote this, and presumably this effects some of the projects you're currently working on :)

from httpresponsecache.

Fixed in OkHttp! See Android issue 38817.

from httpresponsecache.