Insecure cookies without SameSite attribute set
Chrome 80 will deprecate and remove the use of cookies with the SameSite=None attribute but without the Secure attribute. Any cookie that requests SameSite=None but is not marked Secure will be rejected (Reject insecure SameSite=None cookies - Chrome Platform Status).
In the browser console the following warning is thrown:
[QUOTE]A cookie associated with a cross-site resource at was set without the
attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with
and
. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and .
cPanel sets multiple cookies:
SameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with
SameSite=Noneand
Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and .
cPanel sets multiple cookies:
- cpsession (secure cookie without the SameSite attribute)
- timezone (unsecure cookie without the SameSite attribute)
- whostmgrsession (secure cookie without the SameSite attribute)
-
Thank you for your reply but it is not an answer to this bug report. I recommend your development team to read Developers: Get Ready for New SameSite=None; Secure Cookie Settings and prepare for the Chrome update of February 2020. Thanks again 0 -
Hello, We do appreciate the suggestion but this wouldn't be considered a bug. A bug is something that doesn't function as intended. This is an addition to the product you're requesting and it would be considered a feature request and that should be requested in the proper place to receive the attention it deserves. Thank you. 0 -
@cPanelLauren To implement set cookies to strict and http secure would this be the line I need to add to apache pre main include config apache 2.2.4 Header always set Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict0 -
Hello @Cloud9 I do believe that would work but I am more concerned with why you're using Apache 2.2 at all? 0
Please sign in to leave a comment.
Comments
5 comments