I've been struggling with a perplexing issue for the past few days - I'm trying to utilize a WCF service to call another RESTful service.
However, as I trace through the process, it consistently fails to set the appropriate JSON content type on the message.
Below is an example of the call in the client code (within a WCF service that makes the call):
[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)]
[ServiceBehavior()]
public partial class MyRestServiceClient : System.ServiceModel.ClientBase<IMyRestService>, IMyRestService
{
[WebInvoke(Method = "POST", UriTemplate = "/MyService/ReferenceTypes.json", RequestFormat = WebMessageFormat.Json)]
public MyServiceLists GetReferenceTypes()
{
try
{
return base.Channel.GetReferenceTypes();
}
catch (Exception e)
{
throw e; //throws exception here - method not allowed
}
}
}
The issue lies in the fact that instead of setting the content type to application/json, it mistakenly sets it to application/xml. This was deduced from activity tracing data logged by the WCF service responsible for initiating the call.
For instance, here's a snippet of the "message sent" information from the Activity log:
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
...
**<Encoder>application/xml; charset=utf-8</Encoder>**
...
I've attempted using a `webHttpBinding` and even tried a custom binding with a custom web content type mapper specifically designed to enforce a JSON content type, but to no avail.
The client endpoint is directed towards a RESTful service (utilizing the Rest 40 template) on the same machine. Below is the relevant excerpt from the `web.config` file of the WCF service:
<?xml version="1.0"?>
<configuration>
...
It's worth noting that a console application I developed with similar functionality and configuration does work correctly and sets the correct content type.
Any assistance or guidance you can offer would be greatly appreciated.