iBet uBet web content aggregator. Adding the entire web to your favor.
iBet uBet web content aggregator. Adding the entire web to your favor.



Link to original content: https://doi.org/10.17487/RFC2660
Information on RFC 2660 » RFC Editor

RFC 2660

The Secure HyperText Transfer Protocol, August 1999

File formats:
icon for text file icon for PDF icon for HTML
Status:
HISTORIC (changed from EXPERIMENTAL)
Authors:
E. Rescorla
A. Schiffman
Stream:
IETF
Source:
wts (sec)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC2660

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 2660


Abstract

This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) provides independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin.

The protocol emphasizes maximum flexibility in choice of key management mechanisms, security policies and cryptographic algorithms by supporting option negotiation between parties for each transaction.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search