Answered by:
HTTP/1.1 413 Request Entity Too Large

Question
-
Hi Team,
I have exposed my schema as a Service using the WCF Publishinf wizard the binding I have used is WCF Basic HTTP.
Since we are Testing one of our solution with a large file(100 MB) I have increased my Time Out Values and the MaxReceive message zize to 1048576 on my Receive Location.
From the client also I have Updated by binding value to
maxBufferPoolSize
="2147483647"maxBufferSize="2147483647"maxReceivedMessageSize="2147483647"
in the app config file
but still at the client I get the Error saying the Request Entity is too large.
Can you Please help me with this?
Thanks,
sujith.
Friday, October 21, 2016 10:40 AM
Answers
-
Hi Sujith,
Refer the article: https://blogs.msdn.microsoft.com/dsnotes/2015/08/21/large-file-upload-failure-for-web-application-calling-wcf-service-413-request-entity-too-large/
You should consider configuring WCF verbose level tracing for the service and client. For more information on configuring WCF tracing please see the link – https://msdn.microsoft.com/en-us/library/ms733025%28v=vs.110%29.aspx
You can refer an old thread: Cannot consume WCF service. (413) Request Entity Too Large
Check the IIS request Filtering and set the Maximum allowed content length to higher value. Also there is a setting present in the IIS – “UploadReadAheadSize” that prevents upload and download of data greater than 49KB.The value present by default is 49152 bytes and can be increased up to 4 GB.
Try removing named binding configuration and use the default one.Another that what is mentioned in the article you should also consider setting httpRuntime Element- maxRequestLength with appropriate value in your web.config.
Refer discussion here.
Rachit Sikroria (Microsoft Azure MVP)
- Edited by Rachit SikroriaModerator Friday, October 21, 2016 5:50 PM
- Proposed as answer by Rachit SikroriaModerator Saturday, October 29, 2016 12:41 AM
- Marked as answer by Rachit SikroriaModerator Saturday, October 29, 2016 12:42 AM
Friday, October 21, 2016 10:43 AMModerator
All replies
-
Hi Sujith,
Refer the article: https://blogs.msdn.microsoft.com/dsnotes/2015/08/21/large-file-upload-failure-for-web-application-calling-wcf-service-413-request-entity-too-large/
You should consider configuring WCF verbose level tracing for the service and client. For more information on configuring WCF tracing please see the link – https://msdn.microsoft.com/en-us/library/ms733025%28v=vs.110%29.aspx
You can refer an old thread: Cannot consume WCF service. (413) Request Entity Too Large
Check the IIS request Filtering and set the Maximum allowed content length to higher value. Also there is a setting present in the IIS – “UploadReadAheadSize” that prevents upload and download of data greater than 49KB.The value present by default is 49152 bytes and can be increased up to 4 GB.
Try removing named binding configuration and use the default one.Another that what is mentioned in the article you should also consider setting httpRuntime Element- maxRequestLength with appropriate value in your web.config.
Refer discussion here.
Rachit Sikroria (Microsoft Azure MVP)
- Edited by Rachit SikroriaModerator Friday, October 21, 2016 5:50 PM
- Proposed as answer by Rachit SikroriaModerator Saturday, October 29, 2016 12:41 AM
- Marked as answer by Rachit SikroriaModerator Saturday, October 29, 2016 12:42 AM
Friday, October 21, 2016 10:43 AMModerator -
Hi Sujith,
Refer below thread for sample
BizTalk Orchestration published WCF service returning response: (413) Request Entity Too Large
Also refer to the Large file upload failure for Web application calling WCF service – 413 Request entity too large
Mandar Dharmadhikari
Friday, October 21, 2016 10:58 AMModerator -
Friday, October 21, 2016 12:00 PMModerator