blocks|key|2079430|text|我认为最好的方式是不涉及WebOperationContext|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2079431|[OperationContract]
[WebInvoke(Method+=+"POST",+UriTemplate+=+"EntryPoint",+BodyStyle+=+WebMessageBodyStyle.Bare)]
MyData+GetData(System.IO.Stream+pStream);|code-block|syntax|javascript|2079432|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Best way i think doesn't involve WebOperationContext

<pre><code>[OperationContract]
[WebInvoke(Method = "POST", UriTemplate = "EntryPoint", BodyStyle = WebMessageBodyStyle.Bare)]
MyData GetData(System.IO.Stream pStream);
</code></pre>

blocks|key|1660078|text|使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660079|OperationContext.Current.RequestContext.RequestMessage|1660080|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Use 

OperationContext.Current.RequestContext.RequestMessage

blocks|key|1660108|text|很抱歉回答得太晚了，但我想我应该添加与UriTemplate参数一起工作的内容来获取请求正文。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660109|[ServiceContract]
public+class+Service
{++++++++
++++[OperationContract]
++++[WebInvoke(UriTemplate+=+"{param0}/{param1}",+Method+=+"POST")]
++++public+Stream+TestPost(string+param0,+string+param1)
++++{

++++++++string+body+=+Encoding.UTF8.GetString(OperationContext.Current.RequestContext.RequestMessage.GetBody<byte[]>());

++++++++return+...;
++++}
}|code-block|syntax|javascript|1660110|从消息正文的原始字节中为body分配一个字符串。|offset|length|style|CODE|1660111|entityMap^0|0|0|C|4|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Sorry for the late answer but I thought I would add what works with UriTemplate parameters to get the request body.

<pre><code>[ServiceContract]
public class Service
{ 
 [OperationContract]
 [WebInvoke(UriTemplate = "{param0}/{param1}", Method = "POST")]
 public Stream TestPost(string param0, string param1)
 {

 string body = Encoding.UTF8.GetString(OperationContext.Current.RequestContext.RequestMessage.GetBody&lt;byte[]&gt;());

 return ...;
 }
}
</code></pre>

<code>body</code> is assigned a string from the raw bytes of the message body.

blocks|key|5607692|text|此代码返回正文文本。需要使用System、System.Text、System.Reflection、System.ServiceModel|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5607693|public+string+GetBody()
{
++var+requestMessage+=+OperationContext.Current.RequestContext.RequestMessage;
++var+messageDataProperty+=+requestMessage.GetType().GetProperty("MessageData",+(BindingFlags)0x1FFFFFF);
++var+messageData+=+messageDataProperty.GetValue(requestMessage);
++var+bufferProperty+=+messageData.GetType().GetProperty("Buffer");
++var+buffer+=+bufferProperty.GetValue(messageData)+as+ArraySegment<byte>?;
++var+body+=+Encoding.UTF8.GetString(buffer.Value.Array);
++return+body;
}|code-block|syntax|javascript|5607694|entityMap^0|E|6|L|B|X|H|1F|J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|L|$]]

This code return body text. Need using <code>System</code>, <code>System.Text</code>, <code>System.Reflection</code>, <code>System.ServiceModel</code>
<pre><code>public string GetBody()
{
 var requestMessage = OperationContext.Current.RequestContext.RequestMessage;
 var messageDataProperty = requestMessage.GetType().GetProperty(&quot;MessageData&quot;, (BindingFlags)0x1FFFFFF);
 var messageData = messageDataProperty.GetValue(requestMessage);
 var bufferProperty = messageData.GetType().GetProperty(&quot;Buffer&quot;);
 var buffer = bufferProperty.GetValue(messageData) as ArraySegment&lt;byte&gt;?;
 var body = Encoding.UTF8.GetString(buffer.Value.Array);
 return body;
}
</code></pre>

blocks|key|5607596|text|似乎因为WCF被设计为与传输协议无关，所以默认情况下，服务方法不提供对HTTP特定信息的访问。然而，我刚刚看到了一篇描述"ASP.Net兼容模式“的很好的文章，它基本上允许你指定你的服务确实打算通过HTTP公开。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5607597|http://blogs.msdn.com/b/wenlong/archive/2006/01/23/516041.aspx|offset|length|5607598|将aspNetCompatibilityEnabled配置添加到Web.config中，并将AspNetCompatibilityRequirements属性添加到所需的服务操作中，应该可以做到这一点。我自己也要试一试。|style|CODE|5607599|哇哇-Bin|5607600|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1Q|0|0|1|Q|W|A|1A|V|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|6|7|X|8|@$D|Y|E|Z|H|I]|$D|10|E|11|H|I]|$D|12|E|13|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|C]]]]

It seems that because WCF is designed to be transport protocol-agnostic, a service method doesn't provide access to HTTP-specific information by default. However, I just came across a nice article describing "ASP.Net Compatibility Mode" which essentially allows you to specify that your service is indeed intended to be exposed via HTTP.

<a href="http://blogs.msdn.com/b/wenlong/archive/2006/01/23/516041.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/wenlong/archive/2006/01/23/516041.aspx</a>

Adding the <code>aspNetCompatibilityEnabled</code> configuration to <code>Web.config</code>, combined with the <code>AspNetCompatibilityRequirements</code> attribute to the desired service operations, should do the trick. I'm about to try this myself.

Haw-Bin

blocks|key|5607629|text|上面的回答帮助我想出了这个解决方案。我正在接收带有名称/值对的json。{"p1":7514，"p2":3412，"p3":"joe+smith“...+}|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5607630|[OperationBehavior(Impersonation+=+ImpersonationOption.Allowed)]
++++[WebInvoke(Method+=+"POST",
++++++++BodyStyle+=+WebMessageBodyStyle.Bare,+
++++++++RequestFormat+=+WebMessageFormat.Json
++++++++)]

public+Stream+getJsonRequest()
++++{

++++++++//+Get+the+raw+json+POST+content.++.Net+has+this+in+XML+string..
++++++++string+JSONstring+=+OperationContext.Current.RequestContext.RequestMessage.ToString();

++++++++//+Parse+the+XML+string+into+a+XML+document
++++++++XmlDocument+doc+=+new+XmlDocument();
++++++++doc.LoadXml(JSONstring);

++++++++foreach+(XmlNode+node+in+doc.DocumentElement.ChildNodes)
++++++++{
++++++++++++++++node.Name+//+has+key
++++++++++++++++node.InnerText;++//+has+value|code-block|syntax|javascript|5607631|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The above answers helped me come up with this solution. I am receiving json with name/value pairs. {"p1":7514,"p2":3412, "p3":"joe smith" ... }

<pre><code>[OperationBehavior(Impersonation = ImpersonationOption.Allowed)]
 [WebInvoke(Method = "POST",
 BodyStyle = WebMessageBodyStyle.Bare, 
 RequestFormat = WebMessageFormat.Json
 )]

public Stream getJsonRequest()
 {

 // Get the raw json POST content. .Net has this in XML string..
 string JSONstring = OperationContext.Current.RequestContext.RequestMessage.ToString();

 // Parse the XML string into a XML document
 XmlDocument doc = new XmlDocument();
 doc.LoadXml(JSONstring);

 foreach (XmlNode node in doc.DocumentElement.ChildNodes)
 {
 node.Name // has key
 node.InnerText; // has value
</code></pre>

blocks|key|1660148|text|我能够通过在这个帖子上拼凑出多个答案来解决我的问题。我尝试做的是在帖子的主体中接收一个JSON有效负载，并且不对它做任何操作，这样我就可以按自己的意愿解析它。这对我们来说很重要，因为JSON的到来不是一个单一的预先确定的事情，而是几种可能的事情之一。是的，我们可以为每个新事物添加一个单独的调用，但我们正在尝试允许系统在不更改代码的情况下具有可扩展性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660149|在以前的尝试中，我只能在内容类型是'text/plain‘的情况下才能让它工作，但后来我坐在那里反复解释为什么当有人想要调用它时，它不能作为'application/json’发送。|1660150|所以..。从这页上的答案..。签名如下：|1660151|[OperationContract]
[WebInvoke(Method+=+"POST",+UriTemplate+=+"test/",+RequestFormat+=+WebMessageFormat.Json,+ResponseFormat+=+WebMessageFormat.Json,+BodyStyle+=+WebMessageBodyStyle.Bare)]
void+TestCall();|code-block|syntax|javascript|1660152|然后像这样从主体中获取JSON：|1660153|private+string+GetJSONFromBody()
{
++++string+json+=+"";
++++string+contentType+=+WebOperationContext.Current.IncomingRequest.ContentType;
++++if+(contentType.Contains("application/json"))
++++{
++++++++var+requestMessage+=+OperationContext.Current.RequestContext.RequestMessage;
++++++++var+messageDataProperty+=+requestMessage.GetType().GetProperty("MessageData",+(BindingFlags)0x1FFFFFF);
++++++++var+messageData+=+messageDataProperty.GetValue(requestMessage);
++++++++var+bufferProperty+=+messageData.GetType().GetProperty("Buffer");
++++++++var+buffer+=+bufferProperty.GetValue(messageData)+as+ArraySegment<byte>?;
++++++++json+=+Encoding.UTF8.GetString(buffer.Value.Array);
++++}
++++else+if+(contentType.Contains("text"))
++++{
++++++++json+=+Encoding.UTF8.GetString(OperationContext.Current.RequestContext.RequestMessage.GetBody<byte[]>());
++++}

++++return+json;
}|1660154|通过这种方式，虽然有人尝试发送JSON，但最终我还是能够支持'application/json‘。我仍然需要支持‘文本/纯文本’，因为已经有应用程序以这种方式调用。|1660155|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I was able to solve my issue cobbling together multiple answers on this thread. What I am trying to do is to receive a JSON payload in the body of the POST and not have anything done to it so that I can parse it as I will. This is important to us because the JSON coming in is not a single predetermined thing, but rather one of several possible. Yes, we could add a separate call for each new thing, but we are trying to allow the system to be extensible without code changes.
In previous attempts I have only been able to get this to work if the content type was 'text/plain', but then I'm sitting chewing on my tongue explaining why it can't be sent as 'application/json' when someone wants to call it.
So... from the answers on this page... the following signature:
<pre><code>[OperationContract]
[WebInvoke(Method = &quot;POST&quot;, UriTemplate = &quot;test/&quot;, RequestFormat = WebMessageFormat.Json, ResponseFormat = WebMessageFormat.Json, BodyStyle = WebMessageBodyStyle.Bare)]
void TestCall();
</code></pre>
and then getting the JSON from the body like so:
<pre><code>private string GetJSONFromBody()
{
 string json = &quot;&quot;;
 string contentType = WebOperationContext.Current.IncomingRequest.ContentType;
 if (contentType.Contains(&quot;application/json&quot;))
 {
 var requestMessage = OperationContext.Current.RequestContext.RequestMessage;
 var messageDataProperty = requestMessage.GetType().GetProperty(&quot;MessageData&quot;, (BindingFlags)0x1FFFFFF);
 var messageData = messageDataProperty.GetValue(requestMessage);
 var bufferProperty = messageData.GetType().GetProperty(&quot;Buffer&quot;);
 var buffer = bufferProperty.GetValue(messageData) as ArraySegment&lt;byte&gt;?;
 json = Encoding.UTF8.GetString(buffer.Value.Array);
 }
 else if (contentType.Contains(&quot;text&quot;))
 {
 json = Encoding.UTF8.GetString(OperationContext.Current.RequestContext.RequestMessage.GetBody&lt;byte[]&gt;());
 }

 return json;
}
</code></pre>
This way however someone tries to send the JSON it will work, but at last I was able to support 'application/json'. I still needed to support 'text/plain' since there are already apps calling that way.

blocks|key|5607517|text|我为之前的回答道歉，我愚蠢地认为我只是为了在OperationContext上使用WebOperationContext，不幸的是，真正的答案要丑陋得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5607518|让我开始吧，一定有更好的方法！|5607519|首先，我创建了自己的context对象，可以附加到现有的OperationContext对象上。|5607520|public+class+TMRequestContext+:+IExtension<OperationContext>++{

++++private+OperationContext+_Owner;

++++++++public+void+Attach(OperationContext+owner)+{
++++++++++++_Owner+=+owner;
++++++++}

+++++public+void+Detach(OperationContext+owner)+{
++++++++++++_Owner+=+null;
++++++++}

++++public+static+TMRequestContext+Current+{
++++++++++++get+{
++++++++++++++++if+(OperationContext.Current+!=+null)+{
++++++++++++++++++++return+OperationContext.Current.Extensions.Find<TMRequestContext>();
++++++++++++++++}+else+{
++++++++++++++++++++return+null;
++++++++++++++++}
++++++++++++}
++++++++}
}|code-block|syntax|javascript|5607521|为了能够访问这个新的上下文对象，您需要将其添加为当前上下文对象的扩展。我通过创建一个消息检查器类来做到这一点。|5607522|public+class+TMMessageInspector+:+IDispatchMessageInspector+{

++++++++public+object+AfterReceiveRequest(ref+Message+request,+IClientChannel+channel,+InstanceContext+instanceContext)+{

++++++++++++OperationContext.Current.Extensions.Add(new+TMRequestContext());
++++++++++++return+null;
++++++++}
}|5607523|为了让消息检查器工作，你需要创建一个新的“行为”。我使用下面的代码实现了这一点。|5607524|++++public+class+TMServerBehavior+:+IServiceBehavior+{

++++++++public+void+AddBindingParameters(ServiceDescription+serviceDescription,+System.ServiceModel.ServiceHostBase+serviceHostBase,+System.Collections.ObjectModel.Collection<ServiceEndpoint>+endpoints,+System.ServiceModel.Channels.BindingParameterCollection+bindingParameters)+{
++++++++++++//Do+nothing
++++++++}

++++++++public+void+ApplyDispatchBehavior(ServiceDescription+serviceDescription,+System.ServiceModel.ServiceHostBase+serviceHostBase)+{

++++++++++++foreach+(ChannelDispatcher+chDisp+in+serviceHostBase.ChannelDispatchers)+{

++++++++++++++++foreach+(EndpointDispatcher+epDisp+in+chDisp.Endpoints)+{
++++++++++++++++++++epDisp.DispatchRuntime.MessageInspectors.Add(new+TMMessageInspector());
++++++++++++++++}
++++++++++++}

++++++++}
}|5607525|您应该能够在配置文件中添加行为，尽管我是通过创建新主机并在OnOpening方法中手动添加behaviour对象来实现的。我最终使用这些类的目的不仅仅是访问OperationContext对象。我使用它们来记录和覆盖错误处理以及对http请求对象的访问等。因此，它并不像看起来那么可笑。差不多了，但不完全是！|5607526|我真的不记得为什么我不能直接访问OperationContext.Current。我隐约记得它总是空的，这个讨厌的进程是我获得一个实际包含有效数据的实例的唯一方法。|5607527|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

My apologies for the previous answer, I stupidly assumed that I had just cast WebOperationContext to get at the OperationContext, unfortunately the real answer is much more ugly.

Let me preface this with, there must be a better way!

First I created my own context object, that could be attached to the existing OperationContext object.

<pre><code>public class TMRequestContext : IExtension&lt;OperationContext&gt; {

 private OperationContext _Owner;

 public void Attach(OperationContext owner) {
 _Owner = owner;
 }

 public void Detach(OperationContext owner) {
 _Owner = null;
 }

 public static TMRequestContext Current {
 get {
 if (OperationContext.Current != null) {
 return OperationContext.Current.Extensions.Find&lt;TMRequestContext&gt;();
 } else {
 return null;
 }
 }
 }
}
</code></pre>

In order to be able to access this new context object, you need to add it as an extension to the current one. I did that by creating a message inspector class.

<pre><code>public class TMMessageInspector : IDispatchMessageInspector {

 public object AfterReceiveRequest(ref Message request, IClientChannel channel, InstanceContext instanceContext) {

 OperationContext.Current.Extensions.Add(new TMRequestContext());
 return null;
 }
}
</code></pre>

In order for the message inspector to work you need to create a new "behaviour". I did this using the following code. 

<pre><code> public class TMServerBehavior : IServiceBehavior {

 public void AddBindingParameters(ServiceDescription serviceDescription, System.ServiceModel.ServiceHostBase serviceHostBase, System.Collections.ObjectModel.Collection&lt;ServiceEndpoint&gt; endpoints, System.ServiceModel.Channels.BindingParameterCollection bindingParameters) {
 //Do nothing
 }

 public void ApplyDispatchBehavior(ServiceDescription serviceDescription, System.ServiceModel.ServiceHostBase serviceHostBase) {

 foreach (ChannelDispatcher chDisp in serviceHostBase.ChannelDispatchers) {

 foreach (EndpointDispatcher epDisp in chDisp.Endpoints) {
 epDisp.DispatchRuntime.MessageInspectors.Add(new TMMessageInspector());
 }
 }

 }
}
</code></pre>

The behaviour you should be able to add in the config file, although I did it by creating a new host and adding the behaviour object manually in the OnOpening method. I ended up using these class for much more than just accessing the OperationContext object. I used them for logging and overriding the error handling and access to the http request object,etc. So, it is not quite as ridiculous solution as it seems. Almost, but not quite!

I really don't remember why I could not just access OperationContext.Current directly. I have a faint recollection that it was always empty and this nasty process was the only way I could get an instance that actually contained valid data.

blocks|key|5607678|text|下面是我所做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5607679|using+System.IO;
using+System.ServiceModel;
using+System.ServiceModel.Web;
using+System;
using+System.IO;
using+System.ServiceModel;
using+System.ServiceModel.Activation;
using+System.ServiceModel.Web;
using+System.Text;

namespace+YourSpaceName
{
++++[AspNetCompatibilityRequirements(RequirementsMode+=+AspNetCompatibilityRequirementsMode.Required)]
++++public+class+YourClassName
++++{
++++++++[OperationContract]
++++++++[WebInvoke(Method+=+"POST",+UriTemplate+=+"YourMethodName({id})",+BodyStyle+=+WebMessageBodyStyle.Bare)]
++++++++public+Stream+YourMethodName(Stream+input,+string+id)
++++++++{
++++++++++++WebOperationContext+ctx+=+WebOperationContext.Current;
++++++++++++ctx.OutgoingResponse.Headers.Add("Content-Type",+"application/json");

++++++++++++string+response+=+$@"{{""status"":+""failure"",+""message"":+""Please+specify+the+Id+of+the+vehicle+requisition+to+retrieve."",+""d"":null}}";
++++++++++++try
++++++++++++{
++++++++++++++++string+response+=+(new+StreamReader(input)).ReadToEnd();
++++++++++++}
++++++++++++catch+(Exception+ecp)
++++++++++++{
++++++++++++++++response+=+$@"{{""status"":+""failure"",+""message"":+""{ecp.Message}"",+""d"":null}}";
++++++++++++}

++++++++++++return+new+MemoryStream(Encoding.UTF8.GetBytes(response));
++++++++}
++++}
}|code-block|syntax|javascript|5607680|这段代码只是读取输入并将其写出。POST请求的主体被自动分配给input，而不考虑变量名。正如您所看到的，您的UriTemplate中仍然可以包含变量。|5607681|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Here is what I did:

<pre><code>using System.IO;
using System.ServiceModel;
using System.ServiceModel.Web;
using System;
using System.IO;
using System.ServiceModel;
using System.ServiceModel.Activation;
using System.ServiceModel.Web;
using System.Text;

namespace YourSpaceName
{
 [AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)]
 public class YourClassName
 {
 [OperationContract]
 [WebInvoke(Method = "POST", UriTemplate = "YourMethodName({id})", BodyStyle = WebMessageBodyStyle.Bare)]
 public Stream YourMethodName(Stream input, string id)
 {
 WebOperationContext ctx = WebOperationContext.Current;
 ctx.OutgoingResponse.Headers.Add("Content-Type", "application/json");

 string response = $@"{{""status"": ""failure"", ""message"": ""Please specify the Id of the vehicle requisition to retrieve."", ""d"":null}}";
 try
 {
 string response = (new StreamReader(input)).ReadToEnd();
 }
 catch (Exception ecp)
 {
 response = $@"{{""status"": ""failure"", ""message"": ""{ecp.Message}"", ""d"":null}}";
 }

 return new MemoryStream(Encoding.UTF8.GetBytes(response));
 }
 }
}
</code></pre>

This code simply reads the input and writes it out.
the body of the POST request is automatically assigned to input irrespect of the variable name. As you can see, you can still have variables in your your UriTemplate.

How do I access the HTTP POST request body in a WCF REST service?

Here is the service definition:

<pre><code>[ServiceContract]
public interface ITestService
{
 [OperationContract]
 [WebInvoke(Method = "POST", UriTemplate = "EntryPoint")]
 MyData GetData();
}
</code></pre>

Here is the implementation:

<pre><code>public MyData GetData()
{
 return new MyData();
}
</code></pre>

I though of using the following code to access the HTTP request:

<pre><code>IncomingWebRequestContext context = WebOperationContext.Current.IncomingRequest;
</code></pre>

But the IncomingWebRequestContext only gives access to the headers, not the body.

Thanks.

Access Request Body in a WCF RESTful Service

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何访问WCF REST服务中的HTTP POST请求正文？以下是服务定义：[ServiceContract]public interface ITestService{    [OperationContract]    [WebInvoke(Method = "POST", UriTemplate = "EntryPoint")]    MyData GetData();}具体实现如下：pub

问访问RESTful服务中的请求正文
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问访问RESTful服务中的请求正文EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问访问RESTful服务中的请求正文
EN