Re: SSL & normal sessions stored differently?
| From: | James Benson | Date: | Thu, 03 Nov 2005 16:22:06 +0000 |
| Subject: | Re: SSL & normal sessions stored differently? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-225056@lists.php.net to get a copy of this message | ||
Could it be you have two differnt domain names, PHP could be using a different cookie/session for each one.
Jesse Guardiani wrote:
Hello, I'm running php-4.3.2-19.ent under httpd-2.0.46-44.ent on Red Hat Enterprise Linux ES release 3 (Taroon Update 4). Here is my Session section of php.ini: ------------------------------ [Session] session.save_handler = files session.use_cookies = 1 session.name = PHPSESSID session.auto_start = 1 session.cookie_lifetime = 0 session.cookie_path = / session.cookie_domain = session.serialize_handler = php session.gc_probability = 1 session.gc_divisor = 200 session.gc_maxlifetime = 36000 session.referer_check = session.entropy_length = 0 session.entropy_file = session.entropy_length = 16 session.entropy_file = /dev/urandom session.cache_limiter = nocache session.cache_expire = 0 session.use_trans_sid = 1 ------------------------------ My problem is that normal session variables don't seem to be accessible from an instance of PHP servicing an SSL connection. For example, I can put this in test.php: session_id('bob'); session_start(); echo var_export($_SESSION,true); And get different results depending on whether I call:http://www.example.com/test.phpOr:https://secure.example.com/test.phpThe session variables seem to be stored in different places, even though the save_path is identical. Does anyone know why this happens and/or how to work around it? Thanks! Jesse Guardiani jesse@wingnet.net