6
Knowledge

HTTP

Application-layer protocol for transferring web resources

Concept

HTTP (Hypertext Transfer Protocol) is an application layer protocol in the Internet protocol suite 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. HTTP is a request–response protocol in the client–server model. A transaction starts with a client submitting a request to the server, the server attempts to satisfy the request and returns a response to the client that describes the disposition of the request and optionally contains a requested resource such as an HTML document or other content. In a common scenario, a web browser acts as the client, and a web server, hosting one or more websites, is the server. A web browser is an example of a user agent (UA). Other types of user agent include the indexing software used by search providers (web crawlers), voice browsers, mobile apps, and other software that accesses, consumes, or displays web content. HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. High-traffic websites often benefit from web cache servers that deliver content on behalf of upstream servers to improve response time. Web browsers cache previously accessed web resources and reuse them, whenever possible, to reduce network traffic. HTTP proxy servers at private network boundaries can facilitate communication for clients without a globally routable address, by relaying messages with external servers. To allow intermediate HTTP nodes (proxy servers, web caches, etc.) to accomplish their functions, some of the HTTP headers (found in HTTP requests/responses) are managed hop-by-hop whereas other HTTP headers are managed end-to-end (managed only by the source client and by the target web server). A web resource is located by a uniform resource locator (URL), using the Uniform Resource Identifier (URI) schemes http and https. URIs are encoded as hyperlinks in HTML documents, so as to form interlinked hypertext documents.

UtopiaYour beings deal 43% more damage.
Epic48331 / 428109

CardsKnowledge

HTTP

Application-layer protocol for transferring web resources

HTTP (Hypertext Transfer Protocol) is an application layer protocol in the Internet protocol suite 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. HTTP is a request–response protocol in the client–server model. A transaction starts with a client submitting a request to the server, the server attempts to satisfy the request and returns a response to the client that describes the disposition of the request and optionally contains a requested resource such as an HTML document or other content. In a common scenario, a web browser acts as the client, and a web server, hosting one or more websites, is the server. A web browser is an example of a user agent (UA). Other types of user agent include the indexing software used by search providers (web crawlers), voice browsers, mobile apps, and other software that accesses, consumes, or displays web content. HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. High-traffic websites often benefit from web cache servers that deliver content on behalf of upstream servers to improve response time. Web browsers cache previously accessed web resources and reuse them, whenever possible, to reduce network traffic. HTTP proxy servers at private network boundaries can facilitate communication for clients without a globally routable address, by relaying messages with external servers. To allow intermediate HTTP nodes (proxy servers, web caches, etc.) to accomplish their functions, some of the HTTP headers (found in HTTP requests/responses) are managed hop-by-hop whereas other HTTP headers are managed end-to-end (managed only by the source client and by the target web server). A web resource is located by a uniform resource locator (URL), using the Uniform Resource Identifier (URI) schemes http and https. URIs are encoded as hyperlinks in HTML documents, so as to form interlinked hypertext documents.

Read the article on Wikipedia

How these stats are calculated

Every value is derived from a measurement of the article, with no manual input. The measurements below were taken on September 6, 2026.

ConceptAlters a rule of the game for as long as it stays in play.

REA

Reach

Article length

91 / 120

RIG

Rigour

Reference density and count

43 / 120

ANC

Anchorage

Age and revision count

368 / 400

CUR

Currency

Recent edit activity and view trend

20 / 30

DIF

Diffusion

Language editions and incoming links

82 / 100

Article size

58 kB

Sources cited

57

Sections

42

Revisions

5,754

Revisions in 90 days

32

Incoming links

3,806

Language editions

90

Views over 12 months

557,508

Created on

October 29, 2001

Wikidata statements

95

Epic — 99.4th percentile of notability

Rarity ranks cards by how famous their subject is: readership, number of languages and incoming links. This tier appears in 4.50% of cards pulled from packs. It says nothing about the card’s power, which is 690 out of 1000 here.

Effect

This card does not fight on its own: it carries a single effect, chosen by its dominant measure.

UtopiaYour beings deal 43% more damage.

Knowledgetype matchups

Strong against

CosmosLand

Weak against

MythPower

The source article

This card maps to the Wikidata item Q8777, present in 90 Wikipedia editions.

Illustration : file on Wikimedia CommonsIETF HTTP Working Group (HTTPbis) licence Public domain. Article text licensed under CC BY-SA 4.0.

Other Knowledge cards