我对Laravel的会话有一点问题。
我已经完成了这样的身份验证功能：
public function postSignin(){
$attempt = Auth::attempt(array('username' => Input::get('username'), 'password' => Input::get('password')));
if ($attempt) {
return Redirect::to('index')->with('message', 'Anda telah login!' . $attempt)
->with('usersess', Input::get('username'));
} else if(!$attempt){
return Redirect::to('auth')
->with('message', 'Kombinasi email/password salah ' . $attempt)
->withInput();
}
}
让我看看我已经将'usersess' var发送到会话中，我在我的标头片段中使用了这个：{{ Session::get('usersess') }}并将其放在标题中。
但问题是当我刷新PAGE时，会话丢失了！有没有任何线索，如何在不缺少会话的情况下取回它？
我已经了解了php并且使用<?php session_start() ?>是基本功能，但是如何在laravel中工作？
更新我的session.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' => 180,
'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' => 'invsess',
/*
|--------------------------------------------------------------------------
| 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,
);
答案 0 :(得分：6)
->with仅向该会话加载数据以加载该页面。如果您想在会话中保留一个项目，请使用Session::put('key', 'value')。所以对你的例子来说：
if($attempt) {
Session::put('usersess', Input::get('username'));
return Redirect::to('index')->with('message', 'Anda telah login!' . $attempt);
}
修改
您可以使用Session::get('key')检索值，或Session::pull('key')返回值并忘记值。您还可以使用Session::forget('key')删除项目。 Session::flush()清除会话中的所有内容。
可以找到会话文档here
答案 1 :(得分：3)
自从我遇到同样的问题以来，我想为此做出贡献，但我的解决方案与投票后的解决方案不同。
将项目放入我的会话后，它们似乎在下一页加载时消失。
我这样做的方式是通过AJAX调用。每当我进行AJAX调用时，我总是在最后使用exit，以防止任何不必要的页面处理。我发现这个exit阻止了Laravel进一步推进并实际将这些数据写入常会。
Star Fox的声音：祝你好运！
答案 2 :(得分：1)
当我使用
时，这个问题正在发生use Illuminate\Support\Facades\Session;
而不是它，你可以使用
use Symfony\Component\HttpFoundation\Session\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');
答案 3 :(得分：1)
这显然不是您的问题，但对于发现此问题的任何其他人而言，接受的答案并未解决您的问题：
如果要将laravel会话存储在数据库中，则会话值的大小有限制。 Laravel会话迁移有一个名为“payload”的字段，它是一种文本类型。如果超过该字段的限制，整个会话将被终止。当我在我的会话中动态添加json模型数据时，这发生在我身上。
Schema::create('sessions', function (Blueprint $table) {
$table->string('id')->unique();
$table->text('payload');
$table->integer('last_activity');
});
答案 4 :(得分：0)
检查您是否删除了.js中的cookie。 这对我来说是个问题：
var now = new Date();
now.setTime(now.getTime()+(-1*24*60*60*1000));
var expires = "=;"+" path=/; expires="+now.toUTCString();
document.cookie = "lastpage"+expires;