net/http: Client should cache 301/308 redirect

[yonderblue]

What version of Go are you using (go version)?

go1.11.1

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

linux amd64, android arm

What did you do?

Used http.Client for multiple calls against a url that returns 301 or 308.

What did you expect to see?

Second invocation to use a cached response from the first.

What did you see instead?

The first call before the Location is followed is always made.

Is there any reason this choice was made or has the logic just never been put in?

[agnivade]

/cc @bradfitz

[bradfitz]

Never considered either way.

[rsc]

The http.Client does no caching of responses at all. It's not just 301/308.

What is the context here? Is there a situation where this is causing problems? Also, if you are making the same request repeatedly, why is it problematic to be repeating the redirected call but not problematic to be repeating the final call?

[odeke-em]

I believe @Gaillard filed this issue since 301: Moved Permanently and 308: Permanent Redirect both have permanency in them, thus we can assume that those responses will never change, so perhaps we can consider these as cacheable.

[odeke-em]

The issue though is that what happens if we have uncapped/unlimited response caching and many responses are cached; what if a server responds with refresh deadline/tokens in the 301/308 responses?