HTTP Signatures describes a method of creating, encoding and verifying a signature within an HTTP request. This spec can be used for a variety of applications, both involving OAuth as well as outside of OAuth. This work is taking place in the HTTPBIS working group at the IETF.
The latest version of the in-progress specification can be found at:
In OAuth, HTTP Signatures can be used as a proof of possession mechanism to add additional protection to Bearer tokens. Other forms of proof of possession in OAuth include:
HTTP Signatures is referenced by FAPI as one method of signing HTTP messages.
Historical note: This draft is an evolution of the earlier individual draft "Signing HTTP Messages" by Cavage. The Cavage draft was never adopted by a working group and expired in 2018. For a brief period of time, some of this work had been picked up by the "Digital Verification Community Group" and later moved into the "Credentials Community Group" at the W3C. The CCG version of the draft was redirected to the IETF draft in the [HTTPBIS working group](https://datatracker.ietf.org/doc/draft-ietf-httpbis-message-signatures/) where development of the draft has continued.