【问题标题】:Laravel Session Missing after Page Refresh页面刷新后 Laravel 会话丢失
【发布时间】: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 给出了解决方案。谢谢您的帮助! :)

标签: php session laravel


【解决方案1】:

->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找到

【讨论】:

  • 那么当我想删除会话时,只需使用 Auth::logout();或者只使用 Session::flush(); ?
  • 那么我将使用flush for logout方法:)感谢您的帮助!
【解决方案2】:

我在使用时遇到了这个问题

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');

【讨论】:

  • 谢谢,在我的情况下,这是由 dd() 引起的,该 dd() 阻止了请求完成并因此阻止了会话被存储:请参阅 here
【解决方案3】:

我想为此做出贡献,因为我遇到了同样的问题,但我的解决方案与投票的不同。

将项目放入我的会话后,它们似乎在下一页加载时消失了。

我这样做的方式是通过 AJAX 调用。每当我进行 AJAX 调用时,我总是在最后使用 exit,以防止任何不必要的页面处理。我发现这个exit 阻止了 Laravel 进一步进行并将数据写入永久会话。

星狐之声:祝你好运!

【讨论】:

  • 谢谢,我是用“dd()”测试的,没想到这个问题。
  • 我不确定我在调试会话问题上浪费了多少时间 dd()var_dump()+exit,直到我发现这条评论并意识到我正在破坏会话本身。非常感谢!
【解决方案4】:

这显然不是你的问题,但对于发现这个问题并且接受的答案不能解决你的问题的其他人来说,这可能:

如果您将 laravel 会话存储在数据库中,则该会话值的大小是有限制的。 Laravel 会话迁移有一个名为“payload”的字段,它是一个文本类型。如果您超出该字段的限制,则整个会话将被终止。当我将 json 模型数据动态添加到我的会话时,这发生在我身上。

Schema::create('sessions', function (Blueprint $table) {
    $table->string('id')->unique();
    $table->text('payload');
    $table->integer('last_activity');
});

How much UTF-8 text fits in a MySQL "Text" field?

【讨论】:

    【解决方案5】:

    检查您是否没有删除 .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;
    

    【讨论】:

      猜你喜欢
      • 2017-01-13
      • 2019-05-16
      • 2014-08-16
      • 1970-01-01
      • 2023-03-25
      • 2014-12-31
      • 1970-01-01
      • 2018-08-22
      • 1970-01-01
      相关资源
      最近更新 更多