Does not store responses with Set-Cookie headers by default, similar to NGINX

[k1LoW]

In RFC 9111, Servers that wish to control caching of responses with Set-Cookie headers are encouraged to emit appropriate Cache-Control response header fields (see https://httpwg.org/specs/rfc9111.html#rfc.section.7.3).
But to beat on the safe side, this package does not store responses with Set-Cookie headers by default, similar to NGINX.
THIS IS NOT RFC 9111.

[github-actions]

Code Metrics Report

	main (45b3316)	#39 (969fe46)	+/-
Coverage	80.9%	80.3%	-0.7%
Code to Test Ratio	1:2.0	1:2.0	-0.0
Test Execution Time	32s	38s	+6s

Details

  |                     | main (45b3316) | #39 (969fe46) |  +/-  |
  |---------------------|----------------|---------------|-------|
- | Coverage            |          80.9% |         80.3% | -0.7% |
  |   Files             |              4 |             4 |     0 |
  |   Lines             |            299 |           304 |    +5 |
+ |   Covered           |            242 |           244 |    +2 |
- | Code to Test Ratio  |          1:2.0 |         1:2.0 |  -0.0 |
  |   Code              |            660 |           670 |   +10 |
+ |   Test              |           1324 |          1342 |   +18 |
- | Test Execution Time |            32s |           38s |   +6s |

Code coverage of files in pull request scope (87.3% → 85.8%)

Files	Coverage	+/-
rfc9111/shared.go	85.8%	-1.5%

---

Reported by octocov