On Tue, Apr 27, 2010 at 05:07:36PM +0700, Ben van Staveren wrote:
Hi Moritz,
Yeah I just figured that one out - but that's new, never saw it do this
before to be honest - it's not a big deal actually since in production
Static::Simple isn't used and I let lighttpd take care of serving
Hi Matt,
Check your plugin order; this doesn't normally happen because Static::Simple
bypasses the loading of the session. If you've tried it both before and
after you load your session plugins, come back to us with the versions of
all the plugins you're loading and we'll dig further.
On Wed, Apr 28, 2010 at 10:58:58PM +0700, Ben van Staveren wrote:
Hi Matt,
Check your plugin order; this doesn't normally happen because
Static::Simple
bypasses the loading of the session. If you've tried it both before and
after you load your session plugins, come back to us with the
Right after ConfigLoader ... shouldn't do that.
Honestly, the session shouldn't be UPDATEd at all in that case.
Like I said though, for me it's not a big deal that this happens, now
that I know what causes it, I'm not worried about this showing up on my
app_server.pl output during
Right after ConfigLoader ... shouldn't do that.
Honestly, the session shouldn't be UPDATEd at all in that case.
Like I said though, for me it's not a big deal that this happens, now
that I know what causes it, I'm not worried about this showing up on my
app_server.pl output during
Which is great. But a lot of users leave Static::Simple loaded, so while
it's not going to bother you it -will- bother them.
So, in the name of paying karma forwards, any chance I could have the
versions anyway please?
*Cough* remind me not to answer emails late at night :D
Okay I've got
Hi folks,
Recently after upgrading all of Catalyst, I'm witnessing some weird
behaviour in some apps. I'm using Catalyst::Plugin::Session::Store::DBIC
to store my sessions, and when I have DBIC_TRACE going, I see this:
BEGIN WORK
SELECT me.id, me.session_data, me.expires FROM session me
I had the same problem. I boiled it down to Static::Simple. Each request
to a static resource issued a session update. In a recent
release of cat the handling of requests seemed to have changed.
Try downgrading to 5.80018 which fixed it for me (which is not a good
solution, but I have no time
Hi Moritz,
Yeah I just figured that one out - but that's new, never saw it do this
before to be honest - it's not a big deal actually since in production
Static::Simple isn't used and I let lighttpd take care of serving static
files, but in testing it's a bit disconcerting to see it crop up
