Oops. Previous reply didn't go to the list.
Also: the RFC for URLs seems a little unclear, but I think it says that the
user:password syntax is *not* a part of the standard HTTP URL.
http://www.w3.org/Addressing/rfc1738.txt. On the one hand it says:
3.1. Common Internet Scheme Syntax
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
And on the other:
3.3. HTTP
The HTTP URL scheme is used to designate Internet resources
accessible using HTTP (HyperText Transfer Protocol).
The HTTP protocol is specified elsewhere. This specification only
describes the syntax of HTTP URLs.
An HTTP URL takes the form:
http://<host>:<port>/<path>?<searchpart>
where <host> and <port> are as described in Section 3.1. If :<port>
is omitted, the port defaults to 80. No user name or password is
allowed. <path> is an HTTP selector, and <searchpart> is a query
Anyway, so far as I can tell you have to set the authentication headers by
other means. I implement a URIResolver that makes the http request and sets the
headers on it.
Cheers
Chris
