PHP会话启动打开文件而不是数据库连接

时间:2017-11-29 08:50:38

标签: php mysql session oauth

经过几天的摔跤之后,我才注意到以下错误信息中的路径看起来很奇怪。

open(/ var / lib / php / session / sess_fvc591eu71mbrc4tabgtr83pg7,O_RDWR)失败:

有两件事让我感到奇怪。

  1. 目标似乎是/ var / lib / php /下的目录,这对于脚本创建输出文件来说似乎是一个非常奇怪的地方。
  2. 该脚本应该将其会话数据存储在MySQL数据库中。
  3. 以下是精简堆栈跟踪。

    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' => env ( 'SESSION_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' => 'mysql',
    
    /*
    |------------------------------------------------------------------------
    | 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 Cache Store
    |------------------------------------------------------------------------
    |
    | When using the "apc" or "memcached" session drivers, you may specify a
    | cache store that should be used for these sessions. This value must
    | correspond with one of the application's configured cache stores.
    |
    */
    
    'store' => null,
    
    /*
    |------------------------------------------------------------------------
    | 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' => env('SESSION_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' => env('SESSION_SECURE_COOKIE', true),
    
    /*
    |------------------------------------------------------------------------
    | HTTP Access Only
    |------------------------------------------------------------------------
    |
    | Setting this value to true will prevent JavaScript from accessing the
    | value of the cookie and the cookie will only be accessible through
    | the HTTP protocol. You are free to modify this option if needed.
    |
    */
    
    'http_only' => true,
    
    ];
    

    以下是环境数组中的关键项,取自本地XDebug会话。

    SELECT column_name(s)
    FROM table_name
    WHERE condition
    GROUP BY column_name(s)
    ORDER BY column_name(s);
    

    该应用程序使用的是基于PHP 5.6.32的LARAVEL 5框架,在Amazon Linux实例中运行,并且会话由LARITANIAN OAUTH模块管理,用于LARAVEL,我怀疑它忽略了环境中的会话设置。 / p>

    以下是我的整个会话配置文件。

    select [date], [cage no], count([staff])
    from [table]
    where date between '2017-11-01' and '2017-11-27'
    group by [date],[cage no]
    order by [date] asc,[cage no] asc
    

    所有欢呼频率都是敞开的。

1 个答案:

答案 0 :(得分:0)

简短的回答是,我们发现所讨论的库与内部PHP Session对象硬接线,这似乎仅限于使用文件系统作为其后备存储。自那时起,我们就放弃了这个图书馆,并且正在实施Stephen Maguire为PHP联盟的OAuth2库提供专门的Salesforce提供商。