RFC2616 13.4 Response Cacheability

[bino98]

ref. https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.4

Hello.
I was reading RFC2616 chap 13.4,
I noticed that there might be a gap from the implementation.

That part is...

A response received with any other status code (e.g. status codes 302 and 307) MUST NOT be returned in a reply to a subsequent request unless there are cache-control directives or another header(s) that explicitly allow it. For example, these include the following: an Expires header (section 14.21); a "max-age", "s-maxage", "must- revalidate", "proxy-revalidate", "public" or "private" cache-control directive (section 14.9).

I think only this can be supported with the current implementation.
In my RFC interpretation, you can have cache in addition to this.

Am i wrong?