413 Request Entity Too Large uploadReadAheadSize

Question

I ve written a WCF service with  NET 4 0  which is hosted on my Windows 7 x64 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   413  Request Entity Too Large  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     appcmd exe set config -section system webserver serverruntime uploadreadaheadsize  10485760  commit apphost    cscript adsutil vbs set w3svc  lt APP ID gt  uploadreadaheadsize 10485760   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

User · Answer

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    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

User · Answer

Got a similar error on IIS Express with Visual Studio 2017       HTTP Error 413 0 - Request Entity Too Large      The page was not displayed because the request entity is too large       Most likely causes          The Web server is refusing to service the request because the request   entity is too large    The Web server cannot service the request because it is trying to   negotiate a client certificate but the request entity is too large    The request URL or the physical mapping to the URL  i e   the physical   file system path to the URL s content  is too long          Things you can try          Verify that the request is valid    If using client certificates  try          Increasing system webServer serverRuntime uploadReadAheadSize   Configure your SSL endpoint to negotiate client certificates as part   of the initial SSL handshake   netsh http add sslcert       clientcertnegotiation enable   vs config applicationhost config         Solve this by editing   vs config applicationhost config  Switch serverRuntime from Deny to Allow like this    lt section name  serverRuntime  overrideModeDefault  Allow    gt    If this value is not edited  you will get an error like this when setting uploadReadAheadSize      HTTP Error 500 19 - Internal Server Error       The requested page cannot be accessed because the related   configuration data for the page is invalid       This configuration section cannot be used at this path  This happens   when the section is locked at a parent level  Locking is either by   default  overrideModeDefault  Deny    or set explicitly by a location   tag with overrideMode  Deny  or the legacy allowOverride  false     Then edit Web config with the following values     lt system webServer gt     lt serverRuntime uploadReadAheadSize  10485760    gt

User · Answer

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

User · Answer

For me  setting the uploadReadAheadSize 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   The page was not displayed because the request entity is too large  iis7

User · Answer

for issue the remote server returned an unexpected response   413  Request Entity Too Large on WCF with Resful  please see my explain configuration          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

User · Answer

I was receiving this error message  even though I had the max settings set within the binding of my WCF service config file   lt basicHttpBinding gt           lt binding name  quot NewBinding1 quot                   receiveTimeout  quot 01 00 00 quot                   sendTimeout  quot 01 00 00 quot                   maxBufferSize  quot 2000000000 quot                   maxReceivedMessageSize  quot 2000000000 quot  gt                     lt readerQuotas maxDepth  quot 2000000000 quot                        maxStringContentLength  quot 2000000000 quot                        maxArrayLength  quot 2000000000 quot                         maxBytesPerRead  quot 2000000000 quot                         maxNameTableCharCount  quot 2000000000 quot    gt           lt  binding gt   lt  basicHttpBinding gt   It seemed as though these binding settings weren t being applied  thus the following error message   IIS7 -  413  Request Entity Too Large when connecting to the service   The Problem I realised that the name  quot  quot  attribute within the  lt service gt  tag of the web config is not a free text field  as I thought it was   It is the fully qualified name of an implementation of a service contract as mentioned within this documentation page  If that doesn t match  then the binding settings won t be applied   lt services gt     lt  -- The namespace appears in the  name  attribute -- gt     lt service name  quot Your Namespace ConcreteClassName quot  gt       lt endpoint address  quot http   localhost YourService svc quot        binding  quot basicHttpBinding quot  bindingConfiguration  quot NewBinding1 quot        contract  quot Your Namespace IConcreteClassName quot    gt     lt  service gt   lt  services gt   I hope that saves someone some pain

User · Answer

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     BasicHttpBinding vs WsHttpBinding vs WebHttpBinding  If you have a REST service then you need to configure it as  webHttpBinding   Here s the fix    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

User · Answer

This helped me to resolve the problem  one line - split for readability   copy-ability    C  Windows System32 inetsrv appcmd  set config  YOUR WEBSITE NAME        -section system webServer serverRuntime  uploadReadAheadSize  2147483647         commit apphost

User · Answer

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 maxReceivedMessageSize in your binding  You can also need to set readerQuotas    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

User · Answer

If you re running into this issue despite trying all of the solutions in this thread  and you re connecting to the service via SSL  e g  https   this might help   http   forums newatlanta com messages cfm threadid 554611A2-E03F-43DB-92F996F4B6222BC0 amp  top  To summarize  in case the link dies in the future   if your requests are large enough the certificate negotiation between the client and the service will fail randomly  To keep this from happening  you ll need to enable a certain setting on your SSL bindings  From your IIS server  here are the steps you ll need to take    Via cmd or powershell  run netsh http show sslcert  This will give you your current configuration  You ll want to save this somehow so you can reference it again later  You should notice that  Negotiate Client Certificate  is disabled  This is the problem setting  the following steps will demonstrate how to enable it  Unfortunately there is no way to change existing bindings  you ll have to delete it and re-add it  Run netsh http delete sslcert  lt ipaddress gt   lt port gt  where  lt ipaddress gt   lt port gt  is the IP port shown in the configuration you saved earlier  Now you can re-add the binding  You can view the valid parameters for netsh http add sslcert here  MSDN  but in most cases your command will look like this    netsh http add sslcert ipport  lt ipaddress gt   lt port gt  appid  lt application ID from saved config including the    gt  certhash  lt certificate hash from saved config gt  certstorename  lt certificate store name from saved config gt  clientcertnegotiation enable  If you have multiple SSL bindings  you ll repeat the process for each of them  Hopefully this helps save someone else the hours and hours of headache this issue caused me   EDIT  In my experience  you can t actually run the netsh http add sslcert command from the command line directly  You ll need to enter the netsh prompt first by typing netsh and then issue your command like http add sslcert ipport     in order for it to work

User · Answer

My problem has gone after I added this     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

User · Answer

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 https   robertsep wordpress com 2010 12 21 set-maximum-upload-filesize-sharepoint-wcf-service

User · Answer

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

User · Answer

I had the same problem and setting the uploadReadAheadSize solved it   http   www iis net configreference system webserver serverruntime   The value must be between 0 and 2147483647    It is easily set it in the applicationHost config-fle if you don t want to do a cmd-thing   Its located in WindowsFOLDER System32 inetsrv config  2008 server    You must open it with notepad  Do a Backup of the file first   According to the comments in config the recommended way to unlock sections is by using a location tag    lt location path  Default Web Site  overrideMode  Allow  gt       lt system webServer gt           lt asp   gt       lt  system webServer gt   lt  location gt     So you can write in the bottom  since it doesn t exist before   I write maxvalue here - write your own value if you want    lt location path  THENAMEOFTHESITEYOUHAVE  overrideMode  Allow  gt       lt system webServer gt           lt asp   gt           lt serverRuntime uploadReadAheadSize  2147483647    gt       lt  system webServer gt   lt  location gt    If you put it last before  lt  configuration gt  for example  you know where you have it   Hope that solves your problems  It was an SSL overhead issue for me  where too much post freezed the application  raising a  413  Request Entity Too Large error

[wcf] (413) Request Entity Too Large | uploadReadAheadSize

Examples related to wcf

Examples related to iis