【问题标题】:Session resets on every page reload每次页面重新加载时会话重置
【发布时间】:2018-01-23 01:20:54
【问题描述】:

我正在我的 Windows 机器上开发一个 laravel 应用程序,项目在那里运行良好。该项目已与 Dropbox 同步,当我移至 mac 时,我的 laravel 项目在 macos 上无法运行。
我面临的问题是它会在每个页面重新加载时重新生成会话 ID。我使用数据库作为会话存储,它在数据库中添加了一个新条目。
我尝试使用文件驱动程序作为会话存储,同样的事情发生在它在 storage/framework/session 中创建一个新文件,这证明文件权限是可以的并且可写的。
我所有的表格都停止工作并得到 ​​p>

TokenMismatchException in VerifyCsrfToken.php

存储文件夹和会话文件夹的权限为755

应用程序的每次重新加载都会在数据库中添加一个新条目,因为我正在使用数据库驱动程序来保存会话

下面是我的会话文件

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

    'expire_on_close' => false,

    /*
    |--------------------------------------------------------------------------
    | 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 Cache Store
    |--------------------------------------------------------------------------
    |
    | When using the "apc" or "memcached" session drivers, you may specify a
    | cache store that should be used for these sessions. This value must
    | correspond with one of the application's configured cache stores.
    |
    */

    'store' => null,

    /*
    |--------------------------------------------------------------------------
    | 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' => 'laravel_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' => env('SESSION_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' => env('SESSION_SECURE_COOKIE', false),

    /*
    |--------------------------------------------------------------------------
    | HTTP Access Only
    |--------------------------------------------------------------------------
    |
    | Setting this value to true will prevent JavaScript from accessing the
    | value of the cookie and the cookie will only be accessible through
    | the HTTP protocol. You are free to modify this option if needed.
    |
    */

    'http_only' => true,

];

正如我提到的,同一个项目在我的 Windows 机器上运行良好,但由于会话问题而无法在我的 macos 上运行。我在网上尝试了很多解决方案,但都没有对我有用。

【问题讨论】:

标签: php session laravel-5.3


【解决方案1】:

在我看来,当使用 localhost 作为域的 cookie 时,这似乎是一个长期问题的变体。简而言之,您不能这样做,因为在许多浏览器中,域名需要 2 个“.”。域名中的字符最少。

这些都可以:

www.domain.com
.domain.com

这个问题已经在很多地方讨论过,特别是手册中的 php(Laravel 受惠于)和 set cookie 的 cmets,尤其是关于“域”的部分:

cookie 可用的(子)域。将此设置为 子域(例如“www.example.com”)将使 cookie 可用 到该子域及其所有其他子域(即 w2.www.example.com)。使 cookie 可用于整个域 (包括它的所有子域),只需将值设置为域 名称(在本例中为“example.com”)。

旧版浏览器仍在实施已弃用的 » RFC 2109 可能 需要一个领先的。匹配所有子域。

解决此问题的一种简单方法是在 /etc/hosts 文件中为您选择的域添加一个别名。根据rfc2606 的说法,最好的选择是在 TLD 上使用 .test。

// /etc/hosts
127.0.0.1   localhost www.yourbogusdomain.test

顺便说一句,这样的原因是我使用 Vagrant/virtualbox/docker 的原因。您可能将托管在 linux 服务器上,那么为什么要在 Windows/Mac OS 上进行开发,使用一堆变通方法,以及 WAMP/MAMP/任何堵塞您的机器的服务,您必须启动/停止所有时间,更不用说安装/升级了?

最后但并非最不重要的一点是,虚拟化及其提供的网络选项允许您设置集群并测试高级多主机配置,这些配置充其量只是在您的工作站上尝试和配置为一系列互连的进程。

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 2016-06-26
    • 2019-11-07
    • 2018-07-04
    • 2014-04-18
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多