Signed HTTP Requests (SHREQ)
draft-rundgren-signed-http-requests-01

Document Type Expired Internet-Draft (individual)
Last updated 2020-03-12 (latest revision 2019-09-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rundgren-signed-http-requests-01.txt

Abstract

The SHREQ specification describes how the JSON Web Signature (JWS) specification combined with the JSON Canonicalization Scheme (JCS), can be utilized to support HTTP based applications needing digitally signed requests. SHREQ is specifically tailored for Web applications using JSON as data interchange format. There is also a SHREQ scheme for HTTP requests that do not have a body ("payload") like GET. SHREQ was designed to be agnostic with respect to REST concepts versus traditional GET/POST schemes.

Authors

Anders Rundgren (anders.rundgren.net@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)