Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68010 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32746 invoked from network); 28 Jun 2013 21:05:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jun 2013 21:05:42 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:47883] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/43-06897-4AAFDC15 for ; Fri, 28 Jun 2013 17:05:41 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 3FF219812A; Fri, 28 Jun 2013 17:05:38 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id AD88298147; Fri, 28 Jun 2013 17:05:37 -0400 (EDT) Message-ID: <51CDFAA1.3010900@sugarcrm.com> Date: Fri, 28 Jun 2013 14:05:37 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] session.name limitation fix or not fix? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I was browsing bugs and found old feature request that can be fixed easily. > > Request #35703 when session_name("123") consist only digits, should warning > https://bugs.php.net/bug.php?id=35703&thanks=1 > > session.name cannot be integer like string, since it will be initialized as > "long" key hash while session module trying to find as "string" key hash. I > don't understand why some users are willing to use digits only session > name, but problem is problem. Yes, I think we need to generate some message on that, given that such session name would not actually work properly. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227