Cookie blocked due to "not matching" domains #586
-
|
While learning how to use the PSAT for auditing I came upon this error: "This cookie was blocked because the domain in the web address for this request was neither an exact match with the cookie's domain attribute nor a subdomain of it." This brings the question of why it was blocked, because it's the right domain. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hello @hjmace Based on the analysis of your screenshot, it seems the cookie has a Lax security setting. The cookie is most likely from appmaster.io, but it might be getting set on a different website you visited. To pinpoint the exact request that might be adding the blocked cookie, We will recommend checking our guide for filtering network request for given cookie |
Beta Was this translation helpful? Give feedback.
Hello @hjmace
Based on the analysis of your screenshot, it seems the cookie has a Lax security setting.
The cookie is most likely from appmaster.io, but it might be getting set on a different website you visited.
Lax cookies offer some security by only being sent when you directly visit the website that set them, like following a link to appmaster.io. This is the default behavior if the
SameSiteattribute is not specified.To pinpoint the exact request that might be adding the blocked cookie, We will recommend checking our guide for filtering network request for given cookie