Okhttp: no-cache="field-name" is not handled

[1zaman]

The no-cache response directive can specify field names, in which case it should be interpreted as only excluding those specific header fields from being cached. However, this is currently being handled just like the unqualified directive, i.e. by excluding the whole response from being cached.

[swankjesse]

Seems reasonable enough. Can do.

[1zaman]

Great! I guess these fields can just be stripped out as the response is being served from the cache, and can still be be stored in cache, to be served in the case of successful revalidation (just like how the unqualified directive is handled). This seems like a simple change overall, and I'll see if I can contribute a pull request in a couple of days when I get some free time.

[miankhalid]

Any update on this issue's resolution @swankjesse?

[swankjesse]

Needs some attention.