Php 每次重新加载页面时都会重置会话

我当时正在我的windows机器上开发一个laravel应用程序，项目在那里运行得很好。该项目与dropbox同步，当我迁移到mac时，我的laravel项目在macos上不起作用。
我面临的问题是，它会在每次重新加载页面时重新生成会话id。我使用数据库作为会话存储，它在数据库中添加了一个新条目
我曾尝试将文件驱动程序用作会话存储，但同样的情况是，它在存储/框架/会话中创建了一个新文件，证明文件权限正常且可写。
我所有的表格都停止工作，变得越来越糟糕

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,

];

---

在我看来，这似乎是将本地主机作为域使用cookie时长期存在的问题的一个变种。简而言之，您不能这样做，因为在许多浏览器中，域名至少需要2个“.”字符

这些都可以：

www.domain.com
.domain.com

这个问题已经在不同的地方讨论过，尤其是手册中的php（Laravel对php感激不尽），以及对“域”部分的评论：

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

旧浏览器仍在实现弃用的»RFC 2109 5
需要领导。以匹配所有子域

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

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

顺便说一句，我之所以使用Vagrant/virtualbox/docker就是因为这样的原因。您可能将被托管在linux服务器上，那么为什么要在Windows/Mac操作系统上开发，使用一系列解决方法，以及WAMP/MAMP/任何阻塞您机器的服务，您将不得不随时启动/停止，更不用说安装/升级了

最后但并非最不重要的一点是，虚拟化和它提供的网络选项允许您设置群集并测试高级多主机配置，如果您在工作站上尝试将这些配置配置为一系列相互连接的进程，那么这些配置充其量也会很混乱
 请提供有关配置的更多详细信息。我已添加更多详细信息。您的会话域在env文件中是什么？请检查：APP\u URL=SESSION\u DOMAIN=APP URL和会话域是相同的