liveBook · Manning

HTTP status code

Also called response code, response status code, StatusCode

An HTTP status code is a standardized three-digit code in an HTTP response that indicates the outcome of processing a request.

How 12 Manning books explain it

Learn Go with Pocket-Sized Projects

An HTTP status code is a standardized numeric response indicator describing the result of an HTTP request.

How it is used
Uses status codes to validate client responses and communicate outcomes from HTTP handlers.
How deep it goes
Explains the five classes and implements status checking, response writing, and tests rather than cataloging every code.
Examples
Demonstrates an exchange-rate client, a game-creation endpoint, curl output, and recorder-based handler tests.
What you can do after
Apply it via Go's net/http and httptest packages to check, return, and test response statuses.

Read how Learn Go with Pocket-Sized Projects explains HTTP status code →

Crack Any Codebase with AI

An HTTP status code is a standardized numeric response classification indicating the outcome of an HTTP request.

How it is used
Uses status codes to read an API endpoint’s outcome as part of its interface contract.
How deep it goes
Introduces status codes through endpoint examples but stops short of detailed protocol behavior.
Examples
Uses a booking endpoint returning 201, 409, 405, and 401 as concrete outcome examples.
What you can do after
Evaluate API handlers by interpreting status codes alongside methods, request bodies, and authentication checks.

Read how Crack Any Codebase with AI explains HTTP status code →

ASP.NET Core in Action, 3e

An HTTP status code is a three-digit code in an HTTP response that indicates the result of processing the corresponding request.

How it is used
Uses status codes to communicate request outcomes to browsers and API clients.
How deep it goes
Defines the five status classes and common codes, explains response helpers, and points to RFC 9110 for the full standardized list.
Examples
Illustrates missing static files, fruit API lookups and creation, and a manually written teapot response.
What you can do after
Apply status codes using ASP.NET Core Results and TypedResults helpers or set them directly through HttpResponse.

Read how ASP.NET Core in Action, 3e explains HTTP status code →

The Design of Web APIs, Second Edition

An HTTP status code is a numeric code in an HTTP response that indicates the result of processing a request.

How it is used
Signals operation outcomes to API consumers and distinguishes successful responses from consumer- and server-caused failures.
How deep it goes
Works through status selection for create, search, read, update, delete, and common errors; defers fuller error options and long operations.
Examples
Uses product searches, creation, updates, deletion, missing resources, and an OpenAPI response without a body.
What you can do after
Apply it via OpenAPI to choose and describe success and error responses for resource operations.

Read how The Design of Web APIs, Second Edition explains HTTP status code →

Build Financial Software with Generative AI (From Scratch)

An HTTP status code is a numeric response indicator that communicates the outcome of an HTTP request.

How it is used
Uses status codes to guide API development and verify that endpoints respond as expected.
How deep it goes
Walks through 200, 201, 404, and 405 responses, testing and fixed FastAPI configuration, while deferring finer-grained status control.
Examples
Uses a file-upload POST, an ACH batches endpoint, and a company endpoint to illustrate response checks.
What you can do after
Apply it via FastAPI and Postman to configure a response code and test an endpoint’s status.

Read how Build Financial Software with Generative AI (From Scratch) explains HTTP status code →

Spring in Action, Sixth Edition

An HTTP status code is a three-digit code in an HTTP response that indicates the result of processing a request.

How it is used
Uses status codes to communicate REST request results to clients.
How deep it goes
Explains conditional response statuses and annotation-based statuses through controller implementations.
Examples
Uses taco retrieval and creation and order deletion to illustrate 200, 404, 201, and 204.
What you can do after
Apply it via Spring MVC using ResponseEntity or @ResponseStatus to select descriptive response codes.

Read how Spring in Action, Sixth Edition explains HTTP status code →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

An HTTP status code is a three-digit numeric code in an HTTP response that indicates the result of the corresponding request.

How it is used
Communicates the result of an HTTP request during REST API client-server exchanges.
How deep it goes
Defines five categories and common codes, but does not detail every code or implementation mechanism.
Examples
Uses ACL-rule creation with POST and 201 Created, plus examples including 200, 301, 403, 404, and 500.
What you can do after
Evaluate HTTP request results by interpreting the response code and its category.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains HTTP status code →

Contract Testing in Action

An HTTP status code is a numeric code in an HTTP response indicating the result of processing a request.

How it is used
Defines API response expectations within consumer-driven contract scenarios and migration from integration tests.
How deep it goes
Explains concrete response-code expectations and contract assertions, but does not detail HTTP status-code categories or protocol internals.
Examples
Uses movie retrieval, creation, duplication, deletion, Supertest assertions, and Pact interactions as concrete examples.
What you can do after
Apply it via Pact to specify and verify API response-code expectations across consumer and provider tests.

Read how Contract Testing in Action explains HTTP status code →

Go in Practice, Second Edition

An HTTP status code is a three-digit code in an HTTP response indicating the outcome of processing a request.

How it is used
Communicates request outcomes between HTTP servers and clients, especially for errors, authentication, retries, and custom API responses.
How deep it goes
Descends from status ranges to Go constants, response inspection, MIME checks, and custom errors, but leaves retry implementation incomplete.
Examples
Uses Go handlers, curl requests, status inspection, range classification, and custom JSON error conversion.
What you can do after
Diagnose/debug HTTP failures by classifying response codes, checking content types, authenticating, retrying selectively, and returning structured Go errors.

Read how Go in Practice, Second Edition explains HTTP status code →

gRPC Microservices in Go

A gRPC status code is a predefined code that identifies the outcome or error condition of an RPC.

How it is used
Guides interservice error handling and determines client actions such as retrying, timing out, or opening a circuit.
How deep it goes
Defines common gRPC codes and demonstrates structured validation errors, but does not detail the complete status-code catalog.
Examples
Uses order creation, invalid identifiers, quotas, missing orders, duplicate users, and Go field-violation handling.
What you can do after
Diagnose/debug with gRPC by classifying failures, reading structured validation details, and selecting appropriate resilience actions.

Read how gRPC Microservices in Go explains HTTP status code →

The Well-Grounded Python Developer: How the pros use Python and Flask

An HTTP status code is a numeric response code indicating the outcome of an HTTP request.

How it is used
Uses response codes to verify that a browser request reached a running web application and was processed successfully.
How deep it goes
Defines the code and explains 200 as “OK,” without cataloging other response-code categories.
Examples
Uses a browser request to a local Flask route, a “Hello World!” response, and a terminal log ending in 200.
What you can do after
Evaluate whether a local Flask request was handled successfully by reading the browser result and server log.

Read how The Well-Grounded Python Developer: How the pros use Python and Flask explains HTTP status code →

.NET in Action, Second Edition

An HTTP status code is a three-digit response code indicating the outcome of an HTTP request.

How it is used
Controls endpoint outcomes when successful operations or invalid request options require different HTTP responses.
How deep it goes
Explains default 200 responses, conditional 404 responses, built-in ActionResults, and file responses without detailing the full MVC pattern.
Examples
Uses ASCII-art font validation for 404 handling and barcode generation for JPEG file responses.
What you can do after
Apply it via ASP.NET Core Results to return success, not-found, content, or file responses from minimal API endpoints.

Read how .NET in Action, Second Edition explains HTTP status code →

Also covered in

What to know first

Related concepts

Questions about HTTP status code

What is HTTP status code?

An HTTP status code is a standardized three-digit code in an HTTP response that indicates the outcome of processing a request.

Which Manning books explain HTTP status code?

Learn Go with Pocket-Sized Projects, Crack Any Codebase with AI, ASP.NET Core in Action, 3e, The Design of Web APIs, Second Edition, Build Financial Software with Generative AI (From Scratch), Spring in Action, Sixth Edition, Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Contract Testing in Action and 4 more.

What should I know before learning HTTP status code?

Manning books that teach HTTP status code usually introduce JSON, HTTP, HTTP 404 error and HTTP method first.

What kinds of HTTP status code are there?

Kinds of HTTP status code include 500 Internal Server Error and 403 Forbidden.

What is HTTP status code a kind of?

HTTP status code is a kind of code. A code is a symbolic or numeric value assigned according to defined rules to represent, identify, or encode information or a domain concept.

What is HTTP status code part of?

HTTP status code is part of contract. A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.