ODATA services should support $format ($format=json and $format=atom) query string parameters.
As described here http://www.odata.org/documentation/uri-conventions#FormatSystemQueryOption .
Comments: Actually solution proposed by raghuramn does not work. I tried these variants: config.Formatters.XmlFormatter.AddQueryStringMapping("$format", "xml", "application/atom+xml"); config.Formatters.XmlFormatter.MediaTypeMappings.Add(new QueryStringMapping("$format", "xml", "application/atom+xml")); And both of them do not work. The only way that works for me I found in this post http://stackoverflow.com/questions/16455501/why-doesnt-my-odata-response-have-navigation-properties Post above has another reference to https://gist.github.com/raghuramn/5556691 by RaghuRam Nadiminti. RaghuRam Nadiminti advised to add custom handler into config.MessageHandlers that could override Accept header. So question, is advise about formatters actual?
As described here http://www.odata.org/documentation/uri-conventions#FormatSystemQueryOption .
Comments: Actually solution proposed by raghuramn does not work. I tried these variants: config.Formatters.XmlFormatter.AddQueryStringMapping("$format", "xml", "application/atom+xml"); config.Formatters.XmlFormatter.MediaTypeMappings.Add(new QueryStringMapping("$format", "xml", "application/atom+xml")); And both of them do not work. The only way that works for me I found in this post http://stackoverflow.com/questions/16455501/why-doesnt-my-odata-response-have-navigation-properties Post above has another reference to https://gist.github.com/raghuramn/5556691 by RaghuRam Nadiminti. RaghuRam Nadiminti advised to add custom handler into config.MessageHandlers that could override Accept header. So question, is advise about formatters actual?