When may a shared cache store a response to a request that carried an Authorization header field?
q13 · grounded · HTTP 200 · index 0fc1763d6701
What survived the check — each claim with the passage that supports it
Under rfc9111#3, a shared cache must not store a response to a request with an Authorization header field unless a response directive is present that explicitly allows shared caching, along with the other storage requirements in that section.
rfc9111#3 — 80% of
this claim's content words appear in that passage.
Under rfc9111#3.5, the Cache-Control response directives identified as allowing a shared cache to store and later use a response to a request with an Authorization header field are must-revalidate, public, and s-maxage, provided the cache conforms to the requirements of the applicable directive for that response.
rfc9111#3.5 — 70% of
this claim's content words appear in that passage.
Under rfc9111#5.2.2.9, the public response directive explicitly marks a response as cacheable and permits a shared cache to reuse a response to a request containing an Authorization header field, subject to the constraints in Section 3.
rfc9111#5.2.2.9 — 94% of
this claim's content words appear in that passage.
What was retrieved — the passages the drafter saw, and nothing else
| rank | section | score |
|---|---|---|
| 1 | RFC 9111 Section 3.5: Storing Responses to Authenticated Requests |
0.7847 |
| 2 | RFC 9111 Section 3: Storing Responses in Caches |
0.6713 |
| 3 | RFC 9111 Section 4: Constructing Responses from Caches |
0.6360 |
| 5 | RFC 9111 Section 5.2.2.9: public |
0.6116 |
| 6 | RFC 9110 Section 16.4.2: Considerations for New Authentication Schemes |
0.6110 |
| 7 | RFC 9111 Section 3.2: Updating Stored Header Fields |
0.6071 |
| 8 | RFC 9110 Section 11.6.2: Authorization |
0.6067 |
| 10 | RFC 9111 Section 7.3: Caching of Sensitive Information |
0.5906 |