Edit Question - KnowledgeHub

Title Body

I've posted before on this subject, but after a year of getting on with other things, I've managed to get into a pickle once again. I'll try and give a brief overview of the scenario and the current attempts to make things work: IIS web server hosting HTML, JS etc. on host: iis.mycompany.com (referred to as foo ) WCF RESTful web services hosted via a Windows Service on host: wcf.mycompany.com (referred to as bar ) The Javascript served from foo works by making RESTful ajax calls ( GET or POST depending on the action) to the WCF services on bar , obviously these are cross domain calls as they aren't on the same host. The Javascript uses the jQuery (1.7.2) framework to manipulate the DOM and perform ajax calls to bar , the expected content type for POSTS is JSON , and the response from GETS is expected to be JSON too (application/json). Bar has it's WCF services configured using TransportCredentialOnly as the security mode and the transport client credentail type is NTLM , so only authed users to contact the services. CORS Support has been added to bar's WCF services using an extension to WCF: http://blogs.msdn.com/b/carlosfigueira/archive/2012/05/15/implementing-cors-support-in-wcf.aspx We have added additional headers and modfied some that the post already contained based on numerous internet articles: property.Headers.Add("Access-Control-Allow-Headers", "Accept, Content-Type"); property.Headers.Add("Access-Control-Allow-Methods", "POST, GET, OPTIONS"); property.Headers.Add("Access-Control-Max-Age", "172800"); property.Headers.Add("Access-Control-Allow-Origin", "http://iis.mycompany.com")

Tags (comma-separated) Cancel