REGEXVAULTv2.0
Web & Network/HTTP
Verified Safe

HTTP Bearer Token (Authorization Header) Regex for Go

/^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 Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

Go
// HTTP Bearer Token (Authorization Header)
// ReDoS-safe | RegexVault — Web & Network > HTTP

package validation

import "regexp"

var httpBearerTokenAuthorizationHeaderRe = regexp.MustCompile(`^Bearer [A-Za-z0-9\-._~+/]+=*$`)

func ValidateHttpBearerTokenAuthorizationHeader(s string) bool {
    return httpBearerTokenAuthorizationHeaderRe.MatchString(s)
}

// Example
// fmt.Println(ValidateHttpBearerTokenAuthorizationHeader("Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0.dozjgNryP4J3jVmNHl0w5N_XgL0n3I9PlFUP0THsR8U")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIn0.dozjgNryP4J3jVmNHl0w5N_XgL0n3I9PlFUP0THsR8Ubearer token
Bearer abc123def456Bearer
Bearer token==Token abc123
Bearer aBasic dXNlcjpwYXNz
Bearer validTokenBearer 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 Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. 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