Base64 URL-Safe (No Padding) Regex for Go
/^[A-Za-z0-9\-_]+$/What this pattern does
This page provides a lightweight, single-purpose regular expression for matching base64 url-safe (no padding), 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
// Base64 URL-Safe (No Padding)
// ReDoS-safe | RegexVault — Web & Network > Misc
package validation
import "regexp"
var base64UrlsafeNoPaddingRe = regexp.MustCompile(`^[A-Za-z0-9\-_]+$`)
func ValidateBase64UrlsafeNoPadding(s string) bool {
return base64UrlsafeNoPaddingRe.MatchString(s)
}
// Example
// fmt.Println(ValidateBase64UrlsafeNoPadding("SGVsbG8")) // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
SGVsbG8 | SGVsbG8== |
dGVzdA | has+plus |
AAAA | has/slash |
YWJj | has space |
eyJhbGciOiJIUzI1NiJ9 | — |
When to use this pattern
This pattern is drawn from the Web & Network > Misc 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
Do not decode URL-safe base64 with a standard base64 decoder without first replacing - with + and _ with /.
Technical Notes
Used in JWTs, OAuth tokens, and URL-embedded data. Empty string is excluded here since a zero-length token is semantically invalid in most use cases.
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