aspnet-basics/2-controllers-and-http-responses.md

marp	paginate	math	theme	title
true	true	mathjax	buutti	2. HTTP Responses

HTTP Responses

ASP.NET Status Codes

• For a primer on HTTP status codes, check Frontend basics: Lecture 2

• There are multiple possible status codes for each action

• The ControllerBase the controllers should inherit from includes result methods for creating ActionResult objects

  • All ActionResult objects implement the IActionResult interface
  • Includes at least a status code, and can contain data such as view items or an error message
  • This result is processed into a response to then sent to client

Result methods

Status Code	Result Method	Usage
200 - OK	Ok()	GET, DELETE
201 - Created	Created()	POST
204 - No content	NoContent()	PUT, PATCH
400 - Bad request	BadRequest()	POST, PUT, PATCH
404 - Not found	NotFound()	All actions
Custom	StatusCode()	All actions

Status code example

[HttpGet("{id}")]
public IActionResult GetContactById(int id)
{
  // Contacts = list of contact objects, fetched from some repository
  var contact = Contacts.FirstOrDefault(c => c.Id == id);
  if (contact == null)
  {
    return NotFound();
  }
  return Ok(contact);
}

---

• The previous code first attempts to find a Contacts object using the ID provided in the URI parameter
  • If an item is not found, a 404 response is returned using NotFound() ➡
  • Otherwise, the object is sent as a payload with a 200 OK code response using Ok(contact) ➡

Exercise 1: Returning status codes

1. Without using parameter constraints, modify your number list method from Lecture 1, Exercise 3 to return a status code 400 (Bad Request) if k is smaller than 1 or larger than 100.
2. Add a helpful error message to the result for both cases. The message should be seen as a message body in the response.
3. Test with Swagger/Postman.