joyent/node — comment on commit 307f39ce9ed8f4d3de06f63cd1855157be2db82f
File: lib/url.js line 45
By dscape:

I'm kind of lost in RFC land here. I suppose according to the RFC cited in this file this is the correct behavior for chars that need to be encoded?

Personally I was reading [RFC1738] which has a different take on this:
```
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:

//:@:/

Some or all of the parts ":@", ":",
":", and "/" may be excluded. The scheme specific
data start with a double slash "//" to indicate that it complies with
the common Internet scheme syntax. The different components obey the
following rules:

user
An optional user name. Some schemes (e.g., ftp) allow the
specification of a user name.

password
An optional password. If present, it follows the user
name separated from it by a colon.

The user name (and password), if present, are followed by a
commercial at-sign "@". Within the user and password field, any ":",
"@", or "/" must be encoded.
```

Would like to clarify if I should / or shoudn't encode `?` in auth?

[RFC1738]: http://www.ietf.org/rfc/rfc1738.txt