Skip to main content

API Keys and Privacy
draft-rsalz-httpapi-privacy-00

Document Type Replaced Internet-Draft (httpapi WG)
Expired & archived
Authors Rich Salz , Mike Bishop , Marius Kleidl
Last updated 2024-10-04 (Latest revision 2024-08-26)
Replaced by draft-ietf-httpapi-privacy
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-httpapi-privacy
Consensus boilerplate Unknown
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

Redirecting HTTP requests to HTTPS, a common pattern for human-facing web resources, can be an anti-pattern for authenticated API traffic. This document discusses the pitfalls and makes deployment recommendations for authenticated HTTP APIs. It does not specify a protocol.

Authors

Rich Salz
Mike Bishop
Marius Kleidl

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