Документ взят из кэша поисковой машины. Адрес оригинального документа : http://old.master.cmc.msu.ru/rfc/Classified/www/http/comments.txt Дата изменения: Wed Mar 5 17:52:10 1997 Дата индексирования: Tue Oct 2 16:08:22 2012 Кодировка:

RFC 2109
HTTP State Management Mechanism - Proposed Standard RFC 2109

This document specifies a way to create a stateful session with HTTP requests and responses.
It describes two new headers, Cookie and Set-Cookie, which carry state information between
participating origin servers and user agents. The method described here differs from
Netscape's Cookie proposal, but it can interoperate with HTTP/1.0 user agents that use
Netscape's method. (See the HISTORICAL section.)

RFC 2069
Digest Access Authentication - Proposed Standard RFC 2069

The protocol referred to as "HTTP/1.0" includes the specification for a Basic Access
Authentication scheme. This scheme is not considered to be a secure method of user
authentication, as the user name and password are passed over the network as clear text. A
specification for a different authentication scheme is needed to address this severe limitation.
This document provides specification for such a scheme, referred to as "Digest Access
Authentication". Like Basic, Digest access authentication verifies that both parties to a
communication know a shared secret (a password); unlike Basic, this verification can be done
without sending the password in the clear, which is Basic's biggest weakness. As with most
other authentication protocols, the greatest sources of risks are usually found not in the core
protocol itself but in policies and procedures surrounding its use.

RFC 2068
HTTP/1.1 - Proposed Standard RFC 2068

The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed,
collaborative, hypermedia information systems. It is a generic, stateless, object-oriented
protocol which can be used for many tasks, such as name servers and distributed object
management systems, through extension of its request methods.A feature of HTTP is the
typing and negotiation of data representation, allowing systems to be built independently of
the data being transferred. HTTP has been in use by the World-Wide Web global information
initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1". You
can also have a look at the HTTP archives for previous versions of this document.

RFC 1945
HTTP/1.0 - Informational RFC 1945

The HTTP/1.0 specification is available as an Informational RFC 1945. No standards track
activity will occur with HTTP/1.0. The authors are Tim Berners-Lee, Roy T. Fielding, and
Henrik Frystyk Nielsen on behalf of the IETF HTTP working group. You can also have a look
at the HTTP archives for previous versions of this document.

HTTP/1.0 is the version deployed by most existing Web applications yet RFC 1945 does not
specify an Internet standard of any kind. As HTTP/1.0 has serious problems regarding
scalability and performance - some of these are explained in various HTTP Performance
papers - no new HTTP application should be based on this specification but instead on the
new HTTP/1.1 specification.

RFC 1738
URLs are specified by RFC 1738