WCF service shows empty screen on browser


I have a test WCF service, when I try this on visual studio it works fine, when I paste the link http://localhost:1347/Service1.svc/DoWork in the browser it shows bad request with empty white screen of the browser

Failed to load resource: the server responded with a status of 400 (Bad Request)

When I tried with JSON it shows CORS issue, I added some script in Web.Config but still exist the problem of bad request, WCF has following operation contracts;

namespace WcfService1

    public interface IService1

        string DoWork();

        string GetData(int value);

        CompositeType GetDataUsingDataContract(CompositeType composite);

    public class CompositeType
        bool boolValue = true;
        string stringValue = "Hello ";

        public bool BoolValue
            get { return boolValue; }
            set { boolValue = value; }

        public string StringValue
            get { return stringValue; }
            set { stringValue = value; }

their implementation comes here.

public class Service1 : IService1

        public string DoWork()
            return string.Format("This is DoWork()");
        public string GetData(int value)
            return string.Format("You entered: {0}", value);

        public CompositeType GetDataUsingDataContract(CompositeType composite)
            if (composite == null)
                throw new ArgumentNullException("composite");
            if (composite.BoolValue)
                composite.StringValue += "Suffix";
            return composite;


<?xml version="1.0"?>

    <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true"/>
    <compilation debug="true" targetFramework="4.5.2"/>
    <httpRuntime targetFramework="4.5.2"/>
      <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web"/>
          <!-- To avoid disclosing metadata information, set the values below to false before deployment -->
          <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="false"/>
        <add binding="basicHttpsBinding" scheme="https"/>
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/>
    <modules runAllManagedModulesForAllRequests="true">
      <remove name="ApplicationInsightsWebTracking"/>
      <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web"

        <add name="Access-Control-Allow-Origin" value="*"/>
        <add name="Access-Control-Allow-Headers" value="Content-Type, Accept" />
        <add name="Access-Control-Allow-Methods" value="POST,GET,OPTIONS" />
        <add name="Access-Control-Max-Age" value="1728000" />

        To browse web app root directory during debugging, set the value below to true.
        Set to false before deployment to avoid disclosing web app folder information.
    <directoryBrowse enabled="true"/>
    <validation validateIntegratedModeConfiguration="false"/>



JSON call

            $.get("http://localhost:1347/Service1.svc/DoWork", function(data, status){

                alert("Data: " + data + "\nStatus: " + status);

Add following code in your global.asax file. This will allow preflight requests to complete successfully.

protected void Application_BeginRequest(object sender, EventArgs e)
   HttpContext.Current.Response.AddHeader("Access-Control-Allow-Origin", "*");
   if (HttpContext.Current.Request.HttpMethod == "OPTIONS")
    HttpContext.Current.Response.AddHeader("Access-Control-Allow-Methods", "GET, POST");
    HttpContext.Current.Response.AddHeader("Access-Control-Allow-Headers", "Content-Type, Accept");
    HttpContext.Current.Response.AddHeader("Access-Control-Max-Age", "1728000");
By : Leopard

The "bad request" responses would be due to the HTTP verb mismatch. SOAP requests for all operations with basicHttpBinding in WCF use HTTP POST, not HTTP GET. If you want to use HTTP GET, use webHttpBinding.

Or better still, use Web API instead of WCF.

This video can help you solving your question :)
By: admin