URL with User Authentication Regex for Java
/^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]*)?$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching url with user authentication, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.
Java Implementation
// URL with User Authentication
// ReDoS-safe | RegexVault — Web & Network > URL
import java.util.regex.Pattern;
public class UrlWithUserAuthenticationValidator {
private static final Pattern PATTERN =
Pattern.compile("^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]*)?$");
public static boolean validate(String input) {
return PATTERN.matcher(input).matches();
}
// Example
public static void main(String[] args) {
System.out.println(validate("http://user:password@example.com")); // true
}
}Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
http://user:password@example.com | https://example.com |
https://admin:s3cr3t@api.example.com/ | http://:password@example.com |
http://user@example.com/path | ftp://user:pass@example.com |
https://user%40name:pass%21@example.com:8080 | http://user:pass@ |
http://readonly:@example.com | http://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 Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. 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