I'm trying to get CORS working for a new version of our SOAP web service (which runs under HTTPS and has username/password authentication) which can be connected to via JS.
At the moment I'm getting it working fine locally (not cross-domain) but soon as it is using a different domain I get the following from the WCF Traceviewer. (400 Bad Request in IIS7)
<ExceptionString>System.Xml.XmlException: The body of the message cannot be read because it is empty.</ExceptionString>
It seems it's not even getting to the part where my message inspector runs to add the appropriate CORS headers.
Has anyone experienced this before or managed to get CORS to work under a HTTPS SOAP service?
I'd appreciate any advice you can give.
Cheers, Jamie