blocks|key|3439956|text|在本地，一切都能正常工作，但在生产服务器上就不行了。问题出在主机上的php.ini设置中，默认情况下，参数(变量)+"mbstring.func_overload+=+2“设置在那里。我把它移走了，然后一切都正常了。此参数适用于许多CMS使用的早期版本(PHP)。Laravel在授权期间给出了一个错误419，仅此而已，并在每次页面更新时创建一个新的会话。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3439957|entityMap^0|Y|7|1N|Q|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Locally everything worked, but not on the production server. The problem was in the php.ini settings on the hosting, by default the parameter (variable) "mbstring.func_overload = 2" was set there. I removed it and than all worked. This parameter is for previous versions (PHP) which is used by many CMS. And Laravel gave an error 419 during authorization and nothing more, and created a new session every time the page was updated.

blocks|key|5551773|text|在从5.1升级到laravel+5.4之后，我遇到了类似的问题，我发现我没有正确升级app/Http/Kernel.php。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5551774|\Illuminate\Session\Middleware\StartSession::class|code-block|syntax|javascript|5551775|在protected+$middleware数组中声明了两次|offset|length|style|CODE|5551776|protected+$middlewareGroups|5551777|将其从$middleware阵列中删除后，它开始正常工作|5551778|适用于所有路由的$middleware和适用于特定组的$middlewareGroups|5551779|entityMap^0|0|0|1|L|0|0|3|B|0|8|B|R|H|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|T|$]]

after the upgrade from 5.1 to laravel 5.4 I had a similar issue,
I found that I didn't upgraded app/Http/Kernel.php correctly.

<pre><code>\Illuminate\Session\Middleware\StartSession::class
</code></pre>

was declared twice in <code>protected $middleware</code> array
and in

<pre><code>protected $middlewareGroups
</code></pre>

after removing it from <code>$middleware</code> array
it started to work correctly

<code>$middleware</code> applied to all routes
and <code>$middlewareGroups</code> applied to specific groups

blocks|key|3439743|text|检查this+issue+-+Laravel+5.2.27中有一个变化，它会自动为你注册web中间件，所以如果你在你的路由中手动使用它(你必须在5.2中使用)，那么它就会崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3439744|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/laravel/framework/issues/13000^0|2|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check <a href="https://github.com/laravel/framework/issues/13000" rel="nofollow">this issue</a> - there's a change in Laravel 5.2.27 that automatically registers the web middleware for you, so if you manually use it in your routes (which you had to in 5.2) then it breaks.

blocks|key|424728|text|这似乎是PHP+%2B+MacOS的怪癖。在我们的索引文件中，它是<?php之前的一个空行。绝对荒谬的问题，在调试上浪费了几个小时。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|424729|entityMap^0|V|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This seems to be quirk of PHP + MacOS. It was a blank line before <code>&lt;?php</code> in our index file. Absolutely ridiculous issue with hours lost on debugging.

blocks|key|3439725|text|你检查过这个线程laravel+forum吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3439726|它要求检查app/config/app.php文件中的<?php标记之前是否有空行，如果有，请删除空行|style|CODE|3439727|entityMap|0|LINK|mutability|MUTABLE|url|http://laravel.io/forum/07-15-2015-new-session-is-created-on-each-request^0|8|D|0|0|R|5|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

have you checked this thread <a href="http://laravel.io/forum/07-15-2015-new-session-is-created-on-each-request" rel="nofollow">laravel forum</a>

its says to check if there is any blank line before the <code>&lt;?php</code> tag in the file
app/config/app.php , if any remove the blank line

blocks|key|5551705|text|我刚刚遇到了这个问题，它是由使用dump()引起的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5551706|这会将输出发送到浏览器(就像php标记之前的空格一样)，并导致我的会话中断。|5551707|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have just had this problem and it was caused by using dump().

This was sending output to the browser (just as whitespace before php tags would) and causing my session to break.

blocks|key|3439911|text|我的问题是我在生产站点的子域上进行了本地测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3439912|我本地的Laravel在dev.example.com+(映射到本地主机)，prod在example.com。Prod+cookies干扰了开发站点。|offset|length|style|CODE|3439913|解决方案:清除干扰cookies或将开发站点移出子域。|3439914|entityMap^0|0|C|F|17|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

My problem was that I was testing locally on the subdomain of the production site.

My local Laravel was at <code>dev.example.com</code> (mapped to localhost), and prod was at <code>example.com</code>. Prod cookies interfered with the development site.

Solution: clear interfering cookies OR move dev site away from subdomain.

blocks|key|2339536|text|正如其他人所提到的，当会话由于头部已经被发送到浏览器而无法启动时，这种情况经常发生(+session_start函数需要发送几个HTTP头)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2339537|这可能是由于任何文件中开始<?php标记前的空格或换行符造成的。|style|CODE|2339538|这可以通过启用PHP的output+buffering轻松地解决，而不是搜索罪魁祸首。在php.ini中查找output_buffering指令，并将其更改为|BOLD|2339539|output_buffering=4096|code-block|syntax|javascript|2339540|这是生产服务器的推荐值，而且可能已经在OP的本地环境中定义了，因此会话可以按预期在本地运行。|2339541|entityMap|0|LINK|mutability|MUTABLE|url|https://www.php.net/manual/en/function.session-start.php|1|https://www.php.net/manual/en/outcontrol.configuration.php#ini.output-buffering^0|17|D|0|0|D|5|0|18|7|1I|G|B|G|1|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|6|7|15|8|@$A|16|B|17|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|18|8|@$A|19|B|1A|F|J]|$A|1B|B|1C|F|G]]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|K|3|L|5|M|7|1G|8|@]|9|@]|C|$N|O]]|$1|P|3|Q|5|6|7|1H|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]|Z|$5|U|V|W|C|$X|10]]]]

As others have mentioned, this happens a lot when a session can't start because headers have already been sent to the browser (The <a href="https://www.php.net/manual/en/function.session-start.php" rel="nofollow noreferrer">session_start</a> function needs to send out several HTTP headers).
It can be due to a space or newline character before an opening <code>&lt;?php</code> tag in any file.
Instead of searching for the culprit, this can be easily solved by enabling PHP's <a href="https://www.php.net/manual/en/outcontrol.configuration.php#ini.output-buffering" rel="nofollow noreferrer">output buffering</a>.
Look for the <code>output_buffering</code> directive in your php.ini and change it to
<pre class="lang-php prettyprint-override"><code>output_buffering=4096
</code></pre>
This is the recommended value for production servers anyway and it may already be defined in OP's local env so the session works there as expected.

for some reason that I can't figure out my Laravel install has started created a new session file on every request! This renders the session useless and so I users can't stay logged in, csrf tokens don't match etc.

I'm using Laravel 5.2. It seems fine on my local environment but not on the live server

Does anyone have any clues on why this might have happened and how I can resolve it?

Thanks in advance

Laravel creates a new session on every request

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

出于某种原因，我不能确定我的Laravel安装已经开始为每个请求创建一个新的会话文件！这使得会话无用，因此I用户无法保持登录，csrf令牌不匹配等等。我正在使用Laravel 5.2。它在我的本地环境上看起来很好，但在实时服务器上就不行了有谁知道为什么会发生这种情况，以及我如何解决它？提前感谢

问Laravel为每个请求创建一个新会话
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Laravel为每个请求创建一个新会话EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Laravel为每个请求创建一个新会话
EN