HTTP in the context of Hyperlink


HTTP in the context of Hyperlink

HTTP Study page number 1 of 1

Play TriviaQuestions Online!

or

Skip to study material about HTTP in the context of "Hyperlink"


⭐ Core Definition: HTTP

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.

↓ Menu
HINT:

In this Dossier

HTTP in the context of World Wide Web

The World Wide Web (also known as WWW, W3, or simply the Web) is an information system that enables content sharing over the Internet through user-friendly ways meant to appeal to users beyond IT specialists and hobbyists. It allows documents and other web resources to be accessed over the Internet according to specific rules of the Hypertext Transfer Protocol (HTTP).

The Web was invented by English computer scientist Tim Berners-Lee while at CERN in 1989 and opened to the public in 1993. It was conceived as a "universal linked information system". Documents and other media content are made available to the network through web servers and can be accessed by programs such as web browsers. Servers and resources on the World Wide Web are identified and located through a character string called uniform resource locator (URL).

View the full Wikipedia page for World Wide Web
↑ Return to Menu

HTTP in the context of Tim Berners-Lee

Sir Timothy John Berners-Lee (born 8 June 1955), also known as TimBL, is an English computer scientist best known as the inventor of the World Wide Web, HTML, the URL system, and HTTP. He is a professorial research fellow at the University of Oxford and a professor emeritus at the Massachusetts Institute of Technology (MIT).

Berners-Lee proposed an information management system on 12 March 1989 and implemented the first successful communication between a Hypertext Transfer Protocol (HTTP) client and server via the Internet in mid-November. He devised and implemented the first Web browser and Web server and helped foster the Web's subsequent development. He is the founder and emeritus director of the World Wide Web Consortium (W3C), which oversees the continued development of the Web. He co-founded (with Rosemary Leith) the World Wide Web Foundation. In 2009, he was elected Foreign Associate of the National Academy of Sciences.

View the full Wikipedia page for Tim Berners-Lee
↑ Return to Menu

HTTP in the context of BitTorrent

BitTorrent is a communication protocol for peer-to-peer file sharing (P2P), which enables users to distribute data and electronic files over the Internet in a decentralized manner. The act of downloading and uploading data via BitTorrent is also labeled "torrenting". The protocol is developed and maintained by Rainberry, Inc., and was first released in 2001.

To send or receive files, users use a BitTorrent client on their Internet-connected computer, which are available for a variety of computing platforms and operating systems, including an official client. BitTorrent trackers provide a list of files available for transfer and allow the client to find peer users, known as "seeds", who may transfer the files. BitTorrent downloading is considered to be faster than HTTP ("direct downloading") and FTP due to the lack of a central server that could limit bandwidth.

View the full Wikipedia page for BitTorrent
↑ Return to Menu

HTTP in the context of Session Initiation Protocol

The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, modifying, and terminating communication sessions that involve multimedia elements such as voice, video, and messaging. It operates at the application layer of the Internet protocol suite and is widely used in Internet telephony, private IP-based telephone systems, and mobile communication over LTE networks through VoLTE.

SIP is a text-based protocol modeled on the structure of HTTP and SMTP, enabling interoperability and integration with other Internet applications. It provides mechanisms for user location, session setup, and session management, making it a foundational component of modern IP multimedia systems.

View the full Wikipedia page for Session Initiation Protocol
↑ Return to Menu

HTTP in the context of Request-response

In computer science, request–response or request–reply is one of the basic methods computers use to communicate with each other in a network, in which the first computer sends a request for some data and the second responds to the request. More specifically, it is a message exchange pattern in which a requestor sends a request message to a replier system, which receives and processes the request, ultimately returning a message in response. It is analogous to a telephone call, in which the caller must wait for the recipient to pick up before anything can be discussed. This is a simple but powerful messaging pattern which allows two applications to have a two-way conversation with one another over a channel; it is especially common in client–server architectures.

Request–response pattern can be implemented synchronously (such as web service calls over HTTP) or asynchronously.

View the full Wikipedia page for Request-response
↑ Return to Menu

HTTP in the context of Web service

A web service (WS) is either:

  • a service offered by an electronic device to another electronic device, communicating with each other via the Internet, or
  • a server running on a computer device, listening for requests at a particular port over a network, serving web documents (HTML, JSON, XML, images).

In a web service, a web technology such as HTTP is used for transferring machine-readable file formats such as XML and JSON.

View the full Wikipedia page for Web service
↑ Return to Menu

HTTP in the context of XMLHttpRequest

XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

View the full Wikipedia page for XMLHttpRequest
↑ Return to Menu

HTTP in the context of Gopher (protocol)

The Gopher protocol (/ˈɡfər/ ) is a communication protocol designed for distributing, searching, and retrieving documents in Internet Protocol networks. The design of the Gopher protocol and user interface is menu-driven, and presented an alternative to the World Wide Web in its early stages, but ultimately fell into disfavor, yielding to Hypertext Transfer Protocol (HTTP). The Gopher ecosystem is often regarded as the effective predecessor of the World Wide Web.

View the full Wikipedia page for Gopher (protocol)
↑ Return to Menu

HTTP in the context of PHP

PHP is a general-purpose scripting language geared towards web development. It was created by Danish-Canadian programmer Rasmus Lerdorf in 1993 and released in 1995. The PHP reference implementation is now produced by the PHP Group. PHP was originally an abbreviation of Personal Home Page, but it now stands for the recursive backronym PHP: Hypertext Preprocessor.

PHP code is usually processed on a web server by a PHP interpreter implemented as a module, a daemon or a Common Gateway Interface (CGI) executable. On a web server, the result of the interpreted and executed PHP code—which may be any type of data, such as generated HTML or binary image data—can form the whole or part of an HTTP response. Various web template systems, web content management systems, and web frameworks exist that can be employed to orchestrate or facilitate the generation of that response. Additionally, PHP can be used for programming tasks outside the web context, though non-web uses are rare. PHP code can also be directly executed from the command line.

View the full Wikipedia page for PHP
↑ Return to Menu

HTTP in the context of Universal Plug and Play

UPnP (originally Universal Plug and Play) is a set of Internet Protocol-based networking protocols that permits networked devices, such as personal computers, printers, Internet gateways, Wi-Fi access points and mobile devices, to seamlessly discover each other's presence on the network and establish functional network services. UPnP is intended primarily for residential networks without enterprise-class devices. Officially, only the abbrevations UPnP and UPnP+ are trademarked.

UPnP assumes the network runs IP, and then uses HTTP on top of IP to provide device/service description, actions, data transfer and event notification. Device search requests and advertisements are supported by running HTTP on top of UDP (port 1900) using multicast (known as HTTPMU). Responses to search requests are also sent over UDP, but are instead sent using unicast (known as HTTPU).

View the full Wikipedia page for Universal Plug and Play
↑ Return to Menu

HTTP in the context of Gateway (telecommunications)

A gateway is a piece of networking hardware or software used in telecommunications networks that allows data to flow from one discrete network to another. Gateways are distinct from routers or switches in that they communicate using more than one protocol to connect multiple networks and can operate at any of the seven layers of the OSI model.

The term gateway can also loosely refer to a computer or computer program configured to perform the tasks of a gateway, such as a default gateway or router, and in the case of HTTP, gateway is also often used as a synonym for reverse proxy. It can also refer to a device installed in homes that combines router and modem functionality into one device, used by ISPs, also called a residential gateway.

View the full Wikipedia page for Gateway (telecommunications)
↑ Return to Menu

HTTP in the context of HTTPS

Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It uses encryption for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL.

The principal motivations for HTTPS are authentication of the accessed website and protection of the privacy and integrity of the exchanged data while it is in transit. It protects against man-in-the-middle attacks, and the bidirectional block cipher encryption of communications between a client and server protects the communications against eavesdropping and tampering. The authentication aspect of HTTPS requires a trusted third party to sign server-side digital certificates. This was historically an expensive operation, which meant fully authenticated HTTPS connections were usually found only on secured payment transaction services and other secured corporate information systems on the World Wide Web. In 2016, a campaign by the Electronic Frontier Foundation with the support of web browser developers led to the protocol becoming more prevalent. HTTPS has since 2018 been used more often by web users than non-secure HTTP, primarily to protect page authenticity on all types of websites, secure accounts, and keep user communications, identity, and web browsing private.

View the full Wikipedia page for HTTPS
↑ Return to Menu

HTTP in the context of List of HTTP status codes

This article lists standard and notable non-standard HTTP response status codes. Standardized codes are defined by IETF as documented in Request for Comments (RFC) publications and maintained by the IANA. Other, non-standard values are used by various servers. The descriptive text after the numeric code – the reason phrase – is shown here with typical value, but in practice, can be different or omitted.

View the full Wikipedia page for List of HTTP status codes
↑ Return to Menu

HTTP in the context of File hosting service

A file-hosting service, also known as cloud-storage service, online file-storage provider, or cyberlocker, is an internet hosting service specifically designed to host user files. These services allow users to upload files that can be accessed over the internet after providing a username and password or other authentication. Typically, file hosting services allow HTTP access, and in some cases, FTP access. Other related services include content-displaying hosting services (i.e. video and image), virtual storage, and remote backup solutions.

View the full Wikipedia page for File hosting service
↑ Return to Menu

HTTP in the context of WWW

The World Wide Web (also known as WWW, W3, or simply the Web) is an information system that enables content sharing over the Internet using a graphical user interface. It facilitates access to documents and other web resources according to specific rules of the Hypertext Transfer Protocol (HTTP).

The Web was invented by English computer scientist Tim Berners-Lee while at CERN in 1989 and opened to the public in 1993. It was conceived as a "universal linked information system". Documents and other media content are made available to the network through web servers and can be accessed by programs such as web browsers. Servers and resources on the World Wide Web are identified and located through a character string called uniform resource locator (URL).

View the full Wikipedia page for WWW
↑ Return to Menu

HTTP in the context of Content negotiation

In computing, content negotiation refers to mechanisms defined as a part of HTTP that make it possible to serve different versions of a document (or more generally, representations of a resource) at the same URI, so that user agents can specify which version fits their capabilities the best. One classical use of this mechanism is to serve an image in GIF or PNG format, so that a browser that cannot display PNG images (e.g. MS Internet Explorer 4) will be served the GIF version.

A resource may be available in several different representations; for example, it might be available in different languages or different media types. One way of selecting the most appropriate choice is to give the user an index page and let them select the most appropriate choice; however it is often possible to automate the choice based on some selection criteria.

View the full Wikipedia page for Content negotiation
↑ Return to Menu

HTTP in the context of MIME type

In information and communications technology, a media type, content type or MIME type is a two-part identifier for file formats and content formats. Their purpose is comparable to filename extensions and uniform type identifiers, in that they identify the intended data format. They are mainly used by technologies underpinning the Internet, and also used on Linux desktop systems.

The Internet Assigned Numbers Authority (IANA) is the official authority for the standardization and publication of these classifications. Media types were originally defined in Request for Comments RFC 2045 (MIME) Part One: Format of Internet Message Bodies (Nov 1996) in November 1996 as a part of the MIME (Multipurpose Internet Mail Extensions) specification, for denoting type of email message content and attachments; hence the original name, MIME type. Media types are also used by other internet protocols such as HTTP, document file formats such as HTML, and the XDG specifications implemented by Linux desktop environments, for similar purposes.

View the full Wikipedia page for MIME type
↑ Return to Menu