loadbalancer and session management

posted 9 years ago

Hello,

I'm on laravel 4.2, and have inconsistency of the session management

I have this configuration for session (app/config/production/session.php) :

return array(
        'driver'            => 'memcached',
        'host'              => 'memcached sever',
        'lifetime'          => 120,
        'expire_on_close'   => false,
        'lottery'           => array(2, 100),
        'cookie'            => 'cookies_sessions',
        'path'              => '/',
        'table'             => 'table-sessions',
        'domain'            => null,
        'secure'            => false,
);

And this other as base (app/config/session.php) :

<?php
return array(
	'driver' => 'file',
	'lifetime' => 120,
	'expire_on_close' => false,
	'files' => storage_path().'/sessions',
	'connection' => null,
	'table' => 'sessions',
	'lottery' => array(2, 100),
	'cookie' => 'laravel_session',
	'path' => '/',
	'domain' => null,
	'secure' => false,
);

But when I print Session::all() I see that from one request to another the token change (from the instance given by the loadbalancer, stay the same token on the same relative instance).

How can I manage the sessions through the loadbalancer (I have other php application that goes well, so the issue is not on the loadbalancer itself but on my configuration of laravel projet)?

thanks

Last updated 2 years ago.

ikanc

replied 9 years ago

Solution

Hi,

Are you sure that your production configuration is loaded and you are not working on the global settings?

grummfy

replied 9 years ago

Every other value of configuration are loaded from production. Well, if you have a simple way to check it, I will try.

Edit : Well after displayed the configuration (var_dump(Config::get('session'));) I justfix an error in the configuration (port and host were merged). It's working well ;)

But I still have a problem : when I log to the system, it's not logged directly, , I got this : log page => log post => log page => log post => error (double login) log page => log post => refresh on another page and its' ok

Last updated 9 years ago.

Moderators