URL with User Authentication Regex for PHP
/^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 PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.
Php Implementation
<?php
// URL with User Authentication
// ReDoS-safe | RegexVault — Web & Network > URL
define('URL_WITH_USER_AUTHENTICATION_PATTERN', '/^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]*)?$/');
function validate_url_with_user_authentication(string $input): bool {
return (bool) preg_match(URL_WITH_USER_AUTHENTICATION_PATTERN, $input);
}
// Example
var_dump(validate_url_with_user_authentication("http://user:password@example.com")); // bool(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 PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. 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