Php Laravel会话在每个页面加载时都未设置

每次加载页面时，我的会话数据都会被取消设置。我在尝试创建用户登录区域时注意到了这一点。Auth：：尝试工作正常，但在下一页加载时，Auth用户数据已丢失

我通过在Auth:：trunt之后设置会话来检查会话，然后在Auth筛选器中检查会话，但会话数据不在那里。这是我的config/session.php内容

 <?php

return array(

/*
|--------------------------------------------------------------------------
| 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' => 'file',

/*
|--------------------------------------------------------------------------
| 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 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().'/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' => array(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' => 'lodgesdirect',

/*
|--------------------------------------------------------------------------
| 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' => 'test_path',

/*
|--------------------------------------------------------------------------
| 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,

);

---

会话或持久化是一个常见问题。当您在实际将某些内容保存到会话之前输出一些数据时，就会发生这种情况。它不输出任何错误消息，并且很难调试。当然，您没有任何

echo

print（）

或

headers（）

在

Auth:：trunt（）

或

Session:：put（）之前的相关命令

解决这一问题的方法之一，是使用新鲜的Laravel装置。这需要时间，但很多时候它可以解决像这样的神秘问题。
我也有同样的问题，然后我尝试了

Session::save();

将数据放入/推入会话后

编辑

我的问题是，每次我尝试创建会话并将数据推送到会话时，它都会很好地返回。但是，如果我刷新页面，它只会再次执行相同的操作，而不会向会话添加数据

if(Session::has('mySession'))
{
    //Session exists because of the Session::save, lets push
    Session::push('mySession', 'World!');
}
else 
{
    Session::put('mySession', ['Hello']);
}

Session::save();

我也有同样的问题，所以我添加了session_start（）；顶部的public/index.php中的代码。我的问题解决了
 好的，在保存会话之前，我将检查是否输出了任何数据。谢谢你的时间。我也经历了同样的经历，这也解决了我的问题。谢谢你的帮助。谢谢。我的团队从早上就开始打猎了。这节省了很多未知的时间。