Is it the intended behavior to set a cookie any time the session is *fetched* even if nothing is set in the session?<br>
<br>With a new app with these added plugins:<br><br> Cache<br> Session<br> Session::Store::Cache<br> Session::State::Cookie<br><br>And if I just add my $ses = $c->session; to the index action in root then that causes a Set-Cookie header to be set in the response. (And if cookies are disabled on a browser then a new session id is created every request, and expires is written to the store).<br>
<br>Not a big deal, but just curious if that was by design or just a side-effect of how the session code works.<br>
<br>I typically use session cookies and don't set a cookie header in the response if a valid session id was in the request cookie.<br><br><br clear="all"><br>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>