Loading content
HTTP is the fundamental protocol of the World Wide Web. It enables the retrieval of information and data exchange between clients and servers over the internet. HTTP is simple, lightweight, and facilitates efficient communication.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
HTTP is a stateless application protocol through which clients request resources and servers transfer responses.
HTTP emerged around the early World Wide Web developed by Tim Berners-Lee at CERN. The IETF standardized it in stages; HTTP/1.1 was specified in RFC 2616 and later revised into RFC 7230 and related documents.
A client sends a request line with method, target, and headers. The server processes it and returns a status code, headers, and optional content; caching, cookies, and connections add further behavior.
The client describes method, target, and input.
The server returns status, metadata, and content.
Each request generally carries its own context.
HTTP connects browsers, APIs, and services. Methods, status codes, caching, and security headers shape reliability and maintainability.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.