Permissions Policy (Feature Policy) Header Regex for Java
/^(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 Java. 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 Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.
Java Implementation
// Permissions Policy (Feature Policy) Header
// ReDoS-safe | RegexVault — Security > Security Headers
import java.util.regex.Pattern;
public class PermissionsPolicyFeaturePolicyHeaderValidator {
private static final Pattern PATTERN =
Pattern.compile("^(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?://[^\"]+\")*|)\\)$");
public static boolean validate(String input) {
return PATTERN.matcher(input).matches();
}
// Example
public static void main(String[] args) {
System.out.println(validate("camera=()")); // true
}
}Test 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 Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. 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