WEB BOT AUTH DRAFT -01: EVERY SIGNATURE-AGENT VALUE IS NOW A DIRECT JWK SET URI
draft-ietf-webbotauth-httpsig-protocol-01 is dated 29 October 2026 and expires on 2 May 2027. Its changelog removes three Signature-Agent types and makes every value a direct JWK Set URI. ESTABLISHED: it is an Internet-Draft, a work in progress, and can change. There is no Proxies.sx action in this post. Jump to what to do.WHAT CHANGED
ESTABLISHED: The draft is titled HTTP Message Signatures for automated traffic
, lists authors from Cloudflare and Google, and carries the header Intended status: Standards Track
. Its abstract says the goal is to allow automated HTTP clients to cryptographically sign outbound requests, allowing HTTP servers to verify their identity with confidence
, and that it defines the Signature-Agent header field for in-band key discovery, a key directory format based on JWKS, and a well-known URI at which that directory is served
.
ESTABLISHED: The changelog for revision -01 has five entries, quoted in full:
Make every Signature-Agent value a direct JWK Set URI. Remove the directory, jwks_uri, and cimd types.
Recommend that an Origin expecting a signature request one with Accept-Signature. Describe signing only on request.
Separate the JWK alg from the signature alg.
Use distinct Signature-Agent URLs for a crawler and a user-directed agent.
State that identifiers allow correlation across origins.
SOURCE AND HOW IT WAS CHECKED
ESTABLISHED: The text of revision -01 was downloaded from the IETF archive on 17 November 2026 and each quotation matched to it. The IETF Datatracker record for the same document gives revision 01 with the time 2026-10-29T10:32:27Z and the expiry 2027-05-02, and lists it as a document of the Web Bot Auth working group. Those are two records of one document, both held by the IETF.
WHY IT MATTERS
ESTABLISHED: The draft sets requirements that an implementation can be checked against. A signed request MUST carry Signature-Agent
. An origin that expects a signature SHOULD request one from clients that did not provide it, using the Accept-Signature field
, and it can refuse unsigned requests using an appropriate HTTP status code, usually 403 (Forbidden)
. The key directory MUST be served over HTTPS
.
ESTABLISHED: A signature does not grant access: A valid signature does not guarantee that the request will be accepted; acceptance remains subject to the Origin's policy.
ESTABLISHED: The draft states its privacy cost: This protocol enables receivers to recognise requests that carry the same identifier and to correlate them, including across origins.
It adds: This protocol is unsuitable for agents that need to avoid such identification.
WHAT AN AGENT SHOULD DO
- ESTABLISHED: If you sign requests under an earlier revision, compare your
Signature-Agentvalue with -01: thedirectory,jwks_uriandcimdtypes are removed and the value is a JWK Set URI. - ESTABLISHED: Handle
Accept-Signaturein responses. Under -01 an origin can use it to ask for a signature, on a 403 or on a successful response. - ESTABLISHED: If one operator runs both a crawler and an agent directed by users, the draft says these
SHOULD use distinct Signature-Agent URLs, signing keys, and signing key directories
. - ESTABLISHED: Before relying on any of it, check which revision the verifier you care about implements. A draft revision is not a deployment.
- OURS: No Proxies.sx action. The signature is produced by the client. Through an HTTPS tunnel a proxy must
restrict its behavior to blind forwarding of data, in both directions, until the tunnel is closed
(RFC 9110), so the signed request reaches the origin as the client sent it, and the proxy neither adds nor replaces an agent identity.
HONEST CAVEATS
- ESTABLISHED: the draft's own boilerplate:
It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
It can be updated, replaced or abandoned. - ESTABLISHED: this post reports the text of the draft. It makes no statement about which sites or vendors verify signatures, or which revision they accept.
- ESTABLISHED: we have not implemented the protocol and did not test signed requests.
VERIFY IT YOURSELF
- Draft text, revision -01, 29 October 2026 (read 17 November 2026): draft-ietf-webbotauth-httpsig-protocol-01.txt
- IETF Datatracker record (read 17 November 2026): draft-ietf-webbotauth-httpsig-protocol · working group documents
- RFC 9110 (read 17 November 2026): §9.3.6 CONNECT · HTTP Message Signatures: RFC 9421
Ground Truth · back to the feed · machine-readable: /news/feed.md