I would say no, not the way you doing it according to this snippet I found on the interweb:
Of the predefined schemes listed (http, ftp, news, nntp, telnet, gopher
wais, mailto, file, prospero), only ftp: and telnet: URLs use the login
form, which allows for a password. http: uses only hostport.
So the syntax in the spec doesn't allow for what you want. See:
http://www.w3.org/hypertext/WWW/Address ... ssing.html
http://www.w3.org/hypertext/WWW/Addressing/rfc1738.txt
In the HTTP 1.0 protocol (with Basic Authentication) the user name and
password are not sent as part of the URL on the GET line, but rather in a
"Authorization:" header sent in response to a "WWW-Authenticate:" header
sent when a prior request failed.
The HTTP spec also agrees that the http: URL has the form:
http_URL = "
http:" "//" host [ ":" port ] [ abs_path ]
See:
http://www.w3.org/hypertext/WWW/Protocols/Overview.html
http://www.w3.org/hypertext/WWW/Protoco ... /spec.html
While you could write a custom client that would do a GET with a username
and password by sending the right headers with the request, trying to use
the generic URL syntax to do this is not going to work.
(There are other authorization schemes in the works besides Basic, but it
is still widely used.)
(Also note: While the spec for telnet URLs allows for a username and
password, you are unlikely to find this implemented.)