This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Calling All Indigo Team Members and Experts!
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I have an advanced scenario that is producing an exception that I suspect is a simple configuration setting but I don't know what it is. I am posting this on my Longhorn Blog so please comment there. I have an Indigo service (actually one of a whole bunch) that has been working with IIS6/Windows XP and Nov CTP. Our dev team moved to the Dec CTP and we have verified that there are zero changes in our code or config andit works on XP/IIS 6.0. Meanwhile bonehead Sam has overwritten his "work" system with Dec Vista and IIS 7. Everything like VS2005 and WinFX is working but I am getting this exception from Indigo on running:
System.ServiceModel.ProtocolException
{"The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)."}
Do I need to change some setting in IIS 7.0 to get it work? It seems like a mismatch between text/html and application/soap+xml both using charset=utf-8. IIS7 is set to “utf-8“ for “Requests“, Response Headers and Responses under Globalization. We are using wsHttpBinding
Previous Topic
