为什么使用 Laravel 5.x 刷新时会话会消失？

Question

我有一个用于创建会话的简单文件，如下所示：

<?php namespace App\Repositories\Managers;

use Illuminate\Support\Facades\Session;
use Carbon\Carbon;

class SessionTest {

    public function __construct()
    {
    }

    public function sessionTest()
    {
        Session::put('test', 111);
        dd(Session::all());
    }
}

它让我按预期获得了正确的会话。

array:4 [▼
  "_token" => "pYbrTbhnsLx6BfUNZusedQSYiBGxL3t9W7IyRVAh"
  "_previous" => array:1 [▶]
  "flash" => array:2 [▼
    "old" => []
    "new" => []
  ]
  "test" => 111
]

现在由于某种原因，当我打开另一个页面并显示 Session::all() 时，它会返回以下内容：

array:3 [▼
  "_token" => "pYbrTbhnsLx6BfUNZusedQSYiBGxL3t9W7IyRVAh"
  "_previous" => array:1 [▶]
  "flash" => array:2 [▼
    "old" => []
    "new" => []
  ]
]

基本上，一旦我打开一个新页面，它就会删除所有 Session 存储。

我的 session.php 文件如下所示：

<?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' => env('SESSION_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 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' => 'ck_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,

];

当我检查会话文件时，它似乎没有被写入。它只存储默认值。

这里的主要问题是什么？以前从未遇到过同样的情况。

Answer 1

在 dd() 之前试试这个命令：

Session::save()

Session::save() 在渲染到视图时会被自动调用。在您的情况下，您在调用此函数之前退出。所以你的会话没有保存

Answer 2

您是否为应用程序中的存储目录正确分配了写入权限（即 777）。这可能会导致问题。

Answer 3

用途：

use Symfony\Component\HttpFoundation\Session\Session;

而不是

use Illuminate\Support\Facades\Session;

---

//to set a session variable use
$session = new Session();
$session->set('variableName', $requestData['key']);

//to get that session variable
$session = new Session();
$session->get('variableName');

Answer 4

问题是我删除了 JavaScript 中的 cookie，所以也许在刷新之前检查你是否没有在 .js 中使用类似的东西：

var now = new Date();
now.setTime(now.getTime()+(-1*24*60*60*1000));
var expires = "=;"+" path=/; expires="+now.toUTCString();
document.cookie = "lastpage"+expires;