Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 04, 2012 01:47 PM by boehmap
May 02, 2012 02:21 PM|LINK
I'm working on a WCF file uploader using WSHttpBinding. I am looking to upload files around 10 mb (not playing an exact game on that one, but won't be getting files much larger). Everything works pretty well up to about 5mb. after that, I start getting HTTP
My binding is set up as follows:
wsBinding.ReaderQuotas = System.Xml.XmlDictionaryReaderQuotas.Max;
wsBinding.MaxBufferPoolSize = 52428800;
wsBinding.MaxReceivedMessageSize = 13631488;
wsBinding.ReceiveTimeout = new TimeSpan(0, 3, 0);
My httpRuntime maxRequestLength is 20480kb in
My requests look like:
POST http://mywebsite/FileUploader.svc HTTP/1.1
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:fil="http://namespace">
<fil:File>(base 64 file data)</fil:File>
Anyone have any ideas?
Thanks in advance!
May 02, 2012 02:27 PM|LINK
check this link this may help you out
May 02, 2012 02:36 PM|LINK
Thanks for the help. The biggest problem I've found when trying to google stuff is that most of the answers require changing to WebHttpBinding, which is not my primary choice for making this work, although I'm starting to think it may be the only way.
Anyone else have any ideas?
May 04, 2012 06:16 AM|LINK
HTTP error 500 illustrates that the server encountered an unexpected condition which prevented it from fulfilling the request, you could enable WCF tracing on the server side to see the inner executed information, maybe you can find some indicates.
#Enable WCF tracing.
May 04, 2012 01:47 PM|LINK
Yup. WCF tracing helped. Turns out that the increase in size by the base-64 file transform pushed even 5mb files way over the limit. Peter gets the points.
Now.... For bonus points, what can I do to keep from performing that transform to keep bandwidth and buffer size low?