Permissions Policy (Feature Policy) Header Regex for Go
/^(camera|microphone|geolocation|payment|usb|fullscreen|display-capture|gyroscope|accelerometer|magnetometer|ambient-light-sensor|autoplay|encrypted-media|midi|picture-in-picture|speaker-selection|sync-xhr|vibrate|web-share|clipboard-read|clipboard-write|interest-cohort|screen-wake-lock|xr-spatial-tracking)=\((\*|self(?:\s+"https?://[^"]+")*|)\)$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching permissions policy (feature policy) header, ported and verified for Go. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. 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
// Permissions Policy (Feature Policy) Header
// ReDoS-safe | RegexVault — Security > Security Headers
package validation
import "regexp"
var permissionsPolicyFeaturePolicyHeaderRe = regexp.MustCompile(`^(camera|microphone|geolocation|payment|usb|fullscreen|display-capture|gyroscope|accelerometer|magnetometer|ambient-light-sensor|autoplay|encrypted-media|midi|picture-in-picture|speaker-selection|sync-xhr|vibrate|web-share|clipboard-read|clipboard-write|interest-cohort|screen-wake-lock|xr-spatial-tracking)=\((\*|self(?:\s+"https?://[^"]+")*|)\)$`)
func ValidatePermissionsPolicyFeaturePolicyHeader(s string) bool {
return permissionsPolicyFeaturePolicyHeaderRe.MatchString(s)
}
// Example
// fmt.Println(ValidatePermissionsPolicyFeaturePolicyHeader("camera=()")) // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
camera=() | camera=disabled |
geolocation=(self) | geolocation=none |
payment=(self "https://payment.example.com") | payment=(https://example.com) |
microphone=() | microphone=(*)extra |
When to use this pattern
This pattern is drawn from the Security > Security Headers 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
The Permissions Policy syntax changed from the Feature Policy syntax in 2021. Old Feature Policy used ; separators and different syntax. Chrome 88+ uses the new syntax. Set both headers during the migration period.
Technical Notes
Permissions Policy (formerly Feature Policy) controls which browser features are available to a page. camera=(), microphone=(), geolocation=() disables the feature completely. () = nobody, (self) = same origin only, (*) = all origins. Prevents third-party scripts from activating features.
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