We're using Drupal on a number of sites. On all but one server, the
data in the sessions table appears as a serialised string. This is
normal behaviour AFAIK.
Here's an example session entry from site A - this is what I'd like to
see:
captcha|a:1:{s:12:"comment_form";a:3:{s:
32:"5ce32afb28f38e2ec854eb2f9340e2e5";b:1;s:7:"success";b:0;s:
32:"ba52f551aa38e84111938ef9fc2111e4";b:1;}}
And here's one from site B, with the "encoded" session data:
tYeyamtSbI6U_Z5a0DXCwL1pwoY5DUBDNOTDjyftul9Z4TLMMDdVr_8HxPWTleQ8wrTIEPyRAdxb6Ukz69tSEQ..
The encoded values always end with a period (often two). I don't
recognise the encoding method.
Is it the result of PHP's session.serialize_handler configuration
seting? I've tried setting ini_set('session.serialize_handler') to
'php' and 'php_binary', but didn't see any change in format when the
sessions were written to the DB.
My aim is to make site B store sessions in a format matching site A.
--~--~---------~--~----~------------~-------~--~----~
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]
-~----------~----~----~----~------~----~------~--~---
