Question

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

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上运行。我在网上尝试了很多解决方案，但对我来说没什么用。

Answer 1

在使用带有localhost作为域的cookie时，这看起来像是一个长期问题的变体。简而言之，你不能这样做，因为在许多浏览器中，域名需要2'。域名中的字符至少为。

没关系：

www.domain.com
.domain.com

这个问题已经在各个地方进行过讨论，尤其是对于set cookie的手册和评论中的php（Laravel对此感到满意），特别是关于“域”的部分：

Cookie可用的（子）域。将此设置为   子域（例如'www.example.com'）将使cookie可用   到该子域及其所有其他子域（即   w2.www.example.com）。使cookie可用于整个域   （包括它的所有子域），只需将值设置为域   name（'example.com'，在这种情况下）。

旧的浏览器仍然可以实现已弃用的»RFC 2109   要求领先。匹配所有子域。

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

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

另外，像这样的原因是我使用Vagrant / virtualbox / docker的原因。您可能会在Linux服务器上托管，所以为什么要在Windows / Mac OS上进行开发，使用一堆解决方法，以及WAMP / MAMP /无论是什么堵塞您的机器，您必须启动/停止所有的服务时间，更不用说安装/升级？

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

会话重置每个页面重新加载

1 个答案: