REST in WCF: Varying response content type based on HTTP Request Headers

re: REST in WCF: Varying response content type based on HTTP Request Headers

Kyle Beyer — Mon, 17 Nov 2008 08:06:27 GMT

Hi Dino - Thanks for sharing this. I really like Damian's approach as well.

One thing I noticed while starting to use it in conjunction with the WCF REST starter kit is that there also needs to be support for dynamic *request* serialization. So, I’ve extended your code a bit and merged it into the starter kit code to enable this.

You can download source here: http://daptivate.com/archive/2008/11/16/wcf-and-rest-an-approach-to-using-the-content-type-and-accept-http-headers-for-object-serialization.aspx

Any chance this capability can make it into the next version of the starter kit? :)

re: REST in WCF: Varying response content type based on HTTP Request Headers

DotNetInterop — Wed, 19 Nov 2008 09:19:21 GMT

Kyle! I like the way you are thinking. I like your suggestion - will get back to you on it.

re: REST in WCF: Varying response content type based on HTTP Request Headers

Mike O'Brien — Sat, 20 Jun 2009 06:47:46 GMT

The WCF REST Contrib library allows you to do this as well:

http://wcfrestcontrib.codeplex.com/

re: REST in WCF: Varying response content type based on HTTP Request Headers

The Farmer — Thu, 03 Dec 2009 00:09:51 GMT

Great idea but it somehow interferes with the WebProtocolException processing. When I plug this behavior in and the operation throws a WebProtocolException, instead of my error object being returned, I just get a generic "Request Error".

The SerializeReply method is not called on error so I can't explain how it could interfere with error processing.

Trying to change big brother's ways is never this easy ;).