How does the SameSite cookie attribute restrict cross-site requests?
u03 ·
unsupported ·
HTTP 200 ·
index 0fc1763d6701
eval/questions.yaml annotates this question as
unsupported, and the gate holds the service
to agreeing with that annotation across the set.
This corpus does not answer that question. Nothing drafted from the passages below could be traced back to them, so no answer is given.
What was retrieved — the passages the drafter saw, and nothing else
| rank | section | score |
|---|---|---|
| 1 | RFC 6265 Section 4.1.2.6: The HttpOnly Attribute |
0.5126 |
| 2 | RFC 6265 Section 4.1.2.3: The Domain Attribute |
0.5040 |
| 3 | RFC 6265 Section 5.2.6: The HttpOnly Attribute |
0.5026 |
| 4 | RFC 6265 Section 3.1: Examples |
0.4997 |
| 5 | RFC 6265 Section 8.6: Weak Integrity |
0.4927 |
| 7 | RFC 6265 Section 7.1: Third-Party Cookies |
0.4889 |
| 8 | RFC 6265 Section 4.1.2.5: The Secure Attribute |
0.4869 |
| 9 | RFC 6265 Section 4.1.2.4: The Path Attribute |
0.4743 |
| 10 | RFC 6265 Section 8.5: Weak Confidentiality |
0.4698 |