DataTerminology.comNEW
Also known as: HTTP
Application-layer protocol standard for transmitting hypermedia and APIs across the web.
DESCRIPTION
HTTP is the foundational, stateless requestâresponse protocol of the web that defines methods, headers, status codes, and content negotiation. It enables hypermedia retrieval and API communication between clients and servers. HTTP/1.1 established persistent connections and caching; HTTP/2 introduced multiplexing and header compression; HTTP/3 uses QUIC over UDP for lower latency. The protocolâs semantics separate from transport, allowing evolution without breaking applications. Widely supported across platforms, HTTP integrates with TLS for security and underpins RESTful and many RPC-style services.
ALTERNATIVE DEFINITIONS
MDN Web Docs
HTTP is an application-layer protocol for transmitting hypermedia documents, such as HTML.
Emphasizes HTTPâs role in transporting hypermedia documents.
IETF RFC Editor
This document defines the semantics of the Hypertext Transfer Protocol (HTTP).
Focuses on formal definition of HTTP semantics by the standards body.
MDN Web Docs
HTTP (Hypertext Transfer Protocol) is an application-layer protocol for transmitting hypermedia documents, such as HTML.
Highlights application layer and hypermedia focus.
Cloudflare
HTTP is the protocol used to transfer hypertext between two computers on the World Wide Web.
Focuses on client-server transfer over the web.
RELATED TERMS
Hypertext Transfer Protocol Secure TLS HTTP-2 HTTP-3 REST Uniform Resource Identifier Hypertext Markup Language WebSocket Caching Content Delivery Network TCP URL Header Status Codes
COMPETING TERMS
CoAP gRPC
RELATIONS
- Broader: Protocol
- Implemented by: Cache-Control Web Browser
KNOWLEDGE AREAS
Software Engineering Data Integration & Interoperability Infrastructure Cloud
TARGET AUDIENCE
Software Developer DevOps Engineer Software Architect Full Stack Developer Security Architect Cloud Architect Data Engineer
EXTERNAL SOURCES
- Wikipedia - Hypertext Transfer Protocol
- IETF - HTTP semantics specification
- IETF - HTTP/1.1 messaging spec
- IETF - HTTP/3 over QUIC spec
- MDN Web Docs - Developer-oriented HTTP overview
- MDN - HTTP overview and concepts
- Cloudflare - Plain-language HTTP explanation
TOP QUESTIONS
What is the core purpose of Hypertext Transfer Protocol?
HTTP standardizes how clients and servers exchange requests and responses, enabling hypermedia retrieval and APIs across the web. It underpins websites, REST services, and many remote calls.
Category: Definition
How do HTTP/2 and HTTP/3 improve Hypertext Transfer Protocol performance?
HTTP/2 adds multiplexing and header compression; HTTP/3 uses QUIC to reduce latency and improve reliability over UDP. Both significantly enhance throughput and user experience.
Category: Topic
Why is Hypertext Transfer Protocol stateless and what does that imply?
HTTP treats each request independently, simplifying servers and scaling. State is managed via cookies, tokens, or application data rather than the protocol itself.
Category: Misunderstanding
How does caching work in Hypertext Transfer Protocol?
HTTP defines cache-control headers and validators (ETag, Last-Modified) for freshness and revalidation, reducing bandwidth and improving performance when content is reusable.
Category: Management
What security risks exist when using Hypertext Transfer Protocol without encryption?
Plain HTTP exposes data to eavesdropping, tampering, and session hijacking. Use HTTPS to protect confidentiality, integrity, and authentication through TLS.
Category: Risks
Is REST required when building APIs with Hypertext Transfer Protocol?
No. HTTP supports REST, RPC, GraphQL, and other styles. REST leverages HTTP semantics, but architectural choice should match requirements and ecosystem.
Category: Opinion
What is content negotiation in Hypertext Transfer Protocol?
Servers select representations based on Accept headers and other cues, enabling clients to receive preferred formats (e.g., JSON, HTML, XML) for the same resource.
Category: Definition
How do headers and status codes contribute to Hypertext Transfer Protocol interoperability?
Standard headers and codes convey metadata, caching, authentication, and errors, making behavior predictable across diverse clients and servers.
Category: Requirements
What are common implementation mistakes with Hypertext Transfer Protocol?
Misusing status codes, ignoring cache headers, leaking sensitive data in URLs, and inconsistent content types can break clients and degrade performance.
Category: Mistakes
When should I consider protocols competing with Hypertext Transfer Protocol?
In constrained IoT, CoAP may be preferred; for binary RPC, gRPC over HTTP/2 is common. Evaluate resource limits and communication patterns.
Category: Alternatives