I'm wondering if this is normal way how rails handles sessions...
When I login (create a session on server), application sets cookie
value in the HTTP header.
%253D--d806ac851b4e6ee4310dcf2abdcf57e3ea4c12cb; path=/ )
When I logout (delete a session), application gives me other value for
the Set-Cookie header.
But, on every next login and logout application sets the SAME value
for Set-Cookie header.
And, when I use db session based store, application always sets
different values for Set-Cookie header, which is better behavior.
I think, when using cookie based session store, application should set
different values for Set-Cookie header, maybe add some hashed
timestamp to the Set-Cookie value in case to recognize by it if the
session is some old, or it is the last one for.