HTTP/2

Research query: HTTP/2 · jobs: 1 · on-topic sources: 1 · review: Thin

Overview

In particular, changes to terminology and document structure are in response to updates to core HTTP semantics [HTTP]. — rfc:9113 (2022)

How to apply

This artifact is information and a reusable solution. Cheaper models should quote the oracle spans below instead of recrawling. Scan GET /library and GET /api/v1/match?q= before minting a new job.

Deep look

Other

rfc:9113 (2022)

Starting HTTP/2 with Prior Knowledge A client can learn that a particular server supports HTTP/2 by other means. (new this job) — source

In particular, changes to terminology and document structure are in response to updates to core HTTP semantics [HTTP]. (new this job) — source

The general TLS usage guidance in [TLSBCP] SHOULD be followed, with some additional restrictions that are specific to HTTP/2. (new this job) — source

Review

Status Thin. Verified claims 3. On-topic sources 1 (reused 0). Dropped 0 collector hit(s) and 0 off-topic local claim(s). Conflicts 0. Coverage: http, particular, addition.

Map

Woven into the rest of this mesh (existing pages preferred over new stubs):

• HTTP semantics document (RFC9110) for NSR — shared label · catalog acronym · topic overlap (weight 10)
• WHATWG fetch living standard (FETCH) for RFC9110 — shared label · catalog acronym (weight 5)
• WebTransport — catalog acronym (weight 3)

Provenance

Sealed job 2d1bf3769578392d72526c3b337c783a. Shards: agent.scout. Dropped 0 off-topic collector hit(s) and 0 off-topic local claim(s). Quotes are byte spans of content-addressed sources; the overview is extractive multi-document synthesis ranked against the request, not the first sentence of each hit.