Sticky problem with a few WCF REST services on a production machine. All the services are fine across other servers, failing any interactions on one particular server with a 400 Error.
Dropped a "Really simple rest" service onto the same server, call in the same way and works fine - so don't think it's a server issue.
Checked IIS config for things like wildcard maps etc - all seems to be the same as other servers.
Written a quick Powershell script to call - this also fails with a 400, so we think our JS side of things is OK.
Checked request format etc (JSON) in Fiddler - seems to be fine and the same as works on other servers.
Tried to create a new instance of our complete app on the same server - same problem, so it looks like it's something specific to our server side code in this app only, except the server side code is the same as the really simple service above - with one exception - we use code to create our binding object and endpoint rather than having them in web.config. The settings we use are however the same as per the standard info added when adding the normal service reference.
We're about running out of ideas on this one, so any pointers as to areas to look at would be greatly appreciated.
C# has already designed away most of the tedium of C++.
Last Visit: 31-Dec-99 18:00 Last Update: 31-May-16 4:43