BackForwardCacheForWebSocketsAllowed

Allow Back/Forward Cache for WebSockets

Supported versions

• Windows: ≥ 152
• macOS: ≥ 152
• Android: ≥ 152
• iOS: Not supported

Description

This policy controls whether active WebSocket connections are disconnected when a page enters back/forward cache. Active WebSocket connections previously prevented a page from being stored in back/forward cache, but Microsoft Edge has changed this behavior to disconnect the WebSockets instead, allowing the page to be cached and restoring it in a disconnected state.

If this policy is set to Enabled or left unset, WebSockets are disconnected when a page enters back/forward cache.

If this policy is set to Disabled, WebSockets will not be disconnected when a page enters back/forward cache. Since back/forward cache does not support active WebSockets, this means pages with active WebSockets will not be cached.

This policy is intended to be temporary and will be removed in the future.

Supported features

• Can be mandatory: Yes
• Can be recommended: No
• Dynamic Policy Refresh: Yes
• Per Profile: Yes
• Applies to a profile that is signed in with a Microsoft account: No

Data type

• Boolean

Windows information and settings

Group Policy (ADMX) info

• GP unique name: BackForwardCacheForWebSocketsAllowed
• GP name: Allow Back/Forward Cache for WebSockets
• GP path (Mandatory): Administrative Templates/Microsoft Edge
• GP path (Recommended): N/A
• GP ADMX file name: MSEdge.admx

Example value

Enabled

Registry settings

• Path (Mandatory): SOFTWARE\Policies\Microsoft\Edge
• Path (Recommended): N/A
• Value name: BackForwardCacheForWebSocketsAllowed
• Value type: REG_DWORD

Example registry value

0x00000001

Mac information and settings

• Preference Key name: BackForwardCacheForWebSocketsAllowed
• Example value:

<true/>

Android information and settings

• Preference Key name: BackForwardCacheForWebSocketsAllowed
• Example value:

true

See also

• Microsoft Edge - Policies