首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >Laravel 5.1登录表格上的标记不匹配

Laravel 5.1登录表格上的标记不匹配
EN

Stack Overflow用户
提问于 2015-11-18 10:40:27
回答 1查看 1.7K关注 0票数 4

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

代码运行在Red Hat serverphp 5.6上,我也在运行php 5.5.9Ubuntu server上测试过它,它运行得非常好。它在当地也运行得很好。

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

我查过了

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

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

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

我正在为表单使用HTML生成器,这意味着_token正在被设置,所以它不需要手动发生。

表单代码

代码语言:javascript
复制
{!! 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() !!}

会话配置

代码语言:javascript
复制
<?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,

];

如果还有什么有用的话,请告诉我。

EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2015-11-18 12:13:40

终于找到了问题的真相。

这与session.php配置文件中的这一行有关。

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

这一行是从config.php文件获取域,而后者又从.env文件获取域。

Ubuntu和本地的家园,这也是Ubuntu,这是完美的工作。

然而,在红帽上,这一点都不起作用。改变这条线成为'domain' => '.'.env('APP_DOMAIN')和voilàall是正确的,与世界和TokenMissmatch已经消失。

票数 4
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/33777836

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档