@@ -27,7 +27,7 @@ The `node:url` module provides two APIs for working with URLs: a legacy API that |
27 | 27 | is Node.js specific, and a newer API that implements the same |
28 | 28 | [WHATWG URL Standard][] used by web browsers. |
29 | 29 |
|
30 | | -A comparison between the WHATWG and Legacy APIs is provided below. Above the URL |
| 30 | +A comparison between the WHATWG and legacy APIs is provided below. Above the URL |
31 | 31 | |
32 | 32 | of an object returned by the legacy `url.parse()` are shown. Below it are |
33 | 33 | properties of a WHATWG `URL` object. |
@@ -63,7 +63,7 @@ const myURL = |
63 | 63 | |
64 | 64 | ``` |
65 | 65 |
|
66 | | -Parsing the URL string using the Legacy API: |
| 66 | +Parsing the URL string using the legacy API: |
67 | 67 |
|
68 | 68 | ```mjs |
69 | 69 | import url from 'node:url'; |
@@ -1521,6 +1521,9 @@ The formatting process operates as follows: |
1521 | 1521 | <!-- YAML |
1522 | 1522 | added: v0.1.25 |
1523 | 1523 | changes: |
| 1524 | + - version: REPLACEME |
| 1525 | + pr-url: https://github.com/nodejs/node/pull/44919 |
| 1526 | + description: Documentation-only deprecation. |
1524 | 1527 | - version: |
1525 | 1528 | - v15.13.0 |
1526 | 1529 | - v14.17.0 |
@@ -1540,7 +1543,7 @@ changes: |
1540 | 1543 | when no query string is present. |
1541 | 1544 | --> |
1542 | 1545 |
|
1543 | | -> Stability: 3 - Legacy: Use the WHATWG URL API instead. |
| 1546 | +> Stability: 0 - Deprecated: Use the WHATWG URL API instead. |
1544 | 1547 |
|
1545 | 1548 | * `urlString` {string} The URL string to parse. |
1546 | 1549 | * `parseQueryString` {boolean} If `true`, the `query` property will always |
@@ -1562,16 +1565,9 @@ A `URIError` is thrown if the `auth` property is present but cannot be decoded. |
1562 | 1565 |
|
1563 | 1566 | `url.parse()` uses a lenient, non-standard algorithm for parsing URL |
1564 | 1567 | strings. It is prone to security issues such as [host name spoofing][] |
1565 | | -and incorrect handling of usernames and passwords. |
1566 | | - |
1567 | | -`url.parse()` is an exception to most of the legacy APIs. Despite its security |
1568 | | -concerns, it is legacy and not deprecated because it is: |
1569 | | - |
1570 | | -* Faster than the alternative WHATWG `URL` parser. |
1571 | | -* Easier to use with regards to relative URLs than the alternative WHATWG `URL` API. |
1572 | | -* Widely relied upon within the npm ecosystem. |
1573 | | - |
1574 | | -Use with caution. |
| 1568 | +and incorrect handling of usernames and passwords. Do not use with untrusted |
| 1569 | +input. CVEs are not issued for `url.parse()` vulnerabilities. Use the |
| 1570 | +[WHATWG URL][] API instead. |
1575 | 1571 |
|
1576 | 1572 | ### `url.resolve(from, to)` |
1577 | 1573 |
|
|