blocks|key|597421|text|这不是IIS的问题，而是WCF的问题。WCF默认将消息大小限制为65KB，以避免大消息的拒绝服务攻击。另外，如果您不使用MTOM，它会将byte[]发送到base64编码的字符串(大小增加33%25)+=>+48KB+*+1,33+=+64KB|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597422|要解决此问题，您必须重新配置您的服务以接受更大的消息。此问题之前触发了400错误请求错误，但在更新的版本中，WCF开始使用413，这是此类错误的正确状态代码。|597423|您需要在绑定中设置maxReceivedMessageSize。您可能还需要设置readerQuotas。|offset|length|style|CODE|597424|<system.serviceModel>
++<bindings>
++++<basicHttpBinding>
++++++<binding+maxReceivedMessageSize="10485760">
++++++++<readerQuotas+...+/>
++++++</binding>
++++</basicHttpBinding>
++</bindings>++
</system.serviceModel>|code-block|syntax|javascript|597425|entityMap^0|0|0|9|M|14|C|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@$F|T|G|U|H|I]|$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|X|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

That is not problem of IIS but the problem of WCF. WCF by default limits messages to 65KB to avoid denial of service attack with large messages. Also if you don't use MTOM it sends byte[] to base64 encoded string (33% increase in size) => 48KB * 1,33 = 64KB

To solve this issue you must reconfigure your service to accept larger messages. This issue previously fired 400 Bad Request error but in newer version WCF started to use 413 which is correct status code for this type of error.

You need to set <code>maxReceivedMessageSize</code> in your binding. You can also need to set <code>readerQuotas</code>.

<pre><code>&lt;system.serviceModel&gt;
 &lt;bindings&gt;
 &lt;basicHttpBinding&gt;
 &lt;binding maxReceivedMessageSize="10485760"&gt;
 &lt;readerQuotas ... /&gt;
 &lt;/binding&gt;
 &lt;/basicHttpBinding&gt;
 &lt;/bindings&gt; 
&lt;/system.serviceModel&gt;
</code></pre>

blocks|key|597472|text|我在使用WCF+REST服务的IIS+7.5时也遇到了同样的问题。试图通过POST上传超过65k的任何文件，它将返回错误413“请求实体太大”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597473|您需要了解的第一件事是在web.config中配置了哪种绑定。这里有一篇很棒的文章。|597474|BasicHttpBinding+vs+WsHttpBinding+vs+WebHttpBinding|offset|length|597475|如果你有一个REST服务，那么你需要将它配置为"webHttpBinding“。修复方法如下：|597476|<system.serviceModel>

<bindings>
+++<webHttpBinding>
++++<binding+
++++++maxBufferPoolSize="2147483647"+
++++++maxReceivedMessageSize="2147483647"+
++++++maxBufferSize="2147483647"+transferMode="Streamed">
++++</binding>++
+++</webHttpBinding>
</bindings>|code-block|syntax|javascript|597477|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2650785/basichttpbinding-vs-wshttpbinding-vs-webhttpbinding^0|0|0|0|1F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

I was having the same issue with IIS 7.5 with a WCF REST Service. Trying to upload via POST any file above 65k and it would return Error 413 "Request Entity too large".

The first thing you need to understand is what kind of binding you've configured in the web.config. Here's a great article...

<a href="https://stackoverflow.com/questions/2650785/basichttpbinding-vs-wshttpbinding-vs-webhttpbinding">BasicHttpBinding vs WsHttpBinding vs WebHttpBinding</a>

If you have a REST service then you need to configure it as "webHttpBinding". Here's the fix:

<pre><code>&lt;system.serviceModel&gt;

&lt;bindings&gt;
 &lt;webHttpBinding&gt;
 &lt;binding 
 maxBufferPoolSize="2147483647" 
 maxReceivedMessageSize="2147483647" 
 maxBufferSize="2147483647" transferMode="Streamed"&gt;
 &lt;/binding&gt; 
 &lt;/webHttpBinding&gt;
&lt;/bindings&gt;
</code></pre>

blocks|key|381595|text|这帮助我解决了这个问题(为了可读性/可复制性，用一行分隔)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|381596|C:\Windows\System32\inetsrv\appcmd++set+config+"YOUR_WEBSITE_NAME"+
+++++-section:system.webServer/serverRuntime+/uploadReadAheadSize:"2147483647"+
+++++/commit:apphost|code-block|syntax|javascript|381597|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|$]]

This helped me to resolve the problem (one line - split for readability / copy-ability):

<pre><code>C:\Windows\System32\inetsrv\appcmd set config "YOUR_WEBSITE_NAME" 
 -section:system.webServer/serverRuntime /uploadReadAheadSize:"2147483647" 
 /commit:apphost
</code></pre>

blocks|key|597566|text|对于任何正在寻找IIS错误413+:+Request+entity+to+large并在Sharepoint中使用WCF服务的人来说，这是给你的信息。如果使用MultipleBaseAddressBasicHttpBindingServiceHostFactory.，则应用程序主机中的设置和其他站点/帖子中建议的web.config在SharePoint中不起作用您可以使用SP+Powershell来获取SPWebService.Content服务，创建一个新的SPWcvSettings对象，并如上所述地更新您的服务的设置(这些设置将不存在)。请记住在创建和添加设置时仅使用服务的名称(例如yourservice.svc)。有关更多信息，请参阅此网站https://robertsep.wordpress.com/2010/12/21/set-maximum-upload-filesize-sharepoint-wcf-service|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|597567|entityMap|0|LINK|mutability|MUTABLE|url|https://robertsep.wordpress.com/2010/12/21/set-maximum-upload-filesize-sharepoint-wcf-service^0|94|2L|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]]]]

For anyone else ever looking for an IIS WCF error 413 : Request entity to large and using a WCF service in Sharepoint, this is the information for you. The settings in the application host and web.config suggested in other sites/posts don't work in SharePoint if using the MultipleBaseAddressBasicHttpBindingServiceHostFactory. You can use SP Powershell to get the SPWebService.Content service, create a new SPWcvSettings object and update the settings as above for your service (they won't exist). Remember to just use the name of the service (e.g. [yourservice.svc]) when creating and adding the settings. See this site for more info <a href="https://robertsep.wordpress.com/2010/12/21/set-maximum-upload-filesize-sharepoint-wcf-service" rel="nofollow">https://robertsep.wordpress.com/2010/12/21/set-maximum-upload-filesize-sharepoint-wcf-service</a>

blocks|key|597610|text|在我的例子中，我必须增加BizTalk中接收位置的“最大接收消息大小”。它的默认值也是64K，因此无论我在web.config中配置了什么，BizTAlk都会将每封邮件退回|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597611|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case I had to increase the "Maximum received message size" of the Receive Location in BizTalk. That also has a default value of 64K and so every message was bounced by BizTAlk regardless of what I configured in my web.config

blocks|key|597666|text|我已经能够通过在同一个wcf通道/客户端上的请求之前执行一个虚拟调用(例如，IsAlive返回true+)来解决这个问题。显然，ssl协商是在第一次调用时完成的。所以不需要增加Uploadreadaheadsize。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597667|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've been able to solve this by executing a dummy call ( e.g. IsAlive returning true ) just before the request with large content on the same wcf channel/client. Apparently ssl negotation is done on the first call. So no need to increase Uploadreadaheadsize.

blocks|key|597739|text|对我来说，在增加了对uploadReadAheadSize绑定的限制后，将int.MaxValue设置为WCF也解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|597740|看起来，在使用SSL时，整个请求实体主体都是预加载的，为此使用了此元数据库属性。|597741|有关详细信息，请参阅：|597742|The+page+was+not+displayed+because+the+request+entity+is+too+large.+iis7|597743|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/22762311/the-page-was-not-displayed-because-the-request-entity-is-too-large-iis7^0|A|J|0|0|0|0|20|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|L|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

For me, setting the <code>uploadReadAheadSize</code> to int.MaxValue also fixed the problem, after also increasing the limits on the WCF binding.

It seems that, when using SSL, the entire request entity body is preloaded, for which this metabase property is used.

For more info, see:

<a href="https://stackoverflow.com/questions/22762311/the-page-was-not-displayed-because-the-request-entity-is-too-large-iis7">The page was not displayed because the request entity is too large. iis7</a>

blocks|key|597788|text|对于问题，远程服务器返回了意外的响应：(413)带有Resful的WCF上的请求实体太大|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597789|请查看我的解释配置|597790|</client>
<serviceHostingEnvironment+multipleSiteBindingsEnabled="false"+aspNetCompatibilityEnabled="true"/>

<bindings>

+++
++<webHttpBinding>
++++<binding+name="RestfullwebHttpBinding"
++++++maxBufferPoolSize="2147483647"
++++++maxReceivedMessageSize="2147483647"
++++++maxBufferSize="2147483647"+transferMode="Streamed">

++++++<readerQuotas+
++++++++maxDepth="2147483647"+
++++++++maxStringContentLength="2147483647"
++++++++maxArrayLength="2147483647"+
++++++++maxBytesPerRead="2147483647"+/>+

++++</binding>
++</webHttpBinding>
++

+++
++<wsHttpBinding>
++++<binding+name="wsBinding1"+maxReceivedMessageSize="2147483647"+closeTimeout="00:10:00"+openTimeout="00:10:00"+receiveTimeout="00:10:00"+sendTimeout="00:10:00"+bypassProxyOnLocal="false"+transactionFlow="false"+hostNameComparisonMode="StrongWildcard"+maxBufferPoolSize="2147483647"+messageEncoding="Text"+textEncoding="utf-8"+useDefaultWebProxy="true"+allowCookies="false">
++++++<readerQuotas+maxDepth="2147483647"+maxStringContentLength="2147483647"+maxArrayLength="2147483647"+maxBytesPerRead="2147483647"+maxNameTableCharCount="2147483647"/>
++++++<reliableSession+ordered="true"+inactivityTimeout="00:10:00"+enabled="false"/>
++++++
++++++<security+mode="TransportWithMessageCredential">
++++++++<message+clientCredentialType="UserName"+establishSecurityContext="true"/>
++++++</security>
++++</binding>
++</wsHttpBinding>
+++

+++
++<basicHttpBinding>
++++<binding+name="basicBinding1"+maxReceivedMessageSize="2147483647"+closeTimeout="00:10:00"+openTimeout="00:10:00"+receiveTimeout="00:10:00"+sendTimeout="00:10:00"+bypassProxyOnLocal="false"+hostNameComparisonMode="StrongWildcard"+maxBufferPoolSize="2147483647"+messageEncoding="Text"+textEncoding="utf-8"+useDefaultWebProxy="true"+allowCookies="false"+transferMode="Streamed">
++++++<readerQuotas+maxDepth="2147483647"+maxStringContentLength="2147483647"+maxArrayLength="2147483647"+maxBytesPerRead="2147483647"+maxNameTableCharCount="2147483647"/>
++++++<security+mode="None"/>
++++</binding>
++</basicHttpBinding>
</bindings>+


<services>
++<clear/>

++<service+name="ING.IWCFService.CitisecHashTransfer"++>
++++<endpoint+address="http://localhost:8099/CitisecHashTransfer.svc"
++++++++++++++++++behaviorConfiguration="RestfullEndpointBehavior"
++++++++++++++++++binding="webHttpBinding"
++++++++++++++++++bindingConfiguration="RestfullwebHttpBinding"
++++++++++++++++++name="ICitisecHashTransferBasicHttpBinding"
++++++++++++++++++contract="ING.IWCFService.ICitisecHashTransfer"+/>
++</service>

</services>
<behaviors>
++<serviceBehaviors>
++++<behavior+name="ServiceBehavior">
++++++<serviceMetadata+httpsGetEnabled="true"/>
++++++<serviceDebug+includeExceptionDetailInFaults="true"/>
++++++<dataContractSerializer+maxItemsInObjectGraph="2147483647"/>

++++++<serviceCredentials>
++++++++<userNameAuthentication+userNamePasswordValidationMode="Custom"+customUserNamePasswordValidatorType="ING.IWCFService.IWCFServiceValidator,+ING.IWCFService"/>
++++++</serviceCredentials>
++++++<serviceSecurityAudit+auditLogLocation="Application"+serviceAuthorizationAuditLevel="SuccessOrFailure"+messageAuthenticationAuditLevel="SuccessOrFailure"/>
++++++<serviceThrottling+maxConcurrentCalls="1000"+maxConcurrentSessions="100"+maxConcurrentInstances="1000"/>

++++</behavior>
++++<behavior>
++++++<serviceMetadata+httpGetEnabled="true"+httpsGetEnabled="true"/>
++++++<serviceDebug+includeExceptionDetailInFaults="true"/>
++++++<dataContractSerializer+maxItemsInObjectGraph="2147483647"/>
++++</behavior>
++</serviceBehaviors>
++<endpointBehaviors>
++++<behavior+name="EndpointBehavior">
++++++<dataContractSerializer+maxItemsInObjectGraph="2147483647"+/>
++++</behavior>+
++++<behavior+name="RestfullEndpointBehavior">
++++++<dataContractSerializer+maxItemsInObjectGraph="2147483647"++/>
++++++<webHttp/>
++++</behavior>+
++</endpointBehaviors>
</behaviors>|code-block|syntax|javascript|597791|​|597792|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

for issue the remote server returned an unexpected response: (413) Request Entity Too Large on WCF with Resful

please see my explain configuration


 

<pre><code>&lt;/client&gt;
&lt;serviceHostingEnvironment multipleSiteBindingsEnabled="false" aspNetCompatibilityEnabled="true"/&gt;

&lt;bindings&gt;

 &lt;!-- this for restfull service --&gt;
 &lt;webHttpBinding&gt;
 &lt;binding name="RestfullwebHttpBinding"
 maxBufferPoolSize="2147483647"
 maxReceivedMessageSize="2147483647"
 maxBufferSize="2147483647" transferMode="Streamed"&gt;

 &lt;readerQuotas 
 maxDepth="2147483647" 
 maxStringContentLength="2147483647"
 maxArrayLength="2147483647" 
 maxBytesPerRead="2147483647" /&gt; 

 &lt;/binding&gt;
 &lt;/webHttpBinding&gt;
 &lt;!-- end --&gt;

 &lt;!-- this for Soap v.2 --&gt;
 &lt;wsHttpBinding&gt;
 &lt;binding name="wsBinding1" maxReceivedMessageSize="2147483647" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"&gt;
 &lt;readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/&gt;
 &lt;reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false"/&gt;
 &lt;!--UsernameToken over Transport Security--&gt;
 &lt;security mode="TransportWithMessageCredential"&gt;
 &lt;message clientCredentialType="UserName" establishSecurityContext="true"/&gt;
 &lt;/security&gt;
 &lt;/binding&gt;
 &lt;/wsHttpBinding&gt;
 &lt;!-- this for restfull service --&gt;

 &lt;!-- this for Soap v.1 --&gt;
 &lt;basicHttpBinding&gt;
 &lt;binding name="basicBinding1" maxReceivedMessageSize="2147483647" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false" transferMode="Streamed"&gt;
 &lt;readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/&gt;
 &lt;security mode="None"/&gt;
 &lt;/binding&gt;
 &lt;/basicHttpBinding&gt;
&lt;/bindings&gt; 
&lt;!-- end --&gt;

&lt;services&gt;
 &lt;clear/&gt;

 &lt;service name="ING.IWCFService.CitisecHashTransfer" &gt;
 &lt;endpoint address="http://localhost:8099/CitisecHashTransfer.svc"
 behaviorConfiguration="RestfullEndpointBehavior"
 binding="webHttpBinding"
 bindingConfiguration="RestfullwebHttpBinding"
 name="ICitisecHashTransferBasicHttpBinding"
 contract="ING.IWCFService.ICitisecHashTransfer" /&gt;
 &lt;/service&gt;

&lt;/services&gt;
&lt;behaviors&gt;
 &lt;serviceBehaviors&gt;
 &lt;behavior name="ServiceBehavior"&gt;
 &lt;serviceMetadata httpsGetEnabled="true"/&gt;
 &lt;serviceDebug includeExceptionDetailInFaults="true"/&gt;
 &lt;dataContractSerializer maxItemsInObjectGraph="2147483647"/&gt;

 &lt;serviceCredentials&gt;
 &lt;userNameAuthentication userNamePasswordValidationMode="Custom" customUserNamePasswordValidatorType="ING.IWCFService.IWCFServiceValidator, ING.IWCFService"/&gt;
 &lt;/serviceCredentials&gt;
 &lt;serviceSecurityAudit auditLogLocation="Application" serviceAuthorizationAuditLevel="SuccessOrFailure" messageAuthenticationAuditLevel="SuccessOrFailure"/&gt;
 &lt;serviceThrottling maxConcurrentCalls="1000" maxConcurrentSessions="100" maxConcurrentInstances="1000"/&gt;

 &lt;/behavior&gt;
 &lt;behavior&gt;
 &lt;serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/&gt;
 &lt;serviceDebug includeExceptionDetailInFaults="true"/&gt;
 &lt;dataContractSerializer maxItemsInObjectGraph="2147483647"/&gt;
 &lt;/behavior&gt;
 &lt;/serviceBehaviors&gt;
 &lt;endpointBehaviors&gt;
 &lt;behavior name="EndpointBehavior"&gt;
 &lt;dataContractSerializer maxItemsInObjectGraph="2147483647" /&gt;
 &lt;/behavior&gt; 
 &lt;behavior name="RestfullEndpointBehavior"&gt;
 &lt;dataContractSerializer maxItemsInObjectGraph="2147483647" /&gt;
 &lt;webHttp/&gt;
 &lt;/behavior&gt; 
 &lt;/endpointBehaviors&gt;
&lt;/behaviors&gt;
</code></pre>

blocks|key|597852|text|在我的例子中，我收到了这个错误消息，因为我更改了服务的名称空间，并且服务标签指向了较旧的名称空间。我刷新了名称空间，错误消失了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|597853|<services>
++<service+name="My.Namespace.ServiceName">+
++++<endpoint+address=""+
++++++++++++++binding="wsHttpBinding"+
++++++++++++++bindingConfiguration="MyBindingConfiguratioName"+
++++++++++++++contract="My.Namespace.Interface"+
++++/>
++</service>
</services>|code-block|syntax|javascript|597854|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|$]]

In my case, I was getting this error message because I was changed the service's namespace and services tag was pointed to the older namespace. I refreshed the namespace and the error disapear:

<pre><code>&lt;services&gt;
 &lt;service name="My.Namespace.ServiceName"&gt; &lt;!-- Updated name --&gt;
 &lt;endpoint address="" 
 binding="wsHttpBinding" 
 bindingConfiguration="MyBindingConfiguratioName" 
 contract="My.Namespace.Interface" &lt;!-- Updated contract --&gt;
 /&gt;
 &lt;/service&gt;
&lt;/services&gt;
</code></pre>

blocks|key|381952|text|在我添加了这个之后，我的问题就解决了：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|381953|++<system.webServer>
++++++++<security>
++++++++++++<requestFiltering>
++++++++++++++++<requestLimits
++++++++++++++++++++maxAllowedContentLength="104857600"
++++++++++++++++/>
++++++++++++</requestFiltering>
++++++++</security>
++</system.webServer>|code-block|syntax|javascript|381954|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 problem has gone after I added this:
<pre><code> &lt;system.webServer&gt;
 &lt;security&gt;
 &lt;requestFiltering&gt;
 &lt;requestLimits
 maxAllowedContentLength=&quot;104857600&quot;
 /&gt;
 &lt;/requestFiltering&gt;
 &lt;/security&gt;
 &lt;/system.webServer&gt;
</code></pre>

blocks|key|382003|text|将许多回复粘合在一起将是我需要的所有信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|382004|IIS配置:+C:\Windows\System32\inetsrv\config\applicationHost.config+(最底层)|382005|<?xml+version="1.0"+encoding="UTF-8"?>
<configuration>
...
<location+path="Default+Web+Site">
++++++++<system.webServer>
++++++++++++<security>
++++++++++++++++<access+sslFlags="SslNegotiateCert"+/>
++++++++++++++++
++++++++++++++++<requestFiltering>
+++++++++++++++++++++<requestLimits+maxAllowedContentLength="104857600"+/>
++++++++++++++++</requestFiltering>
++++++++++++</security>
++++++++</system.webServer>
++++</location>
</configuration>|code-block|syntax|javascript|382006|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Glued a lot of responses together will ALL info I needed:
IIS Config: C:\Windows\System32\inetsrv\config\applicationHost.config (very bottom)
<pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;configuration&gt;
...
&lt;location path=&quot;Default Web Site&quot;&gt;
 &lt;system.webServer&gt;
 &lt;security&gt;
 &lt;access sslFlags=&quot;SslNegotiateCert&quot; /&gt;
 &lt;!-- Max upload size in bytes --&gt;
 &lt;requestFiltering&gt;
 &lt;requestLimits maxAllowedContentLength=&quot;104857600&quot; /&gt;
 &lt;/requestFiltering&gt;
 &lt;/security&gt;
 &lt;/system.webServer&gt;
 &lt;/location&gt;
&lt;/configuration&gt;
</code></pre>

I've written a WCF service with .NET 4.0, which is hosted on my Windows 7 <code>x64</code> Ultimate system with IIS 7.5.
One of the service methods has an 'object' as argument and I'm trying to send a byte[] which contains a picture.
As long as the file size of this picture is less then approx. 48KB, all goes well. But if I'm trying to upload a larger picture, the WCF service returns an error: <code>(413) Request Entity Too Large.</code>
So ofcourse I've spent 3 hours Googling the error message and every topic I've seen about this subject suggests raising the 'uploadReadAheadSize' property.
So what I've done is using the following commands (10485760 = 10MB):

<code>"appcmd.exe set config -section:system.webserver/serverruntime/uploadreadaheadsize: 10485760 /commit:apphost"</code>

<code>"cscript adsutil.vbs set w3svc/&lt;APP_ID&gt;/uploadreadaheadsize 10485760"</code>

I've also used IIS Manager to set the value by opening the site and going to "Configuration Editor" under Management.
Unfortunately I'm still getting the Request Entity Too Large error and it's getting really frustrating!

So does anybody know what else I can try to fix this error?

(413) Request Entity Too Large | uploadReadAheadSize

数据库

服务器

Windows

我用IIS4.0编写了一个.NET服务，它托管在我的Windows7 x64旗舰版系统和IIS7.5上。其中一个服务方法有一个'object‘作为参数，我试图发送一个包含图片的byte[]。只要这张图片的文件大小小于大约。48KB，一切顺利。但是如果我试图上传更大的图片，WCF服务会返回一个错误：(413) Reque...

问(413)请求实体太大| uploadReadAheadSize
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问(413)请求实体太大| uploadReadAheadSizeEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问(413)请求实体太大| uploadReadAheadSize
EN