User agent (redirect from HTTP client)
email clients, standalone download managers like youtube-dl, and other command-line utilities like cURL. The user agent is the client in a client–server...
1 KB (115 words) - 18:52, 31 May 2025
Development of HTTP was initiated by Tim Berners-Lee at CERN in 1989 and summarized in a simple document describing the behavior of a client and a server...
61 KB (7,794 words) - 11:04, 23 June 2025
Hypertext Transfer Protocol (HTTP) response status codes are issued by a server in response to a client's request made to the server. It includes codes...
46 KB (5,599 words) - 10:40, 11 June 2025
communications between a client and server protects the communications against eavesdropping and tampering. The authentication aspect of HTTPS requires a trusted...
42 KB (4,314 words) - 11:05, 23 June 2025
HTTP header fields are a list of strings sent and received by both the client program and server on every HTTP request and response. These headers are...
53 KB (2,491 words) - 19:46, 6 June 2025
Web server (redirect from HTTP Server)
HTTP responses compatible with versions of client HTTP requests, (e.g., HTTP/1.0, HTTP/1.1, HTTP/2, HTTP/3). Logging: usually web servers have also the...
86 KB (9,910 words) - 04:41, 21 June 2025
fulfill it, if it was correct. HTTP 403 provides a distinct error case from HTTP 401; while HTTP 401 is returned when the client has not authenticated, and...
6 KB (654 words) - 13:05, 8 June 2025
Session (computer science) (redirect from HTTP sessions: Client vs Server side)
it easier to maintain the Web Session and supporting HTTP cookies and file uploads. Most client-server sessions are maintained by the transport layer...
14 KB (1,962 words) - 07:19, 28 September 2024
Server Name Indication (redirect from Encrypted Client Hello)
the conceptual equivalent to HTTP/1.1 name-based virtual hosting, but for HTTPS. This also allows a proxy to forward client traffic to the right server...
34 KB (2,832 words) - 21:00, 1 June 2025
service requesters, called clients. Often clients and servers communicate over a computer network on separate hardware, but both client and server may be on...
26 KB (3,094 words) - 19:19, 10 June 2025
allows clients and servers to elect to use HTTP/1.1, 2.0, or potentially other non-HTTP protocols. Maintain high-level compatibility with HTTP/1.1 (for...
39 KB (3,804 words) - 20:16, 20 June 2025
it behind a flag. Open-source libraries that implement client or server logic for QUIC and HTTP/3 include On 7 June 2021, LiteSpeed Web Server (and OpenLiteSpeed)...
19 KB (1,588 words) - 03:09, 22 May 2025
selecting an HTTP (not HTTPS) URL to the site, the client, such as a Web browser, will automatically upgrade to HTTPS without making an HTTP request, thereby...
24 KB (2,296 words) - 23:37, 17 June 2025
WebSocket (section Client example)
from the HTTP protocol to the WebSocket protocol. The WebSocket protocol enables full-duplex interaction between a web browser (or other client application)...
54 KB (3,915 words) - 16:54, 18 June 2025
HEAD, the client must ask the user before redirecting. Client request: GET /index.php HTTP/1.1 Host: www.example.org Server response: HTTP/1.1 301 Moved...
6 KB (797 words) - 05:30, 17 February 2025
indicates a client error, such as a mistyped Uniform Resource Locator (URL). The following two digits indicate the specific error encountered. HTTP's use of...
16 KB (1,945 words) - 23:09, 3 June 2025
Basic access authentication (redirect from HTTP basic authentication)
Caching policy differs between browsers. HTTP does not provide a method for a web server to instruct the client to "log out" the user. However, there are...
7 KB (863 words) - 12:00, 21 May 2025
Push technology (redirect from HTTP streaming)
information to the subscribed client. Under certain conditions, such as restrictive security policies that block incoming HTTP requests, push technology is...
21 KB (2,447 words) - 09:35, 22 April 2025
file is partitioned into one or more segments and delivered to a client using HTTP. A media presentation description (MPD) describes segment information...
30 KB (2,562 words) - 20:51, 24 January 2025
Social Operating System. p. 237 HTTP State Management Mechanism. doi:10.17487/RFC6265. RFC 6265. "Persistent client state HTTP cookies: Preliminary specification"...
93 KB (10,944 words) - 02:30, 24 June 2025
Client Hints is an extension to the HTTP protocol that allows servers to ask the client (usually a web browser) for information about its configuration...
16 KB (1,946 words) - 06:28, 6 June 2025
Web cache (redirect from HTTP cache)
A web cache (or HTTP cache) is a system for optimizing the World Wide Web. It is implemented both client-side and server-side. The caching of multimedia...
6 KB (496 words) - 04:48, 24 June 2025
Task Force (IETF) in the RFC 7231 specification. The HTTP 402 status code indicates that the client must make a payment to access the requested resource...
5 KB (650 words) - 00:51, 19 December 2024
The most common form of HTTP tunneling is the standardized HTTP CONNECT method. In this mechanism, the client asks an HTTP proxy server to forward the...
5 KB (596 words) - 14:57, 1 February 2025
Proxy server (redirect from HTTP proxy)
proxy server is a server application that acts as an intermediary between a client requesting a resource and the server providing that resource. It improves...
47 KB (5,574 words) - 22:22, 26 May 2025
Web browser (redirect from HTTP clients)
transfer. For this reason, a web browser is often referred to as an HTTP client or a user agent. Requisite materials, including text, style sheets, images...
27 KB (2,516 words) - 03:23, 19 June 2025
HTTP header field introduced in HTTP/1.1. In the exchange, the client begins by making a cleartext request, which is later upgraded to a newer HTTP protocol...
4 KB (540 words) - 00:05, 26 May 2025
HTTP/2 Server Push is an optional feature of the HTTP/2 and HTTP/3 network protocols that allows servers to send resources to a client before the client...
8 KB (787 words) - 21:50, 29 October 2024
rewrite POST to GET. Client request: GET /index.html HTTP/1.1 Host: www.example.com Server response: HTTP/1.1 302 Found Location: http://www.iana.org/domains/example/...
3 KB (304 words) - 19:23, 15 June 2025
this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining. The technique was...
17 KB (1,672 words) - 02:05, 2 June 2025