Welcome back to your advanced journey in mastering RESTful techniques with Spring Boot! In our previous lessons, we delved into validating request data, handling exceptions gracefully, and negotiating content types. Today, we’re stepping into the realm of HTTP headers — key-value pairs that play a crucial role in RESTful services. You will learn what HTTP headers are, their use cases, and how to work with them effectively in Spring Boot.

You're already familiar with key components of HTTP requests and responses, such as HTTP methods, URIs, and bodies. Now it’s time to delve into HTTP headers. Simply put, headers are metadata associated with requests and responses, formatted as key-value pairs. They provide essential information that helps both the client and server understand how to process the data being exchanged.

Here's an example of an HTTP request showing the URI, method, body, and headers:

POST /api/todos HTTP/1.1
Host: example.com
Content-Type: application/json
Authorization: Bearer <token>
Accept: application/json
Accept-Language: en-US

{
    "title": "Finish homework",
    "description": "Complete the math and science homework.",
    "dueDate": "2023-10-20"
}

In this example:

• Method: POST
• URI: /api/todos
• Headers: Content-Type, Authorization, Accept, and Accept-Language
• Body: The JSON payload contains the to-do item details

HTTP headers serve many purposes. Here are some common headers and how they're used:

• Accept: Informs the server about the types of data the client can process (Accept: application/json).
• Accept-Language: Specifies the preferred languages (Accept-Language: en-US, fr-CA).
• Authorization: Contains credentials for authenticating the client (Authorization: Bearer <token>).
• Cache-Control: Directs caching mechanisms (Cache-Control: no-cache).
• Content-Type: Indicates the media type of the resource (Content-Type: application/json).
• Content-Length: The size of the resource in bytes (Content-Length: 348).

Sometimes headers can have multiple values; for example:

• Set-Cookie: Allows the server to pass multiple cookies (Set-Cookie: sessionId=abc; Expires=Wed, 09 Jun 2021 10:18:14 GMT;).

Let's start by retrieving a specific header from the request by its name. Here’s an example using the @RequestHeader annotation:

@GetMapping("/todos/{id}")
fun getTodoItemById(@PathVariable id: Int, @RequestHeader("Accept-Language") acceptLanguage: String): ResponseEntity<TodoItem> {
    println("Accept-Language: $acceptLanguage")
    val todoItem = todoItemRepository.findById(id)
            .orElseThrow { NoSuchElementException("Todo item with id $id not found") }
    return ResponseEntity(todoItem, HttpStatus.OK)
}

In this snippet, the function getTodoItemById retrieves a specific to-do item by its ID. The @RequestHeader("Accept-Language") annotation extracts the Accept-Language header from the HTTP request and assigns it to the acceptLanguage variable. This value is then printed to the console.

Instead of using java.util.Optional, Kotlin's null safety features can handle the absence of a header gracefully:

@GetMapping("/todos/{id}")
fun getTodoItemById(@PathVariable id: Int, @RequestHeader("Accept-Language") acceptLanguage: String?): ResponseEntity<TodoItem> {
    acceptLanguage?.let { println("Accept-Language: $it") }
    val todoItem = todoItemRepository.findById(id)
            .orElseThrow { NoSuchElementException("Todo item with id $id not found") }
    return ResponseEntity(todoItem, HttpStatus.OK)
}

In this example, the @RequestHeader("Accept-Language") annotation uses a nullable String to handle the optional Accept-Language header. The let function prints the header value if it is present.

To add headers to the response, we can use the ResponseEntity class, which allows us to set headers easily:

@GetMapping("/todos")
fun getAllTodoItems(): ResponseEntity<List<TodoItem>> {
    val responseHeaders = HttpHeaders()
    responseHeaders["X-Custom-Header"] = "CustomHeaderValue"
    return ResponseEntity(todoItemRepository.findAll(), responseHeaders, HttpStatus.OK)
}

In this example, the getAllTodoItems function adds a custom header to the response. A new HttpHeaders object is created, and a custom header (X-Custom-Header) is set. The ResponseEntity constructor includes the list of to-do items, response headers, and the HTTP status code.

In this lesson, we explored the significance of HTTP headers in RESTful services, learned how to retrieve specific and all headers from requests, utilized the HttpHeaders class for enhanced readability, and added custom headers to responses. Equipped with this knowledge, you are ready to tackle the forthcoming practice exercises where you'll apply these concepts hands-on.