Hi group,
My current app under development needs to accept a session id from a
referring (non-CGI:App) application, which uses the same 32-digit
construct (MD5) as used by CGI::Session. The session identifier is
passed in the url, so can be captured by the new application as part of
the query. So I have created a new cgi parameter called CGISESSID and
tried to make CGI::Session use it as follows:
my ($session_id) = $cgi->param('uid') =~ /\w+\.([a-z0-9]{32})/;
$cgi->param(CGISESSID => $session_id);
$obj->session_config(
CGI_SESSION_OPTIONS => [ "driver:MySQL", $cgi, { Handle => $dbh, } ],
);
But although $cgi->param('CGISESSID') contains the expected 32-digit
session id from the referring app, it does not get used to create the
new session, and a new 32-digit session identifier is generated instead.
I also tried substituting $session_id for $cgi in the
CGI_SESSION_OPTIONS block.
Presumably this is not the correct way to handle new session id
generation in CGI::Session. Is it even possible to force CGI::Session to
use a pre-defined session id string in the first place?
***************************************************************************
This e-mail is confidential and privileged. If you are not the intended
recipient please accept our apologies; please do not disclose, copy or
distribute information in this e-mail or take any action in reliance on its
contents: to do so is strictly prohibited and may be unlawful. Please
inform us that this message has gone astray before deleting it. Thank you
for your co-operation.
***************************************************************************
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
