Signing HTTP Messages
draft-cavage-http-signatures-06
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Mark Cavage , Manu Sporny | ||
Last updated | 2017-07-17 (Latest revision 2017-01-10) | ||
Replaced by | draft-ietf-httpbis-message-signatures, draft-ietf-httpbis-message-signatures | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
When communicating over the Internet using the HTTP protocol, it can be desirable for a server or client to authenticate the sender of a particular message. It can also be desirable to ensure that the message was not tampered with during transit. This document describes a way for servers and clients to simultaneously add authentication and message integrity to HTTP messages by using a digital signature.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)