HTTP Bearer Token (Authorization Header) Regex for PHP
/^Bearer [A-Za-z0-9\-._~+/]+=*$/What this pattern does
This page provides a well-structured, multi-part regular expression for matching http bearer token (authorization header), 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
// HTTP Bearer Token (Authorization Header)
// ReDoS-safe | RegexVault — Web & Network > HTTP
define('HTTP_BEARER_TOKEN_AUTHORIZATION_HEADER_PATTERN', '/^Bearer [A-Za-z0-9\-._~+\/]+=*$/');
function validate_http_bearer_token_authorization_header(string $input): bool {
return (bool) preg_match(HTTP_BEARER_TOKEN_AUTHORIZATION_HEADER_PATTERN, $input);
}
// Example
var_dump(validate_http_bearer_token_authorization_header("Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0.dozjgNryP4J3jVmNHl0w5N_XgL0n3I9PlFUP0THsR8U")); // bool(true)Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0.dozjgNryP4J3jVmNHl0w5N_XgL0n3I9PlFUP0THsR8U | bearer token |
Bearer abc123def456 | Bearer |
Bearer token== | Token abc123 |
Bearer a | Basic dXNlcjpwYXNz |
Bearer validToken | Bearer invalid token |
When to use this pattern
This pattern is drawn from the Web & Network > HTTP 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
'Bearer' is case-sensitive per RFC 6750, section 2.1. Some non-conforming servers accept 'bearer' — reject it in strict-mode validation.
Technical Notes
Bearer tokens should be treated as opaque strings by resource servers. Validate the token signature and claims with your JWT library, not by regex. Token must not contain spaces.
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