Skip to content

doc: provide alternative to url.parse() using WHATWG URL #59736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
+19 −1
Closed

doc: provide alternative to url.parse() using WHATWG URL #59736

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
adead68
doc: provide alternative to `url.parse()` using WHATWG URL
styfle Sep 2, 2025
2d9d1af
doc: mention reverse proxy and include simple example
styfle Sep 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: provide alternative to url.parse() using WHATWG URL
  • Loading branch information
@styfle
styfle committed Sep 2, 2025
commit adead686a3257c498bdab5012a75425bcb3f2fd9
10 changes: 9 additions & 1 deletion doc/api/url.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1847,7 +1847,15 @@ A `URIError` is thrown if the `auth` property is present but cannot be decoded.
strings. It is prone to security issues such as [host name spoofing][]
and incorrect handling of usernames and passwords. Do not use with untrusted
input. CVEs are not issued for `url.parse()` vulnerabilities. Use the
[WHATWG URL][] API instead.
[WHATWG URL][] API instead, for example:

```js
function getURL(req) {
const proto = req.headers['x-forwarded-proto'] || 'https';
const host = req.headers['x-forwarded-host'] || req.headers.host || 'example.com';
return new URL(req.url || '/', `${proto}://${host}`);
}
```

### `url.resolve(from, to)`

Expand Down
Loading