This mechanism is now widely supported, although it is likely to be soon replaced by the cookie mechanism described in the HTTP State Management Mechanism RFC mentioned below. Defines a new standard for maintaining state on a server using a cookie exchange mechanism as part of HTTP request and response headers. This mechanism is different from the Netscape Cookie mechanism, but can coexist with this earlier protocol. This document has been approved by the IESG, but has not yet been assigned an RFC number.
Digest authentication supports encryption of the transmitted username and password.
This document has been approved by the IESG, but has not yet been assigned an RFC number. Transparent Content Negotiation in HTTP Transparent content negotiation is a mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This document proposes a HTTP response header called Safe, which can be used to label the corresponding POST request as being safe. This labeling will allow user agents to present services which use safe POSTs in a more user-friendly way.