Update the text to use direct RFC references (to automagically pick up URLs

to those specs). Fix the PEP: header at top, after Barry's renumbering.
This commit is contained in:
Greg Stein 2001-08-21 08:22:47 +00:00
parent 05a939622a
commit 919d69018d
1 changed files with 13 additions and 16 deletions

View File

@ -1,4 +1,4 @@
PEP: 267 PEP: 268
Title: Extended HTTP functionality and WebDAV Title: Extended HTTP functionality and WebDAV
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
@ -22,13 +22,14 @@ Rationale
Python has been quite popular as a result of its "batteries Python has been quite popular as a result of its "batteries
included" positioning. One of the most heavily used protocols, included" positioning. One of the most heavily used protocols,
HTTP [2], has been included with Python for years (httplib). However, HTTP (see RFC 2616), has been included with Python for years
this support has not kept up with the full needs and requirements (httplib). However, this support has not kept up with the full
of many HTTP-based applications and systems. In addition, new needs and requirements of many HTTP-based applications and
protocols based on HTTP, such as WebDAV and XML-RPC, are becoming systems. In addition, new protocols based on HTTP, such as WebDAV
useful and are seeing increasing usage. Supplying this and XML-RPC, are becoming useful and are seeing increasing
functionality meets Python's "batteries included" role and also usage. Supplying this functionality meets Python's "batteries
keeps Python at the leading edge of new technologies. included" role and also keeps Python at the leading edge of new
technologies.
While authentication and proxy support are two very notable While authentication and proxy support are two very notable
features missing from Python's core HTTP processing, they are features missing from Python's core HTTP processing, they are
@ -69,10 +70,10 @@ HTTP Authentication
"authenticator" objects, allowing multiple connections to share "authenticator" objects, allowing multiple connections to share
authenticators. The use of a separate object allows for a long authenticators. The use of a separate object allows for a long
term connection to an authentication system (e.g. LDAP). An term connection to an authentication system (e.g. LDAP). An
authenticator for the Basic mechanism [3] will be provided. Digest authenticator for the Basic mechanism (see RFC 2617) will be
would be great, but we need to find some code for it (or a provided. Digest would be great, but we need to find some code for
motivated developer). User-supplied authenticator subclasses can it (or a motivated developer). User-supplied authenticator
be registered and used by the connections. subclasses can be registered and used by the connections.
A "credentials" object is also associated with the mixin, and A "credentials" object is also associated with the mixin, and
stores the credentials (e.g. username and password) needed by the stores the credentials (e.g. username and password) needed by the
@ -135,10 +136,6 @@ References
[1] http://www.webdav.org/ [1] http://www.webdav.org/
[2] http://asg.web.cmu.edu/rfc/rfc2616.html
[3] http://asg.web.cmu.edu/rfc/rfc2617.html
Copyright Copyright