Open valeriosillari opened 4 years ago
You could bypass this by using on your server.
response.setHeader("Set-Cookie", "HttpOnly;Secure;SameSite=Strict");
this are not a lib fault. Some example on express server.
app.use((req, res, next) => {
res.set({
"Set-Cookie", "HttpOnly;Secure;SameSite=Strict"
});
next()
})
or on your Nginx server proxy.
Ok good. I will try.
But right now I get the same issue also with a Nuxt application where I use the plugin and I generate static code, and I guess there is no server (Express) involved.
From Chrome 77 a warning appeared on any chrome browser.
A cookie associated with a resource at http://gstatic.com/ was set with
SameSite=Nonebut without
Secure. A future release of Chrome will only deliver cookies marked
SameSite=Noneif they are also marked
Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032.
I guess it's related to "SameSite". I'm not familiar with it I have to admit, but from this thread seems related to some new standard to use in the future https://stackoverflow.com/questions/58270663/samesite-warning-chrome-77
Just wondering if I'm correct and if it could be fixed?