Reading custom Content-Type (f.e. StackOverflow) feeds using HttpClient from WebAPI

Question

I like a lot how the HttpClient is architectured - but I can't figure out how to add a "not quite standard" media type to be handled by the XmlSerializer.

This code:

var cli = new HttpClient();
cli
    .GetAsync("http://stackoverflow.com/feeds/tag?tagnames=delphi&sort=newest")
    .ContinueWith(task =>
    {
        task.Result.Content.ReadAsAsync<Feed>();
    });

works fine when pointed to atom feeds that have Content-Type of "text/xml", but the one in the example fails with the "No 'MediaTypeFormatter' is available to read an object of type 'Feed' with the media type 'application/atom+xml'" message. I tried different combinations of specifying MediaRangeMappings for the XmlMediaTypeFormatter (to be passed as an argument to ReadAsAsync) but with no success.

What is the "recommended" way to configure the HttpClient to map "application/atom+xml" and "application/rss+xml" to XmlSerializer?

score 4 · Accepted Answer · answered Feb 26 '12 at 20:24

Here is the code that works (credits to ASP.net forum thread):

public class AtomFormatter : XmlMediaTypeFormatter
{
    public AtomFormatter()
    {
        SupportedMediaTypes.Add(new MediaTypeHeaderValue("application/atom+xml"));
    }

    protected override bool CanReadType(Type type)
    {
        return base.CanReadType(type) || type == typeof(Feed);
    }
}

var cli = new HttpClient();
cli
    .GetAsync("http://stackoverflow.com/feeds/tag?tagnames=delphi&sort=newest")
    .ContinueWith(task =>
    {
        task.Result.Content.ReadAsAsync<Feed>(new[] { new AtomFormatter });
    });

Still, would like to see a solution without subclassing XmlMediaTypeFormatter - anybody?

score 0 · Answer 2 · answered Feb 26 '12 at 13:38

0

The problem is that you are trying to convert the result straight to Feed. As error is clearly saying, it cannot figure our how to convert the application/atom+xml into Feed.

You would have to perhaps return as XML and then use and XmlReader to initialise your Feed.

Alternative is to provide your own media formatter - and implementation which encapsulates this.

answered Feb 26 '12 at 13:38

Aliostad

80,612
21
160
208

Please note - if the atom feed has "text/xml" or "application/xml" as the Content-Type, "converting the result straight to feed" works fine, using the XmlSerializer in the background. So the problem must have a solution using only configuration/mapping. – Sergey Aldoukhov Feb 26 '12 at 18:27
@SergeyAldoukhov so if the content-type is XML, it works? I am surprised... they must have hard-coded this translation from that namespace+root into Feed, which if it is then really bad. – Aliostad Feb 26 '12 at 19:10

Reading custom Content-Type (f.e. StackOverflow) feeds using HttpClient from WebAPI

2 Answers2