In my example, session method doesn't try to manipulate sessions. It
allow set it once (do login action) and forget about sessions at all.
It is necessary for cases when you can not get log/pass values or cannot
just login like an empty user.
So it'll keep the test clean
Which is why you don't create cookies manually, the client side is
not supposed to touch them.
To re-emphasize, the session cookie has the HttpOnly flag set, so in
most browsers it is completely inaccessible.
https://github.com/kraih/mojo/blob/master/lib/Mojolicious/Sessions.pm#L56
--
sebastian
--
You received this message because you are subscribed to the Google
Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
