RE: [PHP] PHPSESSID sticks to every link after upgrate of Apache/PHP
In your php.ini, change the following line:
>session.use_trans_sid = 1 ; use transient sid support if enabled
to
>session.use_trans_sid = 0 ; use transient sid support if enabled
And see if that solves your problem. Also, check the change with phpinfo(),
and if nothing changed, look for a second evil twin of php.ini
-Ben
-Original Message-
From: trogers [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 08, 2001 6:59 PM
To: 'PHP General List. (E-mail)'
Subject: Re: [PHP] PHPSESSID sticks to every link after upgrate of
Apache/PHP
Hi
You will probably need to make clean and rebuild php config and do a new
make against the new version of apache.
Just a guess
Tom
At 12:28 PM 5/04/01 +0900, Maxim Maletsky wrote:
>
>Hello,
>
>my co-worker has reinstalled Apache and PHP over the last night.
>
>The Apache was upgraded to the new version while PHP was re-installed the
>same.
>PHP.ini was untouched.
>
>Site uses sessions and, somehow, after this upgrade started carrying
>PHPSESSID through HREF.
>
>What should look for to bring the sessions using Cookies?
>
>from PHP-INI:
>
>NOTE : this was untouched.
>
>
>
>[Session]
>session.save_handler = files ; handler used to store/retrieve data
>session.save_path = /tmp; argument passed to save_handler
> ; in the case of files, this is the
> ; path where data files are stored
>session.use_cookies = 1 ; whether to use cookies
>session.name = PHPSESSID ; name of the session
> ; is used as cookie name
>session.auto_start= 0 ; initialize session on request startup
>session.cookie_lifetime = 0 ; lifetime in seconds of cookie
> ; or if 0, until browser is restarted
>session.cookie_path = / ; the path the cookie is valid for
>session.cookie_domain = ; the domain the cookie is valid for
>session.serialize_handler = php ; handler used to serialize data
> ; php is the standard serializer of
PHP
>session.gc_probability= 1 ; percentual probability that the
> ; 'garbage collection' process is
>started
> ; on every session initialization
>session.gc_maxlifetime= 1440; after this number of seconds, stored
> ; data will be seen as 'garbage' and
> ; cleaned up by the gc process
>session.referer_check = ; check HTTP Referer to invalidate
> ; externally stored URLs containing
ids
>session.entropy_length= 0 ; how many bytes to read from the file
>session.entropy_file = ; specified here to create the session
>id
>; session.entropy_length= 16
>; session.entropy_file = /dev/urandom
>session.cache_limiter = nocache ; set to {nocache,private,public} to
> ; determine HTTP caching aspects
>session.cache_expire = 180 ; document expires after n minutes
>session.use_trans_sid = 1 ; use transient sid support if enabled
> ; by compiling with --enable-trans-sid
>=
>
>
>Has upgrade of apache (modules, etc) anything to do with it?
>
>I can't really give you any more details since my co-coworker is
unreachable
>right now, and this is kinda urgent.
>
>Cheers,
>Max.
>
>
>
>Maxim Maletsky - [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>Webmaster, J-Door.com / J@pan Inc.
>LINC Media, Inc.
>TEL: 03-3499-2175 x 1271
>FAX: 03-3499-3109
>
>http://www.j-door.com <http://www.j-door.com/>
>http://www.japaninc.net <http://www.japaninc.net/>
>http://www.lincmedia.co.jp <http://www.lincmedia.co.jp/>
>
>
>
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP] PHPSESSID sticks to every link after upgrate of Apache/PHP
Hi
You will probably need to make clean and rebuild php config and do a new
make against the new version of apache.
Just a guess
Tom
At 12:28 PM 5/04/01 +0900, Maxim Maletsky wrote:
>
>Hello,
>
>my co-worker has reinstalled Apache and PHP over the last night.
>
>The Apache was upgraded to the new version while PHP was re-installed the
>same.
>PHP.ini was untouched.
>
>Site uses sessions and, somehow, after this upgrade started carrying
>PHPSESSID through HREF.
>
>What should look for to bring the sessions using Cookies?
>
>from PHP-INI:
>
>NOTE : this was untouched.
>
>
>
>[Session]
>session.save_handler = files ; handler used to store/retrieve data
>session.save_path = /tmp; argument passed to save_handler
> ; in the case of files, this is the
> ; path where data files are stored
>session.use_cookies = 1 ; whether to use cookies
>session.name = PHPSESSID ; name of the session
> ; is used as cookie name
>session.auto_start= 0 ; initialize session on request startup
>session.cookie_lifetime = 0 ; lifetime in seconds of cookie
> ; or if 0, until browser is restarted
>session.cookie_path = / ; the path the cookie is valid for
>session.cookie_domain = ; the domain the cookie is valid for
>session.serialize_handler = php ; handler used to serialize data
> ; php is the standard serializer of PHP
>session.gc_probability= 1 ; percentual probability that the
> ; 'garbage collection' process is
>started
> ; on every session initialization
>session.gc_maxlifetime= 1440; after this number of seconds, stored
> ; data will be seen as 'garbage' and
> ; cleaned up by the gc process
>session.referer_check = ; check HTTP Referer to invalidate
> ; externally stored URLs containing ids
>session.entropy_length= 0 ; how many bytes to read from the file
>session.entropy_file = ; specified here to create the session
>id
>; session.entropy_length= 16
>; session.entropy_file = /dev/urandom
>session.cache_limiter = nocache ; set to {nocache,private,public} to
> ; determine HTTP caching aspects
>session.cache_expire = 180 ; document expires after n minutes
>session.use_trans_sid = 1 ; use transient sid support if enabled
> ; by compiling with --enable-trans-sid
>=
>
>
>Has upgrade of apache (modules, etc) anything to do with it?
>
>I can't really give you any more details since my co-coworker is unreachable
>right now, and this is kinda urgent.
>
>Cheers,
>Max.
>
>
>
>Maxim Maletsky - [EMAIL PROTECTED]
>Webmaster, J-Door.com / J@pan Inc.
>LINC Media, Inc.
>TEL: 03-3499-2175 x 1271
>FAX: 03-3499-3109
>
>http://www.j-door.com
Re: [PHP] PHPSESSID sticks to every link after upgrate of Apache/PHP
Hm...what browser are you using to test the site?
By using the trans_id option I believe that tells PHP to append the sessid
into the url if the cookie is not being accepted.
Try turning it off and trying it, and you may need to comment out the
url.rewriter thing directly under that option.
Try having someone else test your site using a different browser. Try IE 5,
5.5, and the new version of Netscape. All with cookies enabled.
If your site still is appending to the url, then something else is wrong.
--
Plutarck
Should be working on something...
...but forgot what it was.
"Maxim Maletsky" <[EMAIL PROTECTED]> wrote in message
DC017B079D81D411998C009027B7112A015ED065@EXC-TYO-01">news:DC017B079D81D411998C009027B7112A015ED065@EXC-TYO-01...
>
> Hello,
>
> my co-worker has reinstalled Apache and PHP over the last night.
>
> The Apache was upgraded to the new version while PHP was re-installed the
> same.
> PHP.ini was untouched.
>
> Site uses sessions and, somehow, after this upgrade started carrying
> PHPSESSID through HREF.
>
> What should look for to bring the sessions using Cookies?
>
> from PHP-INI:
>
> NOTE : this was untouched.
>
>
>
> [Session]
> session.save_handler = files ; handler used to store/retrieve data
> session.save_path = /tmp; argument passed to save_handler
> ; in the case of files, this is the
> ; path where data files are stored
> session.use_cookies = 1 ; whether to use cookies
> session.name = PHPSESSID ; name of the session
> ; is used as cookie name
> session.auto_start= 0 ; initialize session on request
startup
> session.cookie_lifetime = 0 ; lifetime in seconds of cookie
> ; or if 0, until browser is restarted
> session.cookie_path = / ; the path the cookie is valid for
> session.cookie_domain = ; the domain the cookie is valid for
> session.serialize_handler = php ; handler used to serialize data
> ; php is the standard serializer of
PHP
> session.gc_probability= 1 ; percentual probability that the
> ; 'garbage collection' process is
> started
> ; on every session initialization
> session.gc_maxlifetime= 1440; after this number of seconds, stored
> ; data will be seen as 'garbage' and
> ; cleaned up by the gc process
> session.referer_check = ; check HTTP Referer to invalidate
> ; externally stored URLs containing
ids
> session.entropy_length= 0 ; how many bytes to read from the file
> session.entropy_file = ; specified here to create the session
> id
> ; session.entropy_length= 16
> ; session.entropy_file = /dev/urandom
> session.cache_limiter = nocache ; set to {nocache,private,public} to
> ; determine HTTP caching aspects
> session.cache_expire = 180 ; document expires after n minutes
> session.use_trans_sid = 1 ; use transient sid support if enabled
> ; by compiling with --enable-trans-sid
> =
>
>
> Has upgrade of apache (modules, etc) anything to do with it?
>
> I can't really give you any more details since my co-coworker is
unreachable
> right now, and this is kinda urgent.
>
> Cheers,
> Max.
>
>
>
> Maxim Maletsky - [EMAIL PROTECTED]
> Webmaster, J-Door.com / J@pan Inc.
> LINC Media, Inc.
> TEL: 03-3499-2175 x 1271
> FAX: 03-3499-3109
>
> http://www.j-door.com
Re: [PHP] PHPSESSID sticks to every link after upgrate of Apache/PHP
Maxim Maletsky wrote: > > Site uses sessions and, somehow, after this upgrade started carrying > PHPSESSID through HREF. Sounds to me like php was compliled with the --enable-trans-sid option which does exactly that. Just a guess. Regards Joseph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
