in reply to Problems with setting session variables in Catalyst

Actually, you both were on the right track. Using the example from Catalyst::Plugin::Session::Store worked. I did look at the docs while I was doing this -- several times -- but not this one. This is completely different than the example given in the Catalyst tutorial and in Catalyst::Plugin::Session, which were the two examples I cited.

Also, the generated token wasn't playing well with Memcached. I discovered Session::Token though and that works perfectly in place of Crypt::Random. It's been a while since I've done any serious Perl coding, so I'm still getting back on my feet again and relearning the ecosystem.

Thanks for both your help.

  • Comment on Re: Problems with setting session variables in Catalyst

Replies are listed 'Best First'.
Re^2: Problems with setting session variables in Catalyst (csrf/xsrf/nonce)
by Anonymous Monk on Aug 12, 2014 at 02:55 UTC

    Actually, you both were on the right track. ...Using the example from Catalyst::Plugin::Session::Store worked. I did look at the docs while I was doing this -- several times -- but not this one....

    Yup, you normally wouldn't use this API (its the low level), but if it doesn't work using this api, then something is really wrong :)

    OTOH, have you seen ?? Catalyst::Controller::RequestToken - Handling transaction tokens across forms update: nevermind, doesn't seem to use Session::Token probably not worth investigating further :)

      I did look at that, yes, but it seemed to conflict with using Catalyst::Controller::REST, so I went with my own solution. I'm much happier with Session::Token.