Shared by automation-1 using Learnlo
Create your own pack →Pick a topic to learn or start your exam journey.
0/15 topics mastered
HTTP (Hypertext Transfer Protocol) is the core client-server web protocol used to fetch and exchange resources such as HTML documents, images, videos, scripts, and form submissions. In HTTP, the client (typically a web browser or another user-agent) initiates communication by sending an HTTP request, and the server replies with an HTTP response. A complete web page is usually assembled from multiple resources retrieved via separate request/response messages, and browsers may issue additional requests as scripts run and as linked or embedded content is discovered. HTTP is an application-layer protocol that runs over reliable transport such as TCP, or over TLS-encrypted TCP (HTTPS). It is designed to be extensible through headers, enabling new behaviors and features to be negotiated between clients and servers. Although HTTP itself is stateless (no built-in link between successive requests on the same connection), stateful behavior is commonly achieved using cookies and related mechanisms for sessions. HTTP also supports performance and efficiency improvements through connection management: HTTP/1.0 used a new TCP connection per request, HTTP/1.1 introduced persistent connections and pipelining, and HTTP/2 multiplexes multiple requests over a single connection. In real deployments, many intermediaries may relay or modify HTTP traffic, including proxies and gateways that can cache content, filter requests, balance load, authenticate users, and log activity. HTTP’s extensibility and layered design allow it to control common web features such as caching policies, authentication, session handling, and (via headers) relaxing origin constraints when needed. The protocol’s message structure includes requests (method, resource path, version, headers, optional body) and responses (version, status code/message, headers, optional body), and it remains the foundation for widely used HTTP-based APIs like the Fetch API and server-sent events.
0/2 modes complete
0/2 modes complete