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
I recently upgraded from 1.6.0 to 2.1.0 and I'm on Rails 6.0.0.
I have noticed that Clearance sets two cookies when I sign in: one for the domain .example.com and another for example.com. They have the same name (remember_token), value, path (/), and size. They differ as follows:
When I log out Clearance deletes the .example.com cookie but leaves the other one alone.
It looks to me like the .example.com cookie is the "correct" one and the other one is bogus. How do I ensure the other one isn't created in the first place?
Also, I don't use subdomains at all – so should I actually be setting the cookie domain to example.com instead of .example.com?
Many thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello!
I recently upgraded from 1.6.0 to 2.1.0 and I'm on Rails 6.0.0.
I have noticed that Clearance sets two cookies when I sign in: one for the domain
.example.com
and another forexample.com
. They have the same name (remember_token
), value, path (/
), and size. They differ as follows:Here is an excerpt from my configuration:
When I log out Clearance deletes the
.example.com
cookie but leaves the other one alone.It looks to me like the
.example.com
cookie is the "correct" one and the other one is bogus. How do I ensure the other one isn't created in the first place?Also, I don't use subdomains at all – so should I actually be setting the cookie domain to
example.com
instead of.example.com
?Many thanks in advance.
The text was updated successfully, but these errors were encountered: