blocks|key|347679|text|在你提出了PHP的memory_limit，post_max_size和upload_max_filesize之后，我想向你推荐一些与这个主题相关的文章，也许其中一篇能解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|347680|我在服务器故障上找到了这篇文章：|347681|https://serverfault.com/questions/79741/php-apache-post-limit/79745#79745|347682|347683|sybreon建议仔细检查Content-Length，并-引用-“确保你直接连接到Apache，而不是通过代理或反向代理。一些反向代理设置了最大请求大小的上限，作为一种安全措施。所以，你可能想要检查一下你的Apache日志，以确保没有其他事情发生。”|unordered-list-item|BOLD|347684|sybreon还发布了这个链接：Apache+413+error+problems。|347685|347686|以下内容仅适用于在Apache中启用了++模块的。(否则此设置可能会导致服务器崩溃。)|347687|引用这篇文章：|347688|“我使用的是Apache+SSL客户端证书，它有128K的限制，如果必须进行重新协商，更大的POST将失败。|347689|提供了一些线索--您必须将以下内容设置为您的SSL服务器的默认值，而不仅仅是目录。|347690|SSLVerifyClient要求|347691|否则它会强制进行某种重新协商，并以413错误失败。“|347692|在上一篇文章中也提到了指令。|347693|347694|A+guy+says+here+that+the+appropriate+setting+of+this+directive+solved+his+problem..|347695|我希望这些设置之一能解决这个问题！|347696|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/manual/en/ini.core.php#ini.memory-limit|1|http://www.php.net/manual/en/ini.core.php#ini.post-max-size|2|http://www.php.net/manual/en/ini.core.php#ini.upload-max-filesize|3|4|http://blog.bombcar.com/2008/01/apache-413-error-problems.html|5|http://forum.joomla.org/viewtopic.php?p=2302244&sid=a654b905c1d75eb03aff1773a00c77ad#p2302244^0|9|C|M|D|10|J|9|C|0|M|D|1|10|J|2|0|0|0|21|3|0|0|0|7|D|E|0|G|P|4|0|0|L|3|0|0|0|0|0|0|0|0|0|2A|5|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@$9|1Y|A|1Z|1|20]|$9|21|A|22|1|23]|$9|24|A|25|1|26]]|E|$]]|$1|F|3|G|5|6|7|27|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|28|8|@]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|J|3|-4|5|6|7|2C|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|2D|8|@$9|2E|A|2F|B|N]|$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|O|3|P|5|M|7|2I|8|@]|D|@$9|2J|A|2K|1|2L]]|E|$]]|$1|Q|3|-4|5|6|7|2M|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|2N|8|@$9|2O|A|2P|B|N]]|D|@]|E|$]]|$1|T|3|U|5|6|7|2Q|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|2R|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2S|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2T|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2U|8|@]|D|@]|E|$]]|$1|13|3|14|5|M|7|2V|8|@]|D|@]|E|$]]|$1|15|3|-4|5|6|7|2W|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2X|8|@]|D|@$9|2Y|A|2Z|1|30]]|E|$]]|$1|18|3|19|5|6|7|31|8|@]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|32|8|@]|D|@]|E|$]]]|1B|$1C|$5|1D|1E|1F|E|$1G|1H]]|1I|$5|1D|1E|1F|E|$1G|1J]]|1K|$5|1D|1E|1F|E|$1G|1L]]|1M|$5|1D|1E|1F|E|$1G|I]]|1N|$5|1D|1E|1F|E|$1G|1O]]|1P|$5|1D|1E|1F|E|$1G|1Q]]]]

After you are over the raising of PHP's <a href="http://www.php.net/manual/en/ini.core.php#ini.memory-limit" rel="noreferrer" title="memory_limit"><code>memory_limit</code></a>, <a href="http://www.php.net/manual/en/ini.core.php#ini.post-max-size" rel="noreferrer" title="post_max_size"><code>post_max_size</code></a> and <a href="http://www.php.net/manual/en/ini.core.php#ini.upload-max-filesize" rel="noreferrer" title="upload_max_filesize"><code>upload_max_filesize</code></a>, I would like to recommend you some articles related to the topic, maybe one of them solves the problem.

I found this post on Server Fault: 
<a href="https://serverfault.com/questions/79741/php-apache-post-limit/79745#79745">https://serverfault.com/questions/79741/php-apache-post-limit/79745#79745</a>

<ul>
<li>sybreon suggests to double-check the <code>Content-Length</code>, and - citing - "ensure that you are directly connecting to Apache and not through either a proxy or a reverse-proxy. Some reverse-proxies place a cap on the maximum size of a request as a sort of security measure. So, you may want to check that as well as your Apache logs to ensure that nothing else is going on." </li>
<li>sybreon also posted this link: <a href="http://blog.bombcar.com/2008/01/apache-413-error-problems.html" rel="noreferrer" title="Apache 413 error problems">Apache 413 error problems</a>. 
The following is only applicable if you have <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslverifyclient" rel="noreferrer" title="Apache mod_ssl">mod_ssl</a> module turned on in Apache. (Otherwise this setting can cause a server crash.) 
Citing the article: 
"I was using Apache SSL client certificates, which have a limit of 128K, and if re-negotiation has to happen, a larger POST will fail. 
<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=12355" rel="noreferrer" title="Bug 12355 - POST incompatible w/ renegotiate https: connection">This Bugzilla posting</a> had the clues - You have to set the following as DEFAULTS for your SSL server, not just the directory. 

<pre><code>SSLVerifyClient require
</code></pre>

Otherwise it forces a renegotiation of some sort, and fails with a 413 error."</li>
<li>The previous article also mentioned the <a href="http://httpd.apache.org/docs/current/mod/core.html#limitrequestbody" rel="noreferrer" title="LimitRequestBody">LimitRequestBody</a> directive. 
<a href="http://forum.joomla.org/viewtopic.php?p=2302244&amp;sid=a654b905c1d75eb03aff1773a00c77ad#p2302244" rel="noreferrer" title="Request Entity Too Large Error - Solved">A guy says here that the appropriate setting of this directive solved his problem.</a>.</li>
</ul>

I hope one of these settings solves this problem!

blocks|key|231585|text|我唯一能做的就是调优SSL缓冲区的大小。您可以通过以下方式进行设置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|231586|<Directory+/my/blah/blah>
...
++#+Set+this+to+something+big...
++SSLRenegBufferSize+10486000
...
</Directory>|code-block|syntax|javascript|231587|然后，只需重新启动...and即可使更改生效。(位于：http://forum.joomla.org/viewtopic.php?p=2085574)|offset|length|231588|您还可以使用"Location+/“将该设置简单地应用于整个VirtualHost：|231589|<VirtualHost+*:443>
#+...
++++<Location+/>
++++++++SSLRenegBufferSize+101048600
++++</Location>
#+...
</VirtualHost>|231590|entityMap|0|LINK|mutability|MUTABLE|url|http://forum.joomla.org/viewtopic.php?p=2085574^0|0|0|R|1B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

The only thing that would work for me was to tune up the SSL Buffer Size. You can set this by...
<pre><code>&lt;Directory /my/blah/blah&gt;
...
 # Set this to something big...
 SSLRenegBufferSize 10486000
...
&lt;/Directory&gt;
</code></pre>
...and then just restart Apache for the change to take effect. (Found this at: <a href="http://forum.joomla.org/viewtopic.php?p=2085574" rel="nofollow noreferrer">http://forum.joomla.org/viewtopic.php?p=2085574</a>)
You can also use &quot;Location /&quot; to simply apply the setting to a whole VirtualHost:
<pre><code>&lt;VirtualHost *:443&gt;
# ...
 &lt;Location /&gt;
 SSLRenegBufferSize 101048600
 &lt;/Location&gt;
# ...
&lt;/VirtualHost&gt;
</code></pre>

blocks|key|4272571|text|我的服务器是Apache。它是mod_security模块，它阻止发布大约171KB的大数据。我在mod_security.conf中完成了以下配置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4272572|SecRequestBodyNoFilesLimit+10486000
SecRequestBodyInMemoryLimit+10486000|code-block|syntax|javascript|4272573|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

My server is Apache. It was mod_security module which was preventing post of large data approximately 171 KB.
I did below configurations in mod_security.conf

<pre><code>SecRequestBodyNoFilesLimit 10486000
SecRequestBodyInMemoryLimit 10486000
</code></pre>

blocks|key|348778|text|如果已经设置了PHP语言中的max_post_upload和max_file_upload，并且在Apache2.conf或LimitRequestBody的ModSec配置文件中设置了足够高的值|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348779|那么一个.htaccess文件可能会起作用。|348780|348781|转到包含上传php文件的目录(抛出错误的文件或页面)。|ordered-list-item|348782|348783|2.制作或编辑.htaccess|348784|3.编辑或创建一条包含LimitRequestBody+20971520的行。|348785|348786|保存.htaccess。设置权限。(+644和apache+owner)|348787|Possibly重启apache。|348788|348789|塔达。希望能修好。|348790|此设置仅设置此文件夹的限制-这是避免php和apache中的全局设置的一种方法，全局设置会使您受到大型数据包/负载DOS攻击。|348791|LimitRequestBody+0为您提供无限制的上传。|348792|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|18|8|@]|9|@]|A|$]]|$1|P|3|Q|5|G|7|19|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1C|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|Z|$]]

If max_post_upload and max_file_upload in PHP has been set,
and there is a setting in Apache2.conf or ModSec config files of LimitRequestBody set high enough 

then possibly a .htaccess file will work.

<ol>
<li>Go to the directory with the upload php file in it ( the file or page throwing the error.)</li>
</ol>

2 . Make or edit .htaccess

3 . Edit or create a line with 
 LimitRequestBody 20971520 in it.

<ol start="4">
<li>Save the .htaccess. Set permissions. ( 644 and apache owner)</li>
<li>Possibly restart apache.</li>
</ol>

Tada . Hopefully fixed. 

This setting sets that limit for this folder only - which is one way to avoid a global setting in php and apache which makes you open to large packet / load DOS attacks.

LimitRequestBody 0 gives you unlimited uploads.

blocks|key|348809|text|在过去一天左右的时间里，我一直在努力解决这个413个请求的实体太大的问题，因为我试图将非常大的(MB)图像上传到服务器上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348810|我的设置是apache+(227)代理请求到jboss+eap+(6.4.20)服务器以访问rest端点。|348811|有两件事对我很有效。|348812|348813|使SSLVerifyClient成为虚拟主机级别所必需的。这意味着所有资源都需要提供有效的客户端证书才能提供服务。这对我来说不是一个选择，因为除了/api之外的所有资源都不应该被相互认证保护。因此，当它工作时，这对我来说不是一个选项。|ordered-list-item|348814|I删除了所需的全局级SSLVerifyClient，并将其保留为“可选”。我仅在<Location+/api>...</Location>上启用了必需选项。诀窍是让SSL重新协商仅在达到某个阈值后发生-这将是我们希望的上传文件大小。|offset|length|style|CODE|348815|所以，最后我发现我必须在一个特定的LocationMatch上启用'SSLRenegBufferSize‘设置，如下所示：|348816|348817|<LocationMatch+%5E/api/v1/path/(.*)/to/(.*)/resource/endpoint$>|348818|SSLRenegBufferSize+5242880+#allow+upto+5MB+for+files+to+come+through++</LocationMatch>|348819|(.*)表示端点中的路径参数。希望这能有所帮助。|348820|entityMap^0|0|0|0|0|0|14|T|0|0|0|0|1P|0|0|2E|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|15|8|@$L|16|M|17|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|I|7|18|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@$L|1B|M|1C|N|O]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1D|8|@$L|1E|M|1F|N|O]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|Z|$]]

I was struggling with this 413 - Request entity too large problem for last day or so, as I was trying to upload farely large (in MBs) images to the server.

My setup is apache (227) proxying requests to jboss eap (6.4.20) server for accessing rest endpoints.

2 Things worked for me.

<ol>
<li>Make SSLVerifyClient required at the virtual host level. This means all the resources need a valid client cert presented to be served. This was not an option for me as all the resources except /api should NOT be mutual auth protected. So, while it worked, this was not an option for me.</li>
<li>I removed the global level SSLVerifyClient required and kept it 'optional'. I re enabled required option only on <code>&lt;Location /api&gt;...&lt;/Location&gt;</code>. Trick was to have the SSL renegotiation happen only after a certain threshold is reached - which would be our desired upload file size.</li>
<li>So, finally it turned out that I had to enable 'SSLRenegBufferSize' setting on a specific LocationMatch as follows:

<code>&lt;LocationMatch ^/api/v1/path/(.*)/to/(.*)/resource/endpoint$&gt; 
SSLRenegBufferSize 5242880 #allow upto 5MB for files to come through 
&lt;/LocationMatch&gt;</code></li>
</ol>

(.*) in the case above represents my path params in the endpoint. Hope this helps.

I get this message, 

<pre><code>Request Entity Too Large
The requested resource
/index.php
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. 
</code></pre>

I set

<pre><code>php_value post_max_size 50M
php_value upload_max_filesize 50M
</code></pre>

in <code>.htaccess</code> but not helped

How to overcome this? 

Thanks

Request Entity Too Large

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我得到了这样的信息，Request Entity Too LargeThe requested resource/index.phpdoes not allow request data with POST requests, or the amount of data provided in the request ...

问请求实体太大
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问请求实体太大EN