Help getting PHP sessions to persist after being taken off-site

Question

we're working on a payment gateway system with PHP. We use sessions to store the shopping cart data. The system takes you off-site to the payment processor's site, and then return you to your site. On most hosts, we have no issues when we arrive back at our site and having the session data still be there. On those with an issue, turning off the PHP session referer_check has worked in the past. We don't really want to have to include the PHPSESSID as a GET variable, and hope to avoid that. What I'm looking for is what other server configurations would cause the session to be killed, and any other workarounds there might be.

Thanks for your help.

Answer 1

Using cookie-based sessions there's a few possibilities:

• What domain is the cookie set for? mysite.com and secure.mysite.com are not the same.
• Does the problem occur on all web browsers for a given web host?
• Are you calling session_regenerate_id at any point?
• Are you writing out the session cookie and redirecting to the payment processor from the same PHP page? Perhaps the web host is not sending out the correct headers. I'd suggest loading Firebug and checking that the session cookie in the browser matches the current session id on the server.
• When you run phpinfo() on the problem web host does session.refer_check actually have the desired value?

There's a whole lot of possibilities. Here's all the session-related PHP runtime settings many of which could be causing a problem:

http://www.php.net/manual/en/session.configuration.php

Answer 2

我遇到了同样的问题，它主要与Cookie生存期和Cookie域有关，例如，www.example.org与IE的example.org不同。

Answer 3

This aa very shadowy area of PHP security - how to persist the session without exposing a cookie or session id in the url? Unfortunately, the only somewhat safe solution happens to be with a cookie but I'll try and explain a way to make it as safe as possible.

Before the user goes off-site you need to prepare your database to accept them back without needing to provide login details again - create two columns in your user table - "key" and "timeout".

Now, as a user prepares to leave the site through your payment gateway, you need to update their record in the database - generate a unique key to store.

$key = md5(uniqid(rand(), true));

Store this in the datebase along with a timeout (say, an hour or two, or even a whole day - whatever you need). So long as they return within the specified timeframe and can produce the proper key the system will continue to recognize the user and you don't have to worry about logging in again.

Now we need to set a cookie with the same key and, say, a salted md5 hash of their username (just in case). Make sure to give it the same timeout that you gave their record in the database (you don't want old cookies with sensitive information lying around forever).

Once they've returned to the site grab the cookie with the unique ID and their hashed username and compare it to the key/timeout combination in your database. If they match, all is well. Then delete the cookie.

Answer 4

没有cookie，没有会话，仅使用作为附加参数或属性发送到支付系统的uniq id（通常tx id也可以这样做），在返回页url上编写一个函数来识别接收到的uniq ID并进行比较（如果为true则创建）用户的新会话。

Answer 5

As for session timeout problem, it must be the length of time configured in the server. You may need to review the php.ini file of the server.

I have got to know that the following can alter this time:

php_value session.gc_maxlifetime 72000 /* I have not tested this */

I think you can use my method to create a fingerprint id on user session using the following script on the page before leaving out from the website and on the page returning.

$string = $_SERVER['HTTP_USER_AGENT'];
$string .= 'GHYU&*%HHD#JSFHJJFD(*JFJ'; // any long value
        /* Add any other data that is consistent */
$fingerprint = md5($string);



if (isset($_SESSION['HTTP_USER_AGENT']))
    {
        if ($_SESSION['HTTP_USER_AGENT'] !== $fingerprint)
        {
            /* Prompt for password */
            session_destroy();
            header("Location:"."URL/PATH/TO/LOGIN");
        }
    }
else
    {   
        $_SESSION['HTTP_USER_AGENT'] = $fingerprint;
}