The Secure HyperText Transfer Protocol
RFC 2660
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2021-12-10
|
06 | (System) | Received changes through RFC Editor sync (changed abstract to 'This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which … Received changes through RFC Editor sync (changed abstract to '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.', changed standardization level to Historic) |
2021-12-06
|
06 | Amy Vezza | New status of Historic approved by the IESG https://datatracker.ietf.org/doc/status-change-http-experiments-to-historic/ |
1999-08-01
|
06 | (System) | RFC published |
1999-06-03
|
06 | (System) | IESG has approved the document |
1998-06-26
|
06 | (System) | New version available: draft-ietf-wts-shttp-06.txt |
1998-04-10
|
05 | (System) | New version available: draft-ietf-wts-shttp-05.txt |
1997-03-25
|
04 | (System) | New version available: draft-ietf-wts-shttp-04.txt |
1996-08-01
|
03 | (System) | New version available: draft-ietf-wts-shttp-03.txt |
1996-06-03
|
02 | (System) | New version available: draft-ietf-wts-shttp-02.txt |
1996-02-13
|
01 | (System) | New version available: draft-ietf-wts-shttp-01.txt |