re: WCF "Raw" programming model (Web) - receiving arbitrary data

eggshelly — Wed, 24 Sep 2008 03:45:08 GMT

Awesome article Carlos - it helped me almost solve my seeming insurmountable wcf file upload problem.

But of course, I have a problem:

I've implemented your code from above but I'm trying to use the browser as a client. I used YUI from a simple HTML page to submit a form containing a file upload control. When I upload any kind of file, the web service receives the request but when it saves the file, the end result is surrounded with meta-data:

-----------------------------1654974419512

Content-Disposition: form-data; name="upFile"; filename="amazon phone number.txt"

Content-Type: text/plain

[file content here - perfectly reproduced (if I remove the surrounding junk)]

-----------------------------1654974419512--

So there must be some difference between how the POST is coming across from YUI and how it's coming across from the HttpWebRequest class, but I can't figure out what that is. Any ideas?

My web config is set up like:

<system.serviceModel>

</behavior>

</endpointBehaviors>

</behaviors>

</webHttpBinding>

</bindings>

<endpoint address="ajax" behaviorConfiguration="TestBehavior"

binding="webHttpBinding" bindingConfiguration="fileUploadCapable"

contract="ITest" />

</service>

</services>

</system.serviceModel>

And my service has the following interface:

[OperationContract]

[WebInvoke(UriTemplate = "UploadFile?upFile={fileName}")]

void UploadFile(string fileName, Stream fileContents);

and implementation:

public void UploadFile(string fileName, Stream fileContents)

BlogSvc Preview Release 0.2

BlogSvc News — Mon, 22 Dec 2008 22:49:17 GMT

I've put a new release up on codeplex. This release includes an implementation of Atom…

re: WCF "Raw" programming model (Web) - receiving arbitrary data

jimblust — Wed, 05 Aug 2009 21:07:42 GMT

Carlos, this is a great example, and I have it working in a console app. I've managed to modify the example so that the service can be hosted in IIS, but my tests indicate that IIS always waits to receive the entire request before handing it off to WCF for processing. Do you know if there's any way to make IIS hand off the streaming request to the service as soon as the request starts coming in? I've also asked on the WCF msdn forum here:

http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/cfe625b2-1890-471b-a4bd-94373daedd39