Table of Contents
Hypertext Transfer Protocol HTTP Topics
Return to Cloud Monk Courses, Hypertext Transfer Protocol (HTTP), Hypertext, HTTP, Hyperlink, Hypermedia, HTTP Bibliography, HTTP Courses, HTTP Topics, Awesome HTTP
Short description: Application protocol for distributed, collaborative, hypermedia information systems.
- Snippet from Wikipedia: HTTP
HTTP (Hypertext Transfer Protocol) is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.
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 using the first HTTP version, named 0.9. That version was subsequently developed, eventually becoming the public 1.0.
Development of early HTTP Requests for Comments (RFCs) started a few years later in a coordinated effort by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C), with work later moving to the IETF.
HTTP/1 was finalized and fully documented (as version 1.0) in 1996. It evolved (as version 1.1) in 1997 and then its specifications were updated in 1999, 2014, and 2022. Its secure variant named HTTPS is used by more than 85% of websites.
HTTP/2, published in 2015, provides a more efficient expression of HTTP's semantics "on the wire". As of August 2024, it is supported by 66.2% of websites (35.3% HTTP/2 + 30.9% HTTP/3 with backwards compatibility) and supported by almost all web browsers (over 98% of users). It is also supported by major web servers over Transport Layer Security (TLS) using an Application-Layer Protocol Negotiation (ALPN) extension where TLS 1.2 or newer is required.
HTTP/3, the successor to HTTP/2, was published in 2022. As of February 2024, it is now used on 30.9% of websites and is supported by most web browsers, i.e. (at least partially) supported by 97% of users. HTTP/3 uses QUIC instead of TCP for the underlying transport protocol. Like HTTP/2, it does not obsolete previous major versions of the protocol. Support for HTTP/3 was added to Cloudflare and Google Chrome first, and is also enabled in Firefox. HTTP/3 has lower latency for real-world web pages, if enabled on the server, and loads faster than with HTTP/2, in some cases over three times faster than HTTP/1.1 (which is still commonly only enabled).
Category of Hypertext Transfer Protocol
The main article for this category is Hypertext Transfer Protocol.
Subcategories
This HTTP category has the following 5 subcategories, out of 5 total.
H
- Hypertext Transfer Protocol clients (2 C, 8 P)
W
- Web caching protocol (6 P)
- Web server software (3 C, 62 P)
Pages in category "Hypertext Transfer Protocol"
The following 43 pages are in this category, out of 43 total. This list may not reflect recent changes (learn more). Hypertext Transfer Protocol Topics:
A
B
C
D
F
H
- Httperf - see also HTTP performance
L
M
N
P
R
S
W
See Also
Hypertext Transfer Protocol (HTTP):
Request methods - HTTP Request methods
List of HTTP header fields - HTTP Header fields:
List of HTTP status codes - HTTP Status codes:
Security access control methods:
HTTP Protocol, HTTP Request, HTTP Response, HTTP Client, HTTP Server, HTTP Message, HTTP Header, HTTP Body, HTTP Method, HTTP Status Code, HTTP Version, HTTP URL, HTTP Uniform Resource Identifier (URI), HTTP Hypertext Transfer Protocol, HTTP Secure (HTTPS), HTTP TLS (Transport Layer Security), HTTP SSL (Secure Sockets Layer), HTTP Session, HTTP Persistent Connection, HTTP Keep-Alive, HTTP Pipeline, HTTP Chunked Transfer Encoding, HTTP Caching, HTTP Cache-Control Header, HTTP ETag Header, HTTP If-None-Match Header, HTTP If-Modified-Since Header, HTTP Last-Modified Header, HTTP Expires Header, HTTP Conditional Requests, HTTP Range Request, HTTP Content Negotiation, HTTP Accept Header, HTTP Accept-Language Header, HTTP Accept-Encoding Header, HTTP Content-Type Header, HTTP Content-Length Header, HTTP Content-Encoding Header, HTTP Content-Language Header, HTTP Content-Range Header, HTTP Transfer-Encoding Header, HTTP Chunked Encoding, HTTP Gzip Encoding, HTTP Deflate Encoding, HTTP Brotli Encoding, HTTP TE Header, HTTP Connection Header, HTTP Host Header, HTTP User-Agent Header, HTTP Referer Header, HTTP Origin Header, HTTP Authorization Header, HTTP WWW-Authenticate Header, HTTP Proxy-Authenticate Header, HTTP Proxy-Authorization Header, HTTP Cookie Header, HTTP Set-Cookie Header, HTTP Cookie-based Authentication, HTTP Basic Authentication, HTTP Digest Authentication, HTTP Bearer Token Authentication, HTTP SPNEGO Authentication, HTTP NTLM Authentication, HTTP Request Line, HTTP Status Line, HTTP Start Line, HTTP General Headers, HTTP Request Headers, HTTP Response Headers, HTTP Entity Headers, HTTP Hop-by-hop Headers, HTTP End-to-end Headers, HTTP Trailer Headers, HTTP Upgrade Header, HTTP ALPN (Application-Layer Protocol Negotiation), HTTP GET Method, HTTP POST Method, HTTP PUT Method, HTTP DELETE Method, HTTP HEAD Method, HTTP OPTIONS Method, HTTP TRACE Method, HTTP CONNECT Method, HTTP PATCH Method, HTTP Safe Methods, HTTP Idempotent Methods, HTTP Cacheable Methods, HTTP Status Code 200 OK, HTTP Status Code 201 Created, HTTP Status Code 202 Accepted, HTTP Status Code 204 No Content, HTTP Status Code 301 Moved Permanently, HTTP Status Code 302 Found, HTTP Status Code 303 See Other, HTTP Status Code 304 Not Modified, HTTP Status Code 307 Temporary Redirect, HTTP Status Code 308 Permanent Redirect, HTTP Status Code 400 Bad Request, HTTP Status Code 401 Unauthorized, HTTP Status Code 403 Forbidden, HTTP Status Code 404 Not Found, HTTP Status Code 405 Method Not Allowed, HTTP Status Code 406 Not Acceptable, HTTP Status Code 409 Conflict, HTTP Status Code 410 Gone, HTTP Status Code 415 Unsupported Media Type, HTTP Status Code 429 Too Many Requests, HTTP Status Code 500 Internal Server Error, HTTP Status Code 501 Not Implemented, HTTP Status Code 502 Bad Gateway, HTTP Status Code 503 Service Unavailable, HTTP Status Code 504 Gateway Timeout, HTTP Status Code 505 HTTP Version Not Supported, HTTP Informational Responses (1xx), HTTP Successful Responses (2xx), HTTP Redirection Messages (3xx), HTTP Client Error Responses (4xx), HTTP Server Error Responses (5xx), HTTP RFC 7230 (Message Syntax and Routing), HTTP RFC 7231 (Semantics and Content), HTTP RFC 7232 (Conditional Requests), HTTP RFC 7233 (Range Requests), HTTP RFC 7234 (Caching), HTTP RFC 7235 (Authentication), HTTP RFC 9110 (HTTP Semantics), HTTP RFC 9111 (Caching), HTTP RFC 9112 (HTTP/1.1), HTTP RFC 9113 (HTTP/2), HTTP RFC 9114 (HTTP/3), HTTP/0.9 Version, HTTP/1.0 Version, HTTP/1.1 Version, HTTP/2 Protocol, HTTP/3 Protocol, HTTP QUIC Transport, HTTP HEADERS Frame (HTTP/2), HTTP SETTINGS Frame (HTTP/2), HTTP GOAWAY Frame (HTTP/2), HTTP RST_STREAM Frame (HTTP/2), HTTP WINDOW_UPDATE Frame (HTTP/2), HTTP DATA Frame (HTTP/2), HTTP PRIORITY Frame (HTTP/2), HTTP PUSH_PROMISE Frame (HTTP/2), HTTP HPACK (Header Compression for HTTP/2), HTTP Huffman Encoding (HPACK), HTTP Indexing Tables (HPACK), HTTP Dynamic Table (HPACK), HTTP QPACK (HTTP/3 Header Compression), HTTP Multiplexing (HTTP/2), HTTP Stream Identifiers (HTTP/2), HTTP Connection Preface (HTTP/2), HTTP ALPN Extension, HTTP Upgrade Mechanism, HTTP OPTIONS * Request, HTTP no-store Directive, HTTP no-cache Directive, HTTP must-revalidate Directive, HTTP proxy-revalidate Directive, HTTP private Directive, HTTP public Directive, HTTP s-maxage Directive, HTTP stale-while-revalidate Directive, HTTP stale-if-error Directive, HTTP Expect Header, HTTP Content-Disposition Header, HTTP Content-Location Header, HTTP Content-MD5 Header, HTTP Content-Security-Policy Header, HTTP Strict-Transport-Security Header, HTTP X-Frame-Options Header, HTTP X-XSS-Protection Header, HTTP Referrer-Policy Header, HTTP Feature-Policy Header, HTTP Permissions-Policy Header, HTTP X-Content-Type-Options Header, HTTP Accept-Patch Header, HTTP Accept-Post Header, HTTP Retry-After Header, HTTP Warning Header, HTTP Date Header, HTTP Server Header, HTTP Allow Header, HTTP Vary Header, HTTP Accept-Ranges Header, HTTP Forwarded Header, HTTP Max-Forwards Header, HTTP Upgrade-Insecure-Requests Header, HTTP Server-Timing Header, HTTP Large-Allocation Header, HTTP Expect-CT Header, HTTP Public-Key-Pins Header, HTTP Public-Key-Pins-Report-Only Header, HTTP Alt-Svc Header, HTTP Early-Data Header, HTTP Service-Worker-Allowed Header, HTTP Clear-Site-Data Header, HTTP Pragma Header, HTTP Proxy-Connection Header, HTTP X-Content-Duration Header, HTTP X-Forwarded-For Header, HTTP X-Forwarded-Host Header, HTTP X-Forwarded-Proto Header, HTTP Front-End-Https Header, HTTP Save-Data Header, HTTP Link Header, HTTP Access-Control-Allow-Origin Header, HTTP Access-Control-Allow-Methods Header, HTTP Access-Control-Allow-Headers Header, HTTP Access-Control-Max-Age Header, HTTP Access-Control-Allow-Credentials Header, HTTP Access-Control-Expose-Headers Header, HTTP Access-Control-Request-Method Header, HTTP Access-Control-Request-Headers Header, HTTP DNT (Do Not Track) Header, HTTP Tk Header (Tracking Status), HTTP Accept-CH Header (Client Hints), HTTP Device-Memory Header (Client Hint), HTTP Viewport-Width Header (Client Hint), HTTP Width Header (Client Hint), HTTP Downlink Header (Client Hint), HTTP Status Code 408 Request Timeout, HTTP Status Code 411 Length Required, HTTP Status Code 412 Precondition Failed, HTTP Status Code 413 Payload Too Large, HTTP Status Code 414 URI Too Long, HTTP Status Code 417 Expectation Failed, HTTP Status Code 426 Upgrade Required, HTTP Status Code 451 Unavailable For Legal Reasons, HTTP Status Code 506 Variant Also Negotiates, HTTP Status Code 507 Insufficient Storage, HTTP Status Code 508 Loop Detected, HTTP Status Code 510 Not Extended, HTTP Status Code 511 Network Authentication Required, HTTP Status Code 103 Early Hints, HTTP Status Code 418 I'm a Teapot, HTTP Status Code 422 Unprocessable Entity, HTTP Status Code 423 Locked, HTTP Status Code 424 Failed Dependency, HTTP Status Code 431 Request Header Fields Too Large, HTTP Status Code 444 No Response (Nginx), HTTP Status Code 495 SSL Certificate Error (Nginx), HTTP Status Code 496 SSL Certificate Required (Nginx), HTTP Status Code 497 HTTP to HTTPS (Nginx), HTTP Status Code 499 Client Closed Request (Nginx), HTTP Status Code 520 Web Server Returned An Unknown Error (Cloudflare), HTTP Status Code 521 Web Server Is Down (Cloudflare), HTTP Status Code 522 Connection Timed Out (Cloudflare), HTTP Status Code 523 Origin Is Unreachable (Cloudflare), HTTP Status Code 524 A Timeout Occurred (Cloudflare), HTTP Status Code 525 SSL Handshake Failed (Cloudflare), HTTP Status Code 526 Invalid SSL Certificate (Cloudflare), HTTP Status Code 527 Railgun Error (Cloudflare), HTTP 'nosniff' directive, HTTP HSTS max-age Directive, HTTP HSTS includeSubDomains Directive, HTTP HSTS preload Directive, HTTP h2c Upgrade Token, HTTP ALPN protocol IDs, HTTP 'trailers' directive in TE, HTTP MIME Type Negotiation, HTTP SPDY (Predecessor to HTTP/2), HTTP Client Hints, HTTP MIME-Version Header, HTTP Character Encoding, HTTP Charset Parameter, HTTP Language Tags, HTTP Quality Values (q=values), HTTP Content Negotiation Mechanisms, HTTP Reason Phrase (obsolete in HTTP/2), HTTP ABNF (Augmented Backus–Naur Form), HTTP BNF Notation used in specs, HTTP Pseudo-headers (HTTP/2), method Pseudo-Header, scheme Pseudo-Header, authority Pseudo-Header, path Pseudo-Header, status Pseudo-Header, HTTP frame fragmentation (HTTP/2), HTTP Flow Control (HTTP/2), HTTP Priority (HTTP/2), HTTP Server Push (HTTP/2) (Deprecated), HTTP OPTIONS * Request (Asterisk Form), HTTP Origin Form, HTTP Authority Form, HTTP Asterisk Form, HTTP Absolute Path, HTTP Request URI, HTTP Request Target, HTTP CRLF (Carriage Return Line Feed), HTTP Whitespace Handling, HTTP Folding (Obsolete in HTTP/1.1) HTTP - Hypertext Transfer Protocol: RFC 9114 HTTP/3,
HTTP/2 in Action by Barry Pollard - https://manning.com/books/http2-in-action - https://learning.oreilly.com/library/view/http-2-in-action/9781617295164
Hypertext Transfer Protocol | HTTP:
Request methods | Request methods
List of HTTP header fields | Header fields:
List of HTTP status codes | Status codes:
Security access control methods:
HTTP/1.0 <small>(1996)</small>
HTTP/1.1 <small>(1997)</small>
HTTP/1.1 <small>(1999)</small>
HTTP/1.1: Message Syntax and Routing <small>(2014)</small>
HTTP/1.1: Semantics and Content <small>(2014)</small>
HTTP/1.1: Conditional Requests <small>(2014)</small>
HTTP/1.1: Range Requests <small>(2014)</small>
HTTP/1.1: Caching <small>(2014)</small>
HTTP/1.1: Authentication <small>(2014)</small>
HTTP/2 <small>(2015)</small>
HTTP/2: HPACK Header Compression <small>(2015)</small>
HTTP/2: Opportunistic Security for HTTP/2 <small>(2017)</small>
HTTP/2: The ORIGIN HTTP/2 Frame <small>(2018)</small>
HTTP/2: Bootstrapping WebSockets with HTTP/2 <small>(2018)</small>
HTTP/2: Using TLS 1.3 with HTTP/2 <small>(2020)</small>
HTTP/3
}} ]] | developer = initially [[CERN; IETF, W3C ]] | introdate = {{Start date and age | 1991 | df=yes}} | newer = }} {{IPstack}} ([[navbar_http - see also navbar_html)
Cloud Monk is Retired ( for now). Buddha with you. © 2025 and Beginningless Time - Present Moment - Three Times: The Buddhas or Fair Use. Disclaimers
SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.