• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

websockets / ws / 22551840520 / 30
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: add/require-protocol-selection-option
DEFAULT BRANCH: master
Ran 01 Mar 2026 08:26PM UTC
Files 14
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

01 Mar 2026 04:26PM UTC coverage: 99.632%. First build
22551840520.30

Pull #2314

github

lpinca
[feature] Introduce the `requireProtocolSelection` option

To comply with the WHATWG specification, the connection must fail if the
server does not return the `Sec-WebSocket-Protocol` header when a client
requests specific subprotocols. However, some servers omit this header,
as such behavior is permitted by RFC 6455.

This new option adds the ability to skip that validation, enabling the
client to work with servers that are not WHATWG-compliant.

Refs: https://github.com/websockets/ws/issues/1862#issuecomment-3944705526
Pull Request #2314: Introduce the `requireProtocolSelection` option

1113 of 1123 branches covered (99.11%)

1625 of 1631 relevant lines covered (99.63%)

916.36 hits per line

Source Files on job 6f1074fd8839ceaa1c42c5d2e1e43a86 (Node.js 24 x64 on macOS-latest) - 22551840520.30
  • Tree
  • List 14
  • Changed 2
  • Source Changed 0
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 22551840520
  • 69e6cec0 on github
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc