Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Websocket Request Header Capitalization - Sec-Websocket-Key1/2

RESOLVED FIXED

Status

()

Core
Networking: WebSockets
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: Walt W, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; WOW64; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1

Firefox 4.0b1 appears to be sending the HTTP security key headers for websockets as "Sec-Websocket-Key1" and "Sec-Websocket-Key2" instead of "Sec-WebSocket-Key1" and "Sec-WebSocket-Key2".

The spec from http://www.whatwg.org/specs/web-socket-protocol/ indicates that the 'S' in "Socket" should be capitalized.

Reproducible: Always
Component: General → General
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
This has been fixed in a later version of Firefox 4 (and is no longer relevant to WebSockets in version 6 and later).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Component: General → Networking: WebSockets
QA Contact: general → networking.websockets
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.