Php 登录表单POST上的Laravel 5.1令牌不匹配

我在compiled.php第2930行中遇到以下错误

TokenMismatchException:

代码运行在

redhat服务器上，使用
php5.6
我也在运行
php5.5.9
的
Ubuntu服务器上进行了测试，效果非常好。它在本地也运行得很好

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

我查过了


重定向
服务器上的日期/时区问题
session.php和
app.php中的配置问题


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

只要点击登录按钮，您就会点击
csrf
中间件，表示令牌不匹配

我正在为表单使用HTML生成器，这意味着正在设置
\u标记
，因此不需要手动执行

表格代码

{!! 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() !!}

{！！Form:：open（['action'=>'Auth'\AuthController@login']) !!}
登录
@包括（'共享。\错误'）
{！！Form:：label（'username'，'Employee username'）
{！！Form:：text（'username'）！！}
{！！Form:：label（'password'，'password'）！！}
{！！Form:：password（'password'）！！}
{！！表单：：提交（'Login'，['class'=>'按钮大']）
{！！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,

];

终于找到了问题的症结所在

这与
session.php
config文件中的这一行有关

'domain'=>'..config（'app.domain'）

此行从
config.php
文件获取域，该文件又从
.env
文件获取域

Ubuntu和本地的Homestead（也是Ubuntu）都是完美的

然而，在红帽上，这根本不起作用。将行更改为
'domain'=>'..env（'APP_domain'）
和voilía这一切都是正确的，标记匹配已经消失
 您必须在表单中使用csrf_令牌来防止错误。csrf_token为您提供了额外的安全保护，使您免受各种攻击。我相信您没有阅读整个问题。发布的表单代码是一个
blade
模板，使用的是从
Laravel 5
中删除的
HTML/form
生成的，当您使用
form:：open`时，这会自动生成
\u令牌。我也发布了答案。我个人使用了Laravel 5，并且之前也讨论过这个问题，这就是我给您提供解决方案的原因。Laravel当然会生成csrf_令牌，但您必须将其包含在表单中，以便在发布数据时，Laravel检查csrf_令牌以确保它来自正确的源，而不是通过其他源进行操作。除此之外，我没有其他的解决办法。我再次发布了我自己问题的答案。另外，使用表单生成器生成表单的方式会自动添加到页面中，因此无需手动添加。我同意你的看法