ASP Experts

Here’s a few updates coming your way in ASP.NET Web API. The code has been checked into our CodePlex source code repository but haven’t yet been released as part of our official installer . Think of this as a sneak-peak for you to try out and comment on as part of our source code repository (see Getting Started With ASP.NET Web Stack Source on CodePlex for details). Cookie Support Until now the HTTP Cookie and Set-Cookie headers were only exposed as raw strings and not structured classes in the HttpRequestMessage and HttpResponseMessage classes. This made it cumbersome and error prone to work with cookies in ASP.NET Web API. To fix this we introduced two new classes called CookieHeaderValue and CookieState that follow the RFC 6265 HTTP State…(read more)

There are several good blogs on content negotiation in ASP.NET Web API (see for example ASP.NET Web API: How content negotiation works? ) describing how to get JSON, XML, and other response formats depending on what you ask for in a request using the Accept HTTP request header field . However, recently we added support for the header Accept-Charset which can be used by the client to indicate which character encoding it prefers the response to be encoded with. Typical encodings are UTF-8 and UTF-16 (and our built-in formatters support those) but the set is extensible to other encodings as well. Note: This is the first in a series of blogs on upcoming features that have been checked into our CodePlex source code repository but haven’t yet been…(read more)