The userinfo component is supported according to the URI generic syntax, which FTP URIs follow, but HTTP URIs don't.
See the sadly still not obsolete RFC1738:
http://tools.ietf.org/html/rfc1738#section-3.1
RFC 2616 also says "For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," RFC 2396" and it is frequently documented on the interwebs that HTTP uses the generic URI syntax.
I'm not trying to suggest that the intent of the RFC was to allow <authority> where it says <host> in 3.2.2 but I can see how this wording might be confusing, especially when taken with historically observed UA behaviour.
Comments
HTTP URIs never officially supported this syntax anyway: http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2...
The userinfo component is supported according to the URI generic syntax, which FTP URIs follow, but HTTP URIs don't. See the sadly still not obsolete RFC1738: http://tools.ietf.org/html/rfc1738#section-3.1
RFC 2616 also says "For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," RFC 2396" and it is frequently documented on the interwebs that HTTP uses the generic URI syntax.
I'm not trying to suggest that the intent of the RFC was to allow <authority> where it says <host> in 3.2.2 but I can see how this wording might be confusing, especially when taken with historically observed UA behaviour.