Right then.
I've been seeing this error on and off for a while when under the dev
server, often caused when I'm debugging (perl -d) and restart the
server mid-request. Somehow the browser gets its knickers in a twist
or something. Error is:
Tried to set invalid session ID
'5c5ad62b4e9273eb1d5cba69ef4f9e33eeb6ed66, yourpreferences_session'
at ....
Anyway, why are we dying when an invalid session ID is encountered?
Why not log the error and pretend exactly like there was no session id
found at all? Thoughts?
-ash
Oh, and I'm not sure what causing it exactly, but somehow the session
id is getting messed up in the cookie:
DB<10> x $c->get_session_id
0 '5c5ad62b4e9273eb1d5cba69ef4f9e33eeb6ed66, yourpreferences_session'
DB<13> x $c->request->cookies
0 HASH(0x44240c0)
'yourpreferences_session' => CGI::Simple::Cookie=HASH(0x4427700)
'name' => 'yourpreferences_session'
'path' => '/'
'value' => ARRAY(0x44275d4)
0 '5c5ad62b4e9273eb1d5cba69ef4f9e33eeb6ed66,
yourpreferences_session'
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
