HTTP
HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
Designing AI Systems
HTTP is the stateless application-layer protocol used to transfer requests and responses between networked clients and services.
- How it is used
- Uses HTTP to expose workflows consistently to external clients across technology stacks.
- How deep it goes
- Explains methods, headers and three interaction patterns through workflow requests, without detailing HTTP protocol internals.
- Examples
- Illustrates image categorization, research job tracking and a patient assistant’s streamed response.
- What you can do after
- Evaluate HTTP interaction patterns for workflow latency and client experience.
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
- Maps identified API resources, actions, inputs, and outputs into requests and responses that consumers can use.
- How deep it goes
- Explains request–response basics and a path, method, data-location, and status selection process; defers detailed data modeling.
- Examples
- Uses browser and curl page retrieval, product search, and deletion of a nonexistent product.
- What you can do after
- Apply it via curl to inspect resource requests and responses, then map API operations to appropriate methods 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
- Explains HTTP to help readers understand web frameworks, improve performance, and diagnose problems.
- How deep it goes
- Explains networking layers, works through a GET request, and reaches manual HTTP construction over TCP without surveying the full stack.
- Examples
- Demonstrates a Rust HTTP/1.0 GET request with a Host header and a manual client assembled from networking components.
- What you can do after
- Build a basic HTTP GET client with Rust TCP streams or assemble a manual client from networking components.
Read how Rust in Action: Systems programming concepts and techniques explains HTTP →
Vanilla Web
The application-layer protocol used to transfer resources and messages between web clients and servers.
- How it is used
- Connects a browser interface to backend endpoints for fetching, sending, and streaming data.
- How deep it goes
- Identifies HTTP’s place in the web stack and its data-transfer roles, without detailing request syntax or protocol internals.
- Examples
- Uses fetching, sending, and streaming application data as concrete HTTP tasks.
- What you can do after
- Evaluate/understand HTTP’s role in moving data between a browser interface and a backend.
Systems Programming with Zig
HTTP is an application-layer network protocol that defines request and response semantics for transferring hypertext and related resources.
- How it is used
- Uses HTTP to turn a word-ladder REPL into a web application.
- How deep it goes
- Explains protocol layers and request-response components, then points to Mozilla documentation for detailed HTTP reference.
- Examples
- Illustrates GET and POST requests with 200, 404, and body examples.
- What you can do after
- Apply HTTP via Zig’s std.http with a std.net TCP server to parse requests and respond.
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.
Also covered in
- Advanced Algorithms and Data Structures
- The Quick Python Book, Fourth Edition
- ASP.NET Core in Action, 3e
- F# in Action: A Revised Edition of Get Programming with F#
- Quarkus in Action
- Build and Orchestrator in Go (From Scratch)
- Java Persistence with Spring Data and Hibernate epub
- Django in Action
- Platform Engineering on Kubernetes
- ActiveMQ in Action
- Acing the Certified Kubernetes Administrator Exam, Second Edition
- Acing the CCNA Exam: Volume 1 Fundamentals and Protocols
What to know first
- JSONJSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- serverA server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.
- RESTREST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
- HTTP requestAn HTTP request is a message sent by a client to a server using the Hypertext Transfer Protocol, specifying a method and target and optionally including headers and a body.
Related concepts
- RESTused by · REST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
- HTTPScontrasts with · HTTPS is HTTP carried over TLS to provide encrypted communication and authentication between network endpoints.
- contractused by · A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- TCPuses · TCP (Transmission Control Protocol) is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of a byte stream between network endpoints.
- web serviceused by · A web service is a network-accessible software service that exposes functionality or data through a defined interface using web protocols.
Questions about HTTP
What is HTTP?
HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
Which Manning books explain HTTP?
Designing AI Systems, The Design of Web APIs, Second Edition, Building Web APIs with ASP.NET Core, Rust Servers, Services, and Apps, .NET in Action, Second Edition, Build Python Web Apps with Streamlit, Rust in Action: Systems programming concepts and techniques, Vanilla Web and 3 more.
What should I know before learning HTTP?
Manning books that teach HTTP usually introduce JSON, server, REST and HTTP request first.
What is the difference between HTTP and HTTPS?
HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems. HTTPS is HTTP carried over TLS to provide encrypted communication and authentication between network endpoints.
What is HTTP a kind of?
HTTP is a kind of network protocol. A network protocol is a defined set of rules and message formats governing how systems communicate and exchange data over a network.
What is HTTP also called?
HTTP is also called Hypertext Transfer Protocol.
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.










