Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72499
Return-Path: <yohgaki@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 89477 invoked from network); 12 Feb 2014 07:06:17 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Feb 2014 07:06:17 -0000
Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender)
X-PHP-List-Original-Sender: yohgaki@gmail.com
X-Host-Fingerprint: 209.85.217.181 mail-lb0-f181.google.com  
Received: from [209.85.217.181] ([209.85.217.181:47795] helo=mail-lb0-f181.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 3E/B2-07280-86D1BF25 for <internals@lists.php.net>; Wed, 12 Feb 2014 02:06:17 -0500
Received: by mail-lb0-f181.google.com with SMTP id z11so5829858lbi.12
        for <internals@lists.php.net>; Tue, 11 Feb 2014 23:06:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=8rv1ae844zvLC3s1OXZyI03hIZkUZbwDi/qD7nvfSao=;
        b=PFp1UqotZQp5RePnhJao0SqhRPyhVJw418wNLS5TZGW6HtTYuq1MrQ72oqoyuNVj89
         7NzOW8mgvddcIbt0ji/PI3Ik59mqysa5tKJ38UZxI+/SNTah61+30AjPzty6JM2HtvPx
         FimcS2q3sNriMuclFT6wEVdNp0lrfq9+EEDaZV0Tw9kmqPBbNkEzHb4k5KysmUkrbdkL
         3vyTlJ+lKfW/Pd20Mi9kQX2BmtoLEi8iMpkmTOAlWfoq6G/MPNOJYQXTxQzRPjoyEr33
         Zm7HpmG1v5jcG8PZkIA7YoEARqkR0ley8rvwhFLETrT7nOITca7K3Fdw1x5HzClrGvXg
         Emxg==
X-Received: by 10.112.134.134 with SMTP id pk6mr369213lbb.85.1392188772836;
 Tue, 11 Feb 2014 23:06:12 -0800 (PST)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Received: by 10.112.199.37 with HTTP; Tue, 11 Feb 2014 23:05:32 -0800 (PST)
In-Reply-To: <4ED7146272E04A47B986ED49E771E347BBC71EE85D@Ikarus.ameusgmbh.intern>
References: <4ED7146272E04A47B986ED49E771E347BBC71EE85D@Ikarus.ameusgmbh.intern>
Date: Wed, 12 Feb 2014 16:05:32 +0900
X-Google-Sender-Auth: StbCHIoTZk6MhpkboK8ZI_kL7hs
Message-ID: <CAGa2bXbgLDvehTyGDEPMUjDhKiJoarkzORcTZ+ye_UDpq4bVdA@mail.gmail.com>
To: Christian Stoller <stoller@leonex.de>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01175e7d43ecd104f23035b7
Subject: Re: [PHP-DEV] Empty session cookie leads to warning
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e01175e7d43ecd104f23035b7
Content-Type: text/plain; charset=UTF-8

Hi Christian,

On Tue, Feb 11, 2014 at 4:31 PM, Christian Stoller <stoller@leonex.de>wrote:

> On our server we infrequently get a warning when session_start() is
> called. The message says "The session id is too long or contains illegal
> characters, valid characters are a-z, A-Z, 0-9 and '-,'"
>
> But print_r($_SERVER) in those cases contains only "PHPSESSID" - so the
> session cookie has no value. In my opinion the warning message is a bit
> irritating, or does it have a deeper meaning?
>

What is the reason for having extremely insecure session ID?
Is user sending empty cookie by deleting cookie value?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e01175e7d43ecd104f23035b7--