To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
GET /Article HTTP/1.1
Host: tstsrvs.redhotpie.com.au
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<ArrayOfArticleListItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel">
<ArticleListItem>
<IsLiked xmlns="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">false</IsLiked>
<LikeCount xmlns="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">0</LikeCount>
<CommentCount xmlns="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">0</CommentCount>
<ArticleID>0</ArticleID>
<Author>
<ArticleAuthorID>0</ArticleAuthorID>
<ArticleCount>0</ArticleCount>
<Description>String</Description>
<FacebookLink>String</FacebookLink>
<Height>0</Height>
<ImageUrl>String</ImageUrl>
<InstagramLink>String</InstagramLink>
<Name>String</Name>
<TwitterLink>String</TwitterLink>
<Width>0</Width>
<YouTubeLink>String</YouTubeLink>
</Author>
<Categories>0</Categories>
<DatePublished>0001-01-01T00:00:00</DatePublished>
<ImageUrl>String</ImageUrl>
<SEOUrl>String</SEOUrl>
<ShortTitle>String</ShortTitle>
<Summary>String</Summary>
<Title>String</Title>
</ArticleListItem>
</ArrayOfArticleListItem>