You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Cookie is set in a parent domain, if the cookie is set in a domain with https, since it uses secure tag, it can not be accessed from http domains.
Then in http domains the cookie is shown again and again cause it can not be accessed nor set.
This behavior makes sense since you can't set a secure cookie in http but you should have an alternative for these cases.
Proposed solution
Add a 'secure' boolean property in 'Cookie' interface.
Default can be 'true' maintaining current behavior (secure flag on if https and false if http).
If 'secure' is false then secure flag is never set.
Alternatively default value and current behavior can be undefined and when secure is true it may try to force secure flag.
Additional details
No response
The text was updated successfully, but these errors were encountered:
Description
When the Cookie is set in a parent domain, if the cookie is set in a domain with https, since it uses secure tag, it can not be accessed from http domains.
Then in http domains the cookie is shown again and again cause it can not be accessed nor set.
This behavior makes sense since you can't set a secure cookie in http but you should have an alternative for these cases.
Proposed solution
Add a 'secure' boolean property in 'Cookie' interface.
Default can be 'true' maintaining current behavior (secure flag on if https and false if http).
If 'secure' is false then secure flag is never set.
Alternatively default value and current behavior can be undefined and when secure is true it may try to force secure flag.
Additional details
No response
The text was updated successfully, but these errors were encountered: