{"id":783,"date":"2012-04-11T16:05:59","date_gmt":"2012-04-11T16:05:59","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/odatateam\/2012\/04\/11\/what-happened-to-applicationjson-in-wcf-ds-5-0\/"},"modified":"2012-04-11T16:05:59","modified_gmt":"2012-04-11T16:05:59","slug":"what-happened-to-applicationjson-in-wcf-ds-5-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/odata\/what-happened-to-applicationjson-in-wcf-ds-5-0\/","title":{"rendered":"What happened to application\/json in WCF DS 5.0?"},"content":{"rendered":"

The roadmap for serialization formats<\/h2>\n

We have been talking for a while<\/a> about a more efficient format<\/a> for JSON serialization. The new serialization format will be part of the OData v3 protocol, and we believe that the much-improved JSON format should be the default response when requesting application\/json<\/b>.<\/p>\n

You may notice that when you upgrade to WCF DS 5.0, requesting the old JSON format is a bit different. To get the old JSON format, you must now explicitly request application\/json;odata=verbose or set the MaxDataServiceVersion header to 2.0.<\/p>\n

When will I get a 415 response and what can I do about it?<\/h2>\n

WCF Data Services 5.0 will return a 415 in response to a request for application\/json if the service configuration allows a v3 response<\/a> and if the client does not specify a MaxDataServiceVersion header or specifies a MaxDataServiceVersion header of 3.0. Clients should always send a value for the MaxDataServiceVersion header to ensure forward compatibility.<\/b><\/p>\n

There are two ways to get a response formatted with JSON verbose:<\/p>\n

1. Set the MaxDataServiceVersion header<\/a> to 2.0 or less. For instance:<\/p>\n

\n

GET <\/font>http:\/\/odata.example.org\/Items?$top=5<\/font><\/a> HTTP\/1.1<\/font><\/p>\n

Host: odata.example.org<\/font><\/p>\n

Connection: keep-alive<\/font><\/p>\n

User-Agent: Mozilla\/5.0 (Windows NT 6.2; WOW64) AppleWebKit\/535.19 (KHTML, like Gecko) Chrome\/18.0.1025.152 Safari\/535.19<\/font><\/p>\n

Accept: application\/json<\/font><\/p>\n

Accept-Encoding: gzip,deflate,sdch<\/font><\/p>\n

Accept-Language: en-US,en;q=0.8<\/font><\/p>\n

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3<\/font><\/p>\n

MaxDataServiceVersion: 2.0<\/font><\/p>\n<\/blockquote>\n

2. Request a content type of application\/json;odata=verbose<\/a>. For instance:<\/p>\n

\n

GET <\/font>http:\/\/odata.example.org\/Items?$top=5<\/font><\/a> HTTP\/1.1<\/font><\/p>\n

Host: odata.example.org<\/font><\/p>\n

Connection: keep-alive<\/font><\/p>\n

User-Agent: Mozilla\/5.0 (Windows NT 6.2; WOW64) AppleWebKit\/535.19 (KHTML, like Gecko) Chrome\/18.0.1025.152 Safari\/535.19<\/font><\/p>\n

Accept: application\/json;odata=verbose<\/font><\/p>\n

Accept-Encoding: gzip,deflate,sdch<\/font><\/p>\n

Accept-Language: en-US,en;q=0.8<\/font><\/p>\n

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3<\/font><\/p>\n

MaxDataServiceVersion: 3.0<\/font><\/p>\n<\/blockquote>\n

It\u2019s possible to modify the headers with jQuery as follows:<\/p>\n

\n

$.ajax(url, {<\/font><\/font><\/span><\/p>\n

    dataType: <\/font><\/span>"json", <\/font><\/span><\/font>\/\/ this tells jquery that you are expcting a json object and so it will parse the data for you.<\/font><\/span><\/font><\/span><\/p>\n

    beforeSend: <\/font><\/span>function<\/font><\/span><\/font> (xhr) {<\/font><\/span><\/font><\/p>\n

        xhr.setRequestHeader(<\/font><\/span>"Accept"<\/font><\/span>, <\/span>"application\/json;odata=verbose"<\/font><\/span><\/font>);<\/font><\/span><\/font><\/p>\n

        xhr.setRequestHeader(<\/font><\/span>"MaxDataServiceVersion"<\/font><\/span>, <\/span>"3.0"<\/font><\/span><\/font>);<\/font><\/span><\/font><\/p>\n

    },<\/font><\/font><\/span><\/p>\n

    success: <\/font><\/span>function<\/font><\/span><\/font> (data) {<\/font><\/span><\/font><\/p>\n

       <\/font><\/span>\/\/ do something interesting with the data you get back.<\/font><\/span><\/font><\/p>\n

    }<\/font><\/font><\/span><\/p>\n

});<\/font><\/font><\/span><\/p>\n<\/blockquote>\n

Why did WCF DS 5.0 ship before JSON light?<\/h2>\n

We had a set of features that were ready to be released as part of WCF DS 5.0. The more efficient JSON implementation is currently in progress and will be released sometime later this year.<\/p>\n","protected":false},"excerpt":{"rendered":"

The roadmap for serialization formats We have been talking for a while about a more efficient format for JSON serialization. The new serialization format will be part of the OData v3 protocol, and we believe that the much-improved JSON format should be the default response when requesting application\/json. You may notice that when you upgrade […]<\/p>\n","protected":false},"author":512,"featured_media":3253,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-783","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-odata"],"acf":[],"blog_post_summary":"

The roadmap for serialization formats We have been talking for a while about a more efficient format for JSON serialization. The new serialization format will be part of the OData v3 protocol, and we believe that the much-improved JSON format should be the default response when requesting application\/json. You may notice that when you upgrade […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts\/783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/users\/512"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/comments?post=783"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts\/783\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/media\/3253"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/media?parent=783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/categories?post=783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/tags?post=783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}