HTTP

Understand the idea

A request includes a method, URL, headers, and sometimes a body. A response includes a status, headers, and possibly a body. Content-Type describes body representation. Authorization carries a bearer token for the personal API.

A concrete example

POST /api/todos
Content-Type: application/json
Authorization: Bearer TOKEN

{"title":"Task","completed":false}

In the application

Thymeleaf forms and Postman/React requests all use HTTP, but their bodies and response representations differ.

HTML forms use GET or POST natively; JSON clients can issue PUT and DELETE directly.

See it in a working stage

• Stage 3: read two query parameters and return their sum
• Stage 5: submit a form and return the answer directly

Related concepts

• REST / resource API
• HTTP status codes
• Request-body binding