Loading...
Configure and generate modern W3C Permissions-Policy HTTP headers to control browser APIs and hardware access
Load recommended security profiles for web applications
Configure execution privileges for browser subsystems
Permissions-Policy: camera=(), microphone=(), speaker-selection=(), display-capture=(), geolocation=(), accelerometer=(), gyroscope=(), magnetometer=(), payment=(), usb=(), serial=(), bluetooth=(), fullscreen=(self), picture-in-picture=(), screen-wake-lock=(), autoplay=()
// In next.config.mjs headers or proxy.ts
{
key: 'Permissions-Policy',
value: 'camera=(), microphone=(), speaker-selection=(), display-capture=(), geolocation=(), accelerometer=(), gyroscope=(), magnetometer=(), payment=(), usb=(), serial=(), bluetooth=(), fullscreen=(self), picture-in-picture=(), screen-wake-lock=(), autoplay=()'
}add_header Permissions-Policy "camera=(), microphone=(), speaker-selection=(), display-capture=(), geolocation=(), accelerometer=(), gyroscope=(), magnetometer=(), payment=(), usb=(), serial=(), bluetooth=(), fullscreen=(self), picture-in-picture=(), screen-wake-lock=(), autoplay=()" always;
<meta http-equiv="Permissions-Policy" content="camera=(), microphone=(), speaker-selection=(), display-capture=(), geolocation=(), accelerometer=(), gyroscope=(), magnetometer=(), payment=(), usb=(), serial=(), bluetooth=(), fullscreen=(self), picture-in-picture=(), screen-wake-lock=(), autoplay=()">
Permissions-Policy replaces legacy Feature-Policy. Deploy this header via reverse proxy, CDN, or server response to harden browser attack surface.