HTTP
HTTP is a standardized application-layer protocol that defines request-and-response messages for transferring resource representations between networked systems.
The Design of Web APIs, Second Edition
HTTP is the Hypertext Transfer Protocol, a standardized synchronous request–response protocol for exchanging resources and messages between clients and servers.
- How it is used
- Deploys HTTP as the interoperable interface between API consumers and servers, especially when representing REST operations.
- How deep it goes
- Explains request–response basics, resource paths, methods, status codes, data locations, semantic correctness, and version efficiency.
- Examples
- Uses browser, curl, Python requests, blog retrieval, product search, and CRUD-style resource paths as concrete HTTP examples.
- What you can do after
- Apply it via curl or Python requests to retrieve resources and design API operations with appropriate paths, methods, inputs, outputs, and statuses.
Read how The Design of Web APIs, Second Edition explains HTTP →
Building Web APIs with ASP.NET Core
HTTP is the stateless application-layer protocol used to transfer web resources and messages between clients and servers.
- How it is used
- Carries the requests and responses through which REST APIs access and manipulate resources.
- How deep it goes
- Defines the purposes of five request methods and describes REST statelessness without detailing HTTP message formats.
- Examples
- Uses GET, POST, PATCH, PUT, and DELETE actions alongside a REST request-response diagram.
- What you can do after
- Evaluate/understand which HTTP method matches a REST resource action and why each stateless call needs its own context.
Read how Building Web APIs with ASP.NET Core explains HTTP →
Rust Servers, Services, and Apps
The Hypertext Transfer Protocol is an application-layer protocol for transferring resources and messages over networks.
- How it is used
- Connects distributed web applications with browsers, clients, and external services through a universal application-layer protocol.
- How deep it goes
- Builds TCP servers, byte-stream conversion, static-page and JSON responses, then stops short of production-ready completeness.
- Examples
- Uses Rust servers, static pages, JSON data, REST APIs, cURL, browsers, Actix routes, and a distributed social-media stack.
- What you can do after
- Build basic HTTP servers, expose REST APIs, test them with cURL or browsers, and troubleshoot higher-level backend services.
.NET in Action, Second Edition
HTTP is an application-layer protocol for transferring resources and exchanging messages between clients and servers.
- How it is used
- Uses HTTP to retrieve JSON API resources and support client-server request/response traffic.
- How deep it goes
- Explains HttpClient retrieval, JSON deserialization, request failures, HTTPS redirection, certificates, and HSTS, but not protocol internals.
- Examples
- Demonstrates xkcd metadata retrieval, title search, HTTPS redirection, development certificates, and production HSTS configuration.
- What you can do after
- Operate/configure HTTP clients and ASP.NET Core services that retrieve JSON, handle request failures, and enforce HTTPS.
Build Python Web Apps with Streamlit
HTTP is the application-layer protocol used to transfer web resources and exchange messages between clients and servers.
- How it is used
- Connects applications to external services through standardized web requests and responses.
- How deep it goes
- Defines clients, servers, URLs, methods, headers, parameters, and JSON, but does not descend into protocol internals.
- Examples
- Uses a weather forecast URL, date query parameter, JSON response, and API-key error response.
- What you can do after
- Apply it via API URLs, HTTP methods, parameters, headers, and JSON parsing.
Read how Build Python Web Apps with Streamlit explains HTTP →
Rust in Action: Systems programming concepts and techniques
HTTP (Hypertext Transfer Protocol) is an application-layer protocol for exchanging requests and responses between clients and servers.
- How it is used
- Uses HTTP to understand web frameworks, improve performance, and diagnose networking problems.
- How deep it goes
- Explains HTTP within layered networking and builds a raw TCP client, including connection, request, and response states.
- Examples
- Demonstrates HTTP through the Rust mget client, its modular project tree, and a state-driven TCP request implementation.
- What you can do after
- Builds a manually operated HTTP client that resolves domains and exchanges requests through TCP-level networking primitives.
Read how Rust in Action: Systems programming concepts and techniques explains HTTP →
The Well-Grounded Python Developer: How the pros use Python and Flask
HTTP is the application-layer protocol that defines how clients and web servers exchange requests and responses.
- How it is used
- Connects browsers and web servers through independent requests and responses in networked applications.
- How deep it goes
- Explains statelessness and basic request fields, but deliberately stops short of a full protocol definition.
- Examples
- Uses a browser request for an HTML path with GET, HTTP/1.1, Host, Accept, domain, and port details.
- What you can do after
- Evaluate/understand how browsers identify resources and how servers construct responses without retained request history.
Read how The Well-Grounded Python Developer: How the pros use Python and Flask explains HTTP →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
HTTP is the application-layer protocol used to exchange requests and responses across networks.
- How it is used
- Coordinates microservices through direct HTTP requests that return immediate handling results.
- How deep it goes
- Explains HTTP as a web-service foundation and demonstrates direct POST messaging, but defers protocol internals.
- Examples
- Uses a video-streaming service sending an HTTP POST message directly to a history service.
- What you can do after
- Apply HTTP to send direct messages between microservices and assess success from immediate responses.
Related concepts
- RESTused by · REST is an architectural style for distributed hypermedia systems that organizes interactions around resources and representations through constraints including a uniform interface, stateless communication, cacheability, and layered components.
- contractused by · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- HTTPScontrasts with · HTTPS is HTTP carried over TLS, which provides encryption and endpoint authentication for network communication.
- TCPuses · TCP is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of byte streams between network endpoints.
- web serviceused by · A web service is a programmatic software interface that exposes functionality or data through web technologies or network protocols, typically HTTP.
- protocolkind of · A protocol is a defined set of rules and conventions governing communication or interaction among systems, components, or participants.
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.