lukechilds/node - node - Gitea: Git with a cup of tea

Branch: v0.10.10-release

isaacs 5dc51d4e21 url: Properly parse certain oddly formed urls In cases where there are multiple @-chars in a url, Node currently parses the hostname and auth sections differently than web browsers. This part of the bug is serious, and should be landed in v0.10, and also ported to v0.8, and releases made as soon as possible. The less serious issue is that there are many other sorts of malformed urls which Node either accepts when it should reject, or interprets differently than web browsers. For example, `http://a.comfoo` is interpreted by Node like `http://a.com/foo` when web browsers treat this as `http://a.com%3Bfoo/`. In general, only the `hostEndingChars` should be the characters that delimit the host portion of the URL. Most of the current `nonHostChars` that appear in the hostname should be escaped, but some of them (such as `;` and `%` when it does not introduce a hex pair) should raise an error. We need to have a broader discussion about whether it's best to throw in these cases, and potentially break extant programs, or return an object that has every field set to `null` so that any attempt to read the hostname/auth/etc. will appear to be empty.		12 years ago
..
addons	test: modify async native test.js to test for #4820	12 years ago
disabled	Merge remote-tracking branch 'ry/v0.8' into master	12 years ago
fixtures	debugger: breakpoints in scripts not loaded yet	12 years ago
gc	test: use the debug build of node-weak when necessary	13 years ago
internet	DNS: Support NAPTR queries	12 years ago
message	process: separate nextTick domain logic	12 years ago
pummel	test: fix pummel/test-net-many-clients.js	12 years ago
simple	url: Properly parse certain oddly formed urls	12 years ago
common.js	test: optionally set common.PORT via env variable	12 years ago