Well, for that, we can prepend the attribute to the parameter like so. But what if we want to use the querystring? As a result, we are not going to try and attempt to fix the 415 errors with the other HTTP POST content types.īut how do we fix the HTTP GET request? Now we could make the request using the application/json type. When using any REST API, a HTTP POST request will typically expect an application/json content type as it's request. We have made extensive efforts to explain all basic and advanced trou.
However, the application/json content type request is returning a 200 response, and is binding our request to our model. Do you want to fix your not working problem Then, read the post ahead. Interestingly, the HTTP GET request using a querystring is throwing a 415 error, alongside the form-data and x-www-form-url-encoded content types in the HTTP POST request. We are running our ASP.NET Core Web API on These are the tests we are running, and the responses returned. Now that we've done that, we are going to run some tests in Postman.
0 kommentar(er)
