Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Edge: 156.0.4314.70 to 157.0.4341.46

3 new settings, 1 changed since 156.0.4314.70. 4 retained releases apart.

Changes that matter

4 settings · compared with 156.0.4314.70
  • Computer and user · Microsoft Edge\HTTP authentication
    Registry key: Software\Policies\Microsoft\Edge · Value name: Not specified
  • Computer and user · Microsoft Edge
    Registry key: Software\Policies\Microsoft\Edge · Value name: BackForwardCacheForWebSocketsAllowed
    • Renamed Allow Back/Forward Cache for WebSockets[added: (deprecated)]
    • Description [added: DEPRECATED: ]This policy [added: is deprecated. It is currently supported but will become obsolete in a future release. This policy ]controls whether active WebSocket connections are disconnected when a page enters back/forward … means pages with active WebSockets will not be cached. This policy is [added: deprecated starting in Microsoft Edge version 157 because it was ]intended to be [removed: temporary and][added: temporary. It] will be removed [added: starting ]in [removed: the future.][added: Microsoft Edge version 167. There is no replacement policy; organizations should stop configuring it before then.]
      Whole description, marked

      [added: DEPRECATED: ]This policy [added: is deprecated. It is currently supported but will become obsolete in a future release. 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 [added: deprecated starting in Microsoft Edge version 157 because it was ]intended to be [removed: temporary and][added: temporary. It] will be removed [added: starting ]in [removed: the future.][added: Microsoft Edge version 167. There is no replacement policy; organizations should stop configuring it before then.]

  • Computer and user · Microsoft Edge
    Registry key: Software\Policies\Microsoft\Edge · Value name: Not specified
  • Computer and user · Microsoft Edge
    Registry key: Software\Policies\Microsoft\Edge · Value name: Not specified
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 13:11 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current