REGEXVAULTv2.0
Web & Network/URL
Verified Safe

URL with User Authentication Regex for JavaScript

/^https?://[a-zA-Z0-9._~!$&'()*+,;=%-]+(?::[a-zA-Z0-9._~!$&'()*+,;=%-]*)?@(?:[a-zA-Z0-9\-]+\.)+[a-zA-Z]{2,63}(?::[1-9][0-9]{0,4})?(?:/[^\s]*)?$/i

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching url with user authentication, ported and verified for JavaScript. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your JavaScript project — whether you're validating in an Express middleware, a Next.js API route, or a client-side form.

Javascript Implementation

Javascript
// URL with User Authentication
// ReDoS-safe | RegexVault — Web & Network > URL

const urlWithUserAuthenticationRegex = /^https?:\/\/[a-zA-Z0-9._~!$&'()*+,;=%-]+(?::[a-zA-Z0-9._~!$&'()*+,;=%-]*)?@(?:[a-zA-Z0-9\-]+\.)+[a-zA-Z]{2,63}(?::[1-9][0-9]{0,4})?(?:\/[^\s]*)?$/i;

function validateUrlWithUserAuthentication(input: string): boolean {
  return urlWithUserAuthenticationRegex.test(input);
}

// Example
console.log(validateUrlWithUserAuthentication("http://user:password@example.com")); // true

Test Cases

Matches (Valid)
Rejects (Invalid)
http://user:password@example.comhttps://example.com
https://admin:s3cr3t@api.example.com/http://:password@example.com
http://user@example.com/pathftp://user:pass@example.com
https://user%40name:pass%21@example.com:8080http://user:pass@
http://readonly:@example.comhttp://user:pass:extra@example.com

When to use this pattern

This pattern is drawn from the Web & Network > URL category and carries a ReDoS-safe certification. That matters for JavaScript developers because especially critical in long-running Node.js event loops where a ReDoS vulnerability can block the entire process. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

The @ character in the username or password must be percent-encoded as %40. Unencoded @ will cause the parser to misidentify the host.

Technical Notes

Embedding credentials in URLs is a significant security risk — they appear in browser history, server logs, and referrer headers. Use Authorization headers instead.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern