Document that basic authorization now kinda works.

svn path=/head/; revision=62966

lib/libfetch/fetch.3

@@ -379,12 +379,25 @@ Invalid URL
 The accompanying error message includes a protocol-specific error code
 and message, e.g. "File is not available (404 Not Found)"
 .Sh ENVIRONMENT
-The FTP and HTTP related functions use the
-.Ev HTTP_PROXY
-and
-.Ev FTP_PROXY
-environment variables, respectively, as the address of a proxy server
-to use for transferring files.
+.Bl -tag -width HTTP_PROXY_AUTH
+.It Ev FTP_PROXY
+host name of the FTP proxy to use, optionally followed by a port
+number separated from the host name by a colon.
+.\" .It Ev HTTP_AUTH
+.\" Specifies HTTP authorization parameters.
+.It Ev HTTP_PROXY
+host name of the HTTP proxy to use, optionally followed by a port
+number separated from the host name by a colon.
+If no port number is specified, the default is 3128.
+.It Ev HTTP_PROXY_AUTH
+Specifies authorization parameters for the HTTP proxy as a
+colon-separated list.
+The first and second item are the authorization scheme and realm
+respectively; further items are scheme-dependent.
+Currently, only basic authorization is supported.
+Basic authorization requires two parameters: the user's login name and
+password, in that order.
+.El
 .Sh SEE ALSO
 .Xr fetch 1 ,
 .Xr ftpio 3 ,
@@ -454,18 +467,9 @@ environment variables as appropriate.
 There is also no way to stop the
 FTP and HTTP functions from trying to use a proxy if these variables
 are set.
-.Pp
-HTTP authentication doesn't work.
-I'm not sure that's a bug in my
-code; as far as I can determine,
-.Nm libfetch
-handles HTTP/1.1 basic authentication correctly as outlined in
-RFC2068, but I haven't been able to find an HTTP server that honors
-the Authentication: header field.
-Also,
 .Nm libfetch
 does not attempt to interpret and respond to authentication requests
-from the HTTP server.
+from the HTTP server or proxy (code 401 and 407 respectively).
 .Pp
 No attempt is made to encode spaces etc. within URLs.
 Spaces in the