Closed Bug 1721858 Opened 4 years ago Closed 4 years ago

Enable WebSocket connection partitioning if first party isolation is enabled

Categories

(Core :: Networking: WebSockets, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
92 Branch
Tracking Status
firefox92 --- fixed

People

(Reporter: emz, Assigned: emz)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

The Websocket connection partitioning which was added in Bug 1713748 separates the pending connection queue by origin attributes. That means first party isolation can also benefit from it and we should enable it when first party isolation is enabled.

We can extend this pref check to include the first party isolation pref:
https://searchfox.org/mozilla-central/rev/352b525ab841278cd9b3098343f655ef85933544/netwerk/protocol/websocket/WebSocketChannel.cpp#490

bool isPartitioned =
          ( StaticPrefs::privacy_partition_network_state() || StaticPrefs::privacy_firstparty_isolate() ) &&
          StaticPrefs::privacy_partition_network_state_ws_connection_queue()

Keeping privacy_partition_network_state_ws_connection_queue separate is probably a good idea so the feature can still be turned off independently.

Severity: -- → N/A
Priority: -- → P2
Whiteboard: [necko-triaged]
Assignee: nobody → pbz
Status: NEW → ASSIGNED
Pushed by pzuhlcke@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8dc169b04bbc Enable WebSocket connection partitioning if first party isolation is enabled. r=nhnt11
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: