frombodyattribute

I've got this code in a Web API Controller: [Route("{unit}/{begindate}/{enddate}")] [HttpPost] public void Post(string unit, string begindate, string enddate, [FromBody] string stringifiedjsondata) { List<ProduceUsageSPResults> _produceUsageList = JsonConvert.DeserializeObject<List<ProduceUsageSPResults>>(stringifiedjsondata); string _unit = unit; string _begindate = String.Format("{0}01", HyphenizeYYYYMM(begindate)); string _enddate = GetEndOfMonthFor(enddate); string appDataFolder = HttpContext.Current.Server.MapPath("~/App_Data/"); string htmlStr = ConvertProduceUsageListToHtml(

This is Asp.Net Webform application This is my POST method in my Apicontroller public void Post([FromBody]string value) { } I'm with fiddler post process. I did so experiment. But it did not. What is the problem. Can you help? I've tried it, I've failed. public void Post(MyViewModel model) { string aa = model.Value; } public class MyViewModel { public string Value { get; set; } } In Fiddler: Request Body: Value=hakan The POST body payload in Fiddler should be: =foo_bar instead of: value=foo_bar That's just one of those strange things about the model binding in the Web API. If you want to

I want to implement a REST API and need a body on my GET requests. (Like discussed here: HTTP GET with request body ) Are there http clients which are not able to send a body with a GET request? Fiddler is able to do it, although the message box is red. As a general rule, the idea of a GET in REST is that any of your parameters are sent in the URL. As the answer on the question you included indicates, it's doable but misses the point of REST, which is to have a consistent webbish interface. If you want to pass complex data to your endpoint, you probably want to use a POST, which your users