Note that there are some explanatory texts on larger screens.

plurals
  1. POThis operation is not supported in the wcf test client because it uses type system.io.stream
    text
    copied!<p>When I run my sample WCF application I get the following error in WCF Test Client window</p> <pre><code>This operation is not supported in the wcf test client because it uses type system.io.stream </code></pre> <p>I have ping method that uses Stream in my service implementation.</p> <pre><code> public string Ping(Stream input) { var streamReader = new StreamReader(input); string streamString = streamReader.ReadToEnd(); streamReader.Close(); NameValueCollection nvc = HttpUtility.ParseQueryString(streamString); return string.IsNullOrEmpty(nvc["message"]) ? "The 'message' key value pair was not received." : nvc["message"]; } </code></pre> <p>in my web.config file I added </p> <pre><code>&lt;basicHttpBinding&gt; &lt;binding name="HttpStreaming" maxReceivedMessageSize="67108864" transferMode="Streamed" &gt; &lt;/binding&gt; &lt;/basicHttpBinding&gt; </code></pre> <p>To allow streaming. now when I run the application I get the above error. I googled and researched quite a bit. I used fiddler to track down the error and it was http error 415 which is confirming the above error coming from WCF Test Client. </p> <p><strong>Update:</strong> Here is my service contract</p> <pre><code>[ServiceContract] public interface IService1 { [OperationContract] [WebInvoke(UriTemplate = "ping")] string Ping(Stream input); } </code></pre> <p>Curl command I used </p> <pre><code>curl -x 127.0.0.1:8888 http://localhost:8000/Service1.svc/ping -d message=pong </code></pre> <p>Notice -x 127.0.0.1:8888 is for fiddler to capture the traffic </p> <p>Here is fiddler result</p> <pre><code># Result Protocol Host URL Body Caching Content-Type Process Comments Custom 1 415 HTTP localhost:8000 /Service1.svc/ping 0 private curl:7440 </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload