Laravel 5.1会话随机过期

8
我有一个L5.1应用程序,在使用过程中会随机出现会话过期的问题。这种情况发生在我的本地环境和线上环境,所以看起来不是服务器的问题。在本地,我使用的是安装了PHP 5.5.11版本的XAMPP。线上网站运行在Centos 6上的专用服务器中,PHP版本为5.6.13。
只要在网站上浏览大约20-30个页面请求后,会话就会丢失,因此用户需要重新登录。我正在使用数据库驱动程序,并且以下是我的会话配置:
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Session Driver
    |--------------------------------------------------------------------------
    |
    | This option controls the default session "driver" that will be used on
    | requests. By default, we will use the lightweight native driver but
    | you may specify any of the other wonderful drivers provided here.
    |
    | Supported: "file", "cookie", "database", "apc",
    |            "memcached", "redis", "array"
    |
    */

    'driver' => 'database',

    /*
    |--------------------------------------------------------------------------
    | Session Lifetime
    |--------------------------------------------------------------------------
    |
    | Here you may specify the number of minutes that you wish the session
    | to be allowed to remain idle before it expires. If you want them
    | to immediately expire on the browser closing, set that option.
    |
    */

    'lifetime' => 120,

    'expire_on_close' => false,

    /*
    |--------------------------------------------------------------------------
    | Session Encryption
    |--------------------------------------------------------------------------
    |
    | This option allows you to easily specify that all of your session data
    | should be encrypted before it is stored. All encryption will be run
    | automatically by Laravel and you can use the Session like normal.
    |
    */

    'encrypt' => false,

    /*
    |--------------------------------------------------------------------------
    | Session File Location
    |--------------------------------------------------------------------------
    |
    | When using the native session driver, we need a location where session
    | files may be stored. A default has been set for you but a different
    | location may be specified. This is only needed for file sessions.
    |
    */

    'files' => storage_path('framework/sessions'),

    /*
    |--------------------------------------------------------------------------
    | Session Database Connection
    |--------------------------------------------------------------------------
    |
    | When using the "database" or "redis" session drivers, you may specify a
    | connection that should be used to manage these sessions. This should
    | correspond to a connection in your database configuration options.
    |
    */

    'connection' => null,

    /*
    |--------------------------------------------------------------------------
    | Session Database Table
    |--------------------------------------------------------------------------
    |
    | When using the "database" session driver, you may specify the table we
    | should use to manage the sessions. Of course, a sensible default is
    | provided for you; however, you are free to change this as needed.
    |
    */

    'table' => 'sessions',

    /*
    |--------------------------------------------------------------------------
    | Session Sweeping Lottery
    |--------------------------------------------------------------------------
    |
    | Some session drivers must manually sweep their storage location to get
    | rid of old sessions from storage. Here are the chances that it will
    | happen on a given request. By default, the odds are 2 out of 100.
    |
    */

    'lottery' => [2, 100],

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Name
    |--------------------------------------------------------------------------
    |
    | Here you may change the name of the cookie used to identify a session
    | instance by ID. The name specified here will get used every time a
    | new session cookie is created by the framework for every driver.
    |
    */

    'cookie' => 'laravel_session',

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Path
    |--------------------------------------------------------------------------
    |
    | The session cookie path determines the path for which the cookie will
    | be regarded as available. Typically, this will be the root path of
    | your application but you are free to change this when necessary.
    |
    */

    'path' => '/',

    /*
    |--------------------------------------------------------------------------
    | Session Cookie Domain
    |--------------------------------------------------------------------------
    |
    | Here you may change the domain of the cookie used to identify a session
    | in your application. This will determine which domains the cookie is
    | available to in your application. A sensible default has been set.
    |
    */

    'domain' => null,

    /*
    |--------------------------------------------------------------------------
    | HTTPS Only Cookies
    |--------------------------------------------------------------------------
    |
    | By setting this option to true, session cookies will only be sent back
    | to the server if the browser has a HTTPS connection. This will keep
    | the cookie from being sent to you if it can not be done securely.
    |
    */

    'secure' => false,

];

由于我没有手动清除任何会话,所以我相当有信心我的操作不会导致这种情况发生。是否已知有任何可能导致此行为的 bug?


1
建议在登录时添加一个中间件,根据设置的“恢复令牌”cookie自动重新登录用户。将令牌有效期设置为等于或大于会话持续时间。否则,您将受制于会话存储和Laravel的错误抽奖功能。 - r3wt
2个回答

8
如果您正在使用数据库驱动程序,则有时可能会遇到payload字段太短的问题。默认情况下,payload字段是一个text字段,允许64KB的数据。
这似乎很多,但由于负载存储为序列化数组(基本上是一个非常长的字符串),然后进行base64编码,因此它很容易达到其最大长度,这将有效地使该用户的会话损坏。
我建议将数据类型更改为MEDIUMTEXT(最大16MB),或重新考虑首先保存到会话中的数据量。

1
哦,我的天啊,Mikemike,你真是个天才,非常感谢!我一定要请你喝一杯!像你说的那样,我认为长期来看,我需要重新考虑我在会话中存储的信息,但是暂时将列更改为mediumtext已经解决了问题。 - geoffs3310

1
请在同一文件中进一步检查您的会话扫描抽奖 config/session.php
/*
|--------------------------------------------------------------------------
| Session Sweeping Lottery
|--------------------------------------------------------------------------
|
| Some session drivers must manually sweep their storage location to get
| rid of old sessions from storage. Here are the chances that it will
| happen on a given request. By default, the odds are 2 out of 100.
|
*/

'lottery' => [2, 100],

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接