我有一个简单的文件，我正在创建会话，它看起来像这样:
<?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.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,
];
当我检查它时，似乎会话文件没有被写入。它只存储默认值。
这里的主要问题是什么?从来没有面对过同样的事情。
在dd():
之前试试这个命令Session::save()
Session::save()将在渲染到视图时自动调用。在您的示例中，在调用此函数之前退出。所以你的会话没有保存
您是否为应用程序中的存储目录正确分配了写权限(即777)?
使用说明:
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');
问题是我在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;