Open Bug 1684694 Opened 5 years ago Updated 5 years ago

Firefox has a hard limit of 1,000 active web socket connections regardless of the value set in network.websocket.max-connections (default: 200).

Categories

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

Product:
Core
Component:
Networking: WebSockets
Version:
Firefox 84
Type:
enhancement

Tracking

()

People

(Reporter: mail+mozilla.org, Unassigned)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

  1. Set network.websocket.max-connections to > 1,000
  2. Try to open more than 1,000 web socket connections

Actual results:

Socket connections are rejected after 1,000.

Expected results:

Either:

a. The 1,000 limit should be stated or
b. More than 1,000 connections should be allowed

Isn't this just an operating system limit? What does

ulimit -n

say when you run it?

Flags: needinfo?(mail+mozilla.org)

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Networking: WebSockets
Product: Firefox → Core

Nope, was able to get 28,000+ connections (the default Linux port range) via a Node.js client. ulimit is “unlimited.” This looks like a Firefox limit.

Flags: needinfo?(mail+mozilla.org)

We have a max value (1000) defined here.
Maybe we should make this limitation as a pref.

Severity: -- → S4
Priority: -- → P3
Whiteboard: [necko-triaged]
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.