Hypertext Transfer Protocol

Hypertext Transfer Protocol
Name	Hypertext Transfer Protocol
Developer	Tim Berners-Lee; CERN
Introduced	1991
Latest release	Internet Engineering Task Force (IETF) standards
Type	Application layer protocol

Hypertext Transfer Protocol is an application-layer protocol for distributed, collaborative, hypermedia information systems, originally designed to enable retrieval of linked documents and resources across the World Wide Web. It defines request–response semantics between clients and servers and underpins interactions between Web browsers, Web servers, and intermediary systems such as Proxy servers, Content delivery networks, and Load balancers. Influential figures and organizations in its creation and evolution include Tim Berners-Lee, Roberto di Cosmo, Internet Engineering Task Force, and World Wide Web Consortium.

Overview

HTTP provides a stateless, extensible framework for transmitting representations of resources identified by Uniform Resource Identifiers between user agents like Netscape Navigator, Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, and servers such as Apache HTTP Server, Nginx, and Microsoft Internet Information Services. The protocol operates over transport protocols like Transmission Control Protocol and Stream Control Transmission Protocol, with secure deployments layered over Transport Layer Security and historically Secure Sockets Layer. Core concepts link to systems and standards including Hypertext Markup Language, MIME, XML, and JSON for representation formats, and to deployment platforms like Amazon Web Services, Google Cloud Platform, Microsoft Azure, and Heroku.

History and Development

HTTP originated at CERN in the early 1990s as part of the project led by Tim Berners-Lee with contributions from collaborators in institutions like MIT and research groups tied to European Organization for Nuclear Research. Early implementations and demonstrations involved browsers on workstations connected to Internet backbones and services that later evolved into major projects such as World Wide Web Consortium standards and IETF Requests for Comments authored by contributors including Roy Fielding. The protocol’s evolution intersected with milestones like the rise of Apache HTTP Server, the commercialization of the web by companies like Netscape Communications Corporation and Microsoft Corporation, and standardization efforts reflected in documents from RFC 1945, RFC 2616, and later RFCs that guided modern web architecture used by enterprises such as Facebook, Twitter, Wikipedia, and YouTube.

Protocol Architecture and Operation

HTTP follows a client–server model where Web browsers or automated clients issue requests to origin servers; intermediaries such as Proxy servers, Reverse proxys, and Content delivery networks may cache or forward messages. Architectural constraints and design principles were influenced by concepts articulated at conferences like SIGGRAPH and in publications from ACM and IEEE. HTTP sessions are typically managed over TCP/IP sockets; the protocol’s semantics are defined separately from underlying transports, enabling deployment over platforms including IPv4, IPv6, and tunneling technologies used by services such as Cloudflare and Akamai Technologies. Related internet infrastructure projects influencing HTTP include Domain Name System, Border Gateway Protocol, and routing efforts by organizations like IANA and ICANN.

Message Structure and Methods

HTTP messages comprise start-lines, header fields, and optional message bodies. Request methods include standardized verbs such as GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE, and CONNECT, used in systems ranging from RESTful APIs at companies like Amazon.com and Google to web applications built with frameworks such as Django, Ruby on Rails, Express.js, and ASP.NET. Response status codes (1xx–5xx) communicate outcomes for clients and intermediaries; common codes like 200 OK, 301 Moved Permanently, 404 Not Found, and 500 Internal Server Error are handled by server software including Apache Tomcat and Jetty. Message headers such as Host, Content-Type, Accept, Cache-Control, and Set-Cookie interact with standards and services like RFC 7231, RFC 7234, OAuth, SameSite cookie policy, and authentication systems used by OAuth 2.0 providers and identity platforms like Okta and Auth0.

Security (HTTPS and TLS)

Secure HTTP deployments use HTTPS, which layers HTTP over Transport Layer Security to provide confidentiality, integrity, and endpoint authentication. Certificate management and trust involve certificate authorities such as Let's Encrypt, DigiCert, and Entrust, and protocols like OCSP and DNS Certification Authority Authorization that relate to ecosystem services offered by Cloudflare and Amazon Certificate Manager. Security incidents and mitigation strategies are documented by organizations including CERT and regulatory frameworks overseen by entities such as European Commission directives impacting privacy and compliance with laws like General Data Protection Regulation applied by companies such as Google LLC and Meta Platforms, Inc..

Extensions, Versions, and Standards Evolution

HTTP has evolved through major versions and extension mechanisms standardized by the IETF and influenced by researchers such as Roy Fielding. HTTP/0.9, HTTP/1.0, and HTTP/1.1 introduced persistent connections and pipelining; HTTP/2 introduced binary framing, multiplexing, header compression (HPACK) and was influenced by efforts from Google’s SPDY project; HTTP/3 replaces TCP with QUIC (originally developed by Google LLC and standardized via IETF QUIC), improving latency and connection migration. Extension mechanisms include upgrade headers, content negotiation, and registries maintained by IANA, with conformance testing and deployment tracked by vendors such as Mozilla Foundation, Apple Inc., and Microsoft Corporation.

Implementation, Performance, and Use Cases

Implementations span server software like Apache HTTP Server, Nginx, Lighttpd, and application servers such as Node.js and Tomcat, and client libraries in languages supported by ecosystems like Python Software Foundation’s requests and Java’s HttpClient. Performance optimization techniques include TLS session resumption, HTTP/2 multiplexing, HTTP/3 QUIC features, caching strategies used by Varnish, CDN edge computing by Cloudflare Workers, and protocol tuning in large-scale platforms such as Netflix, LinkedIn, and Spotify. Use cases range from traditional hypertext document delivery to RESTful microservices architectures in deployments by Uber Technologies, Airbnb, and Slack Technologies.

Category:Internet protocols