【发布时间】:2014-07-20 10:00:02
【问题描述】:
我对 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') }} 并将其放在标题中。
但问题是当我刷新页面时,会话丢失了!是否有任何线索,如何在不丢失会话的情况下将其取回?
我已经了解了 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,
);
【问题讨论】:
-
你能发布你的 app/config/session.php 文件吗?
-
@TheShiftExchange 请参阅更新的部分。无论如何,仅供参考,我将刀片放入两个不同的页面。哪个索引扩展了标题。我将会话放在标题刀片中,但我的路由将转到索引刀片。有问题吗?
-
你不应该把 session_start() 放在你代码的任何地方——Laravel 会为你处理所有的会话包装。
-
@TheShiftExchange,RMcLeod 给出了解决方案。谢谢您的帮助! :)