我在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 中,该 session 在我的 header Blade 中消耗,如下所示:{{ Session::get('usersess') }}并将其放在 header 中。

但是问题是当我刷新PAGE时, session 丢失了!是否有任何线索,如何在不丢失 session 的情况下将其找回?

我已经了解了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,

 );

最佳答案

->with仅将数据刷新到 session 中以用于该页面加载。如果要在 session 中保留项目,请使用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()清除 session 中的所有内容。

session 文档可以在here中找到

09-11 17:30
查看更多