ID: 16263
Comment by: sven dot holcombe at gmail dot com
Reported By: kur at natur dot cuni dot cz
Status: No Feedback
Bug Type: Session related
Operating System: ANY
PHP Version: 4.3.0-dev
New Comment:
Running on default XAMPP installation, with the
session.save_path = "C:\xampplite\tmp"
When I set the apache document root to be:
<Directory "C:/xampplite/htdocs">
And then run a file with contents:
<?PHP session_start(); ?>
There is a session file created. Ie, normal operation.
When I set the apache document root to be:
<Directory "S:/htdocs">
And then run THE SAME file with contents:
<?PHP session_start(); ?>
A 0KB session file is created. Ie, it is empty, and I cannot access
session variables.
Please help.
Previous Comments:
------------------------------------------------------------------------
[2009-12-02 18:57:14] john at 5070 dot info
The same issue.
# php-cgi -v
PHP 5.2.6-1+lenny3 with Suhosin-Patch 0.9.6.2 (cgi-fcgi) (built: Apr 26
2009 22:11:16)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator,
by eAccelerator
with Zend Extension Manager v1.2.2, Copyright (c) 2003-2007, by
Zend Technologies
with Suhosin v0.9.27, Copyright (c) 2007, by SektionEins GmbH
with Zend Optimizer v3.3.3, Copyright (c) 1998-2007, by Zend
Technologies
System call trace (in fact, this is processed by mod_php of the same
version):
open(".../sess_a6549.............", O_RDWR|O_CREAT|O_LARGEFILE, 0600) =
1035
fstat64(1035, {st_mode=S_IFREG|0600, st_size=96, ...}) = 0
flock(1035, LOCK_EX) = 0
fcntl64(1035, F_SETFD, FD_CLOEXEC) = 0
fstat64(1035, {st_mode=S_IFREG|0600, st_size=96, ...}) = 0
_llseek(1035, 0, [0], SEEK_SET) = 0
read(1035, "Acess|s:1:\"1\";id|s:3:\"108\";login|"..., 96) = 96
...
ftruncate64(1035, 0) = 0
_llseek(1035, 0, [0], SEEK_SET) = 0
write(1035, ""..., 0) = 0
close(1035) = 0
Session files are shared via NFSv4, if it is important.
------------------------------------------------------------------------
[2009-08-26 18:00:41] chris dot kerrison at farrendale dot co dot uk
Hello, I have theis session problem, tried everything on this page not
still wont work. Is anyone else having the problem still??
I have 2 servers, one it works fine on and the other it fails, they use
the same settings, and have tried differant versions, yet it still fails
on the 2nd server.
Ho many people here are running it on a server with a " _ " in the
computer name? that to me seems the only thing differant between the
computers with my setup.
------------------------------------------------------------------------
[2008-09-12 23:42:19] robin dot chauhan at gmail dot com
As noted on http://www.kirupa.com/forum/showthread.php?t=288773
"After 10 hours of searching over 2 days, I figured it out. The UTF-8
encoding was placing invisible characters before my <?php tag, thus
throwing an error (which I couldn't see because my server host's debug
doesn't show). Switching to ANSI removed those characters and thus the
session_start() functioned properly this time, giving me a consistent
session ID. Thanks to those who helped."
------------------------------------------------------------------------
[2008-06-26 10:50:29] karst at spectraweb dot nl
I have apache/php configured to run as another user then "apache". I
tried to install php-xml and yum updated php, setting the owner of the
directory where the sessions are stored to "apache", NOT MY USER!
This worked for me:
to check if this was the problem I did a chmod 777 to session directory
- and: it worked again
I changed the owner of the session directory to my apache user,
chmodded session directory to the initial 770 - and yay: it worked.
------------------------------------------------------------------------
[2008-06-02 12:45:16] shashibanzal at hotmail dot com
While running a programme as a login for librarian, if the name of
programme is changed in the URL, it switches to the pgm entered now and
the borrower can perform all functions of librarian. This is not
correct. Session start has been used.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/16263
--
Edit this bug report at http://bugs.php.net/?id=16263&edit=1
