Skip to content
AITroveRead. Build. Understand.
Reading list

Web APIs

HTTP input and response contracts

Spring MVC handles HTTP requests through conversion, validation, controllers and response handling.

Learning roadmap

Read the contract, run the source-kit checks, and inspect a rejected input before extending the application. This subject covers Spring and Spring Boot together; Java language lessons remain in their own subject.

Prerequisites

Use Java object ownership, interfaces, exceptions and Maven builds before the framework-specific lessons.

Section lessons

Continue learning

Boot Foundations, Spring Core, Data & Transactions, Security, Testing, Production, Exercises, Quizzes, Projects.

Curriculum

Inspect the contract and its failure cases.

  1. 1Spring MVC request validation: reject invalid commands before mutation
  2. 2Spring MVC ProblemDetail: stable errors without leaking internals
  3. 3Spring API pagination: bounded requests and immutable snapshots
  4. 4Spring MVC CORS: a browser-origin policy is not authentication

Inspect the state boundary and run its checked fixture.

  1. 1Spring reactive foundations: request values and cancel a subscription

Follow the input contract, inspect failures and run the checked source.

  1. 1Spring WebFlux SSE: emit bounded receipt events and test HTTP encoding
  2. 2Spring WebFlux cancellation: observe downstream cleanup without undoing work

Read the contract, run the checked fixture and inspect the rejected path.

  1. 1Spring MVC conditional GET: validate the representation tag

Run the checked example, then inspect its rejected path and cost boundary.

  1. 1Spring MVC consumes and produces: 415 and 406 are different failures
  2. 2Spring MVC nested validation: reject a bad line before the handler

Check the invariant, run the fixture and test a rejected boundary.

  1. 1Spring If-Match writes: reject a stale receipt revision

Run the source-kit fixture and inspect its rejected boundary.

  1. 1Spring POST idempotency keys: replay the same receipt result
  2. 2Spring retry and stale-write checks: choose the right HTTP contract

Run the source-kit test and inspect the rejected case.

  1. 1Spring MVC validation paths: object constraints and method parameters
  2. 2Spring MVC validation errors: one public ProblemDetail for two failure paths

Trace a tenant-scoped command from token to committed rows.

  1. 1Spring POST idempotency keys: bind replay to tenant and command

Check byte, storage and operational health boundaries.

  1. 1Spring MVC multipart receipt import: validate before storing
  2. 2Spring multipart size limits: enforce parser and application budgets
  3. 3Spring CSV uploads: reject malformed UTF-8 and an unknown header

Follow the boundary from local fixtures to a release test.

  1. 1Spring RestClient request factories: pin the transport you test
  2. 2Spring HTTP client timeouts: bound the call inside the request deadline
  3. 3Spring HTTP retries: only replay a command with a defined identity

Read the checked transport, timeout and replay contracts.

  1. 1Spring RestClient transport: run the factory you configured
  2. 2Spring RestClient 503 response: count attempts before adding a retry
  3. 3Spring RestClient read timeout: reject a server that accepts but stalls
  4. 4Spring HTTP timeout after POST: the write may already exist
  5. 5Spring HTTP replay key: two requests, one modeled reservation
Storage details