From 81c1735809f55a876b8a821a7b9646304afca675 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Fri, 15 Sep 2000 04:12:56 +0000 Subject: [PATCH] Add item to the list of limitations that points out the lack of support for authenticated proxies. This is noted elsewhere, but this makes it easier to find. Fix typo where it was already mentioned. This closes SourceForge bug #110619. --- Doc/lib/liburllib.tex | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Doc/lib/liburllib.tex b/Doc/lib/liburllib.tex index 1cdfafdc5d..3901a9cf76 100644 --- a/Doc/lib/liburllib.tex +++ b/Doc/lib/liburllib.tex @@ -63,7 +63,7 @@ must in standard \file{application/x-www-form-urlencoded} format; see the \function{urlencode()} function below. The \function{urlopen()} function works transparently with proxies -whicd do not require authentication. In a \UNIX{} or Windows +which do not require authentication. In a \UNIX{} or Windows environment, set the \envvar{http_proxy}, \envvar{ftp_proxy} or \envvar{gopher_proxy} environment variables to a URL that identifies the proxy server before starting the Python interpreter. For example @@ -261,6 +261,10 @@ protocol, type information is encoded in the URL; there is currently no easy way to extract it. If the returned data is HTML, you can use the module \refmodule{htmllib}\refstmodindex{htmllib} to parse it. +\item +This module does not support the use of proxies which require +authentication. This may be implemented in the future. + \item Although the \module{urllib} module contains (undocumented) routines to parse and unparse URL strings, the recommended interface for URL -- 2.40.0