Laravel 5.1登录表单提交时令牌不匹配

4

我收到以下错误:TokenMismatchException in compiled.php line 2930:

该代码在运行在一个 Red Hat 服务器 上,使用的是 php 5.6 ,我也在运行 php 5.5.9Ubuntu 服务器 上进行了测试,结果完全正常。本地运行也完全正常。

原始的 GET 请求似乎会在 storage/framework/sessions 中创建两个会话文件,这意味着当通过 POST 发送表单时,会话就不同了。

我已经检查了:

  • 重定向
  • 服务器上的日期/时区问题
  • session.phpapp.php 中的设置问题

最奇怪的是为什么在 GET 请求时会生成两个会话文件。

一旦点击登录按钮,就会触发 csrf 中间件,显示令牌不匹配。

我正在使用表单的 HTML 生成器,这意味着 _token 已经被设置,因此不需要手动操作。

表单代码

{!! Form::open(['action' => 'Auth\AuthController@login']) !!}

<div class="panel">

    <div class="panel-title">
        Login
    </div>

    <div class="panel-body">

        <div class="grid">

            <div class="grid-2-4 grid-prepend-1-4 grid-append-1-4">

                @include('shared._errors')

                <div class="field">
                    {!! Form::label('username', 'Employee username') !!}
                    {!! Form::text('username') !!}
                </div>

                <div class="field">
                    {!! Form::label('password', 'Password') !!}
                    {!! Form::password('password') !!}
                </div>

                <div class="actions">
                    {!! Form::submit('Login', ['class' => 'button large']) !!}
                </div>

            </div>

        </div>

    </div>

</div>

{!! Form::close() !!}

会话配置

<?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' => 45,

    'expire_on_close' => true,

    /*
    |--------------------------------------------------------------------------
    | 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' => 'geeksquad_form_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' => '.'.config('app.domain'),

    /*
    |--------------------------------------------------------------------------
    | 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,

];

如果还有其他有帮助的内容,请告诉我。

1个回答

4

最终找到了问题的根本原因。

session.php配置文件中的这行代码有关。

'domain' => '.'.config('app.domain')

此行代码从config.php文件中获取域名,而该文件又从.env文件中获取域名。

在Ubuntu和Homestead本地环境下,这个功能完美运行。

然而,在Red Hat上,这个功能根本无法正常工作。把这一行代码改为'domain' => '.'.env('APP_DOMAIN'),问题迎刃而解,TokenMissmatch消失了。


你必须在表单中使用csrf_token来防止错误。csrf_token可以为你提供额外的安全保障,以抵御各种攻击。 - Ajit Kumar Singh
我相信你没有完整地阅读问题。所发布的表单代码是一个“blade”模板,使用了在“Laravel 5”中被移除的HTML/Form生成器,这会在使用Form::open时自动生成_token。我也发布了答案。 - Matt Stephens
我个人使用laravel 5,并且之前也遇到过这个问题,所以我给你提供了解决方案。Laravel确实会生成csrf_token,但是你必须在表单中包含它,这样当你提交数据时,Laravel会检查csrf_token以确保它来自正确的来源,而不是通过其他来源进行操作。除此之外,我没有其他解决方案。 - Ajit Kumar Singh
我又回答了自己的问题。此外,使用表单生成器构建表单的方式会自动将其添加到页面中,因此无需手动添加。 - Matt Stephens
1
我同意你的看法,Matt。 - Efriandika Pratama

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接