HTTP/2

E6319

HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (11)

Statements (55)

Predicate Object
instanceOf Hypertext Transfer Protocol version
application layer protocol
network protocol
backwardsCompatibleWith HTTP/1.1 semantics
canBeUsedOver TLS
cleartext TCP
cleartextUpgradeMechanism HTTP Upgrade header
compatibleWith HTTP URIs
HTTP methods
HTTP semantics
HTTP status codes
defaultPortOverCleartext 80
defaultPortOverTLS 443
definedInRFC HTTP/2 self-linksurface differs
surface form: RFC 7540

RFC 7541
doesNotChange HTTP authentication semantics
HTTP caching semantics
HTTP cookies semantics
URI scheme semantics
follows HTTP/1.1
headerCompressionAlgorithm HPACK
improves web performance
influencedBy SPDY
layer application layer
multiplexingAllows multiple concurrent streams over a single TCP connection
negotiatedVia ALPN
obsoletedBy HTTP/3 (for many deployments)
originatedFrom SPDY
partOf TCP/IP
surface form: Internet protocol suite
publicationYear 2015
reduces header overhead
latency
replaces text-based message framing of HTTP/1.1
securityRecommendation use over TLS
serverPushAllows sending resources before client requests them
standardizedBy Internet Engineering Task Force
surface form: IETF
status Proposed Standard
streamIdentifierType integer
successorTo HTTP/1.1
supportsFeature binary framing
flow control
header compression
multiplexing
persistent connections
request pipelining without head-of-line blocking at HTTP layer
server push
stream prioritization
TLSALPNIdentifier h2
transportProtocol Transmission Control Protocol
surface form: TCP
uses binary framing layer
usesConcept connections
frames
messages
streams
usesHeaderCompressionSpecification HTTP/2 self-linksurface differs
surface form: HPACK

How these facts were elicited

The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.

Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10.

# Requirements
- If you don't know the subject at all, return an empty list.
- If the subject is not a named entity, return an empty list.
- Include at least one triple where predicate is "instanceOf".
- Do not get too wordy.
- Separate several objects into multiple triples with one object.
Input
Subject: HTTP/2
Description of subject: HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.

Referenced by (32)

Full triples — surface form annotated when it differs from this entity's canonical label.

HTTP successorOf HTTP/2
subject surface form: HTTP/3
HTTP/3 successorOf HTTP/2
HTTP/2 definedInRFC HTTP/2 self-linksurface differs
this entity surface form: RFC 7540
HTTP/2 usesHeaderCompressionSpecification HTTP/2 self-linksurface differs
this entity surface form: HPACK
RFC 9114 obsoletes HTTP/2
this entity surface form: RFC 7540
RFC 9114 obsoletes HTTP/2
RFC 9113 title HTTP/2
RFC 9113 specifiesProtocol HTTP/2
RFC 9113 defines HTTP/2
this entity surface form: HTTP/2 framing layer
RFC 9113 obsoletes HTTP/2
this entity surface form: RFC 7540
RFC 9113 definesConcept HTTP/2
this entity surface form: HTTP/2 server push
RFC 9113 definesConcept HTTP/2
this entity surface form: HTTP/2 stream states
RFC 9113 definesConcept HTTP/2
this entity surface form: HTTP/2 graceful shutdown
HTTP/1.1 coexistsWith HTTP/2
Chromium supportsProtocol HTTP/2
AES-GCM usedInProtocol HTTP/2
HPACK usedByProtocol HTTP/2
RFC 7541 relatedTo HTTP/2
RFC 7541 appliesTo HTTP/2
this entity surface form: HTTP/2 intermediaries
SPDY influenced HTTP/2
RFC 9205 relatedTo HTTP/2
RFC 7540 title HTTP/2
this entity surface form: Hypertext Transfer Protocol Version 2 (HTTP/2)
RFC 7540 definesProtocol HTTP/2
RFC 7540 defines HTTP/2
this entity surface form: Hypertext Transfer Protocol Version 2
RFC 7540 workingGroup HTTP/2
this entity surface form: Hypertext Transfer Protocol (httpbis)
nginx supportsProtocol HTTP/2
ALPN (Application-Layer Protocol Negotiation) allowsNegotiationOf HTTP/2
subject surface form: ALPN
IIS supportsProtocol HTTP/2
SNI usedIn HTTP/2