Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut
Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.
Diarsipkan

Sec-WebSocket-Protocol in websocket handshake response

Firefox Lainnya
Gerd replied
manlm1
manlm1

In Chrome when I make a websocket handshake, if in the request, the "Sec-WebSocket-Protocol" header is specified, then the response from server must also has this header, if not, chrome will not allow to make the connection But in Firefox, the response does not need to have the header. Why Firefox allow this?

Regards, ManLM

In Chrome when I make a websocket handshake, if in the request, the "Sec-WebSocket-Protocol" header is specified, then the response from server must also has this header, if not, chrome will not allow to make the connection But in Firefox, the response does not need to have the header. Why Firefox allow this? Regards, ManLM

Semua Balasan (1)

Gerd
Gerd

It is possible that this is a non-standard header (that is therefor not implemented in FF), or that Firefox' security policies are not as strict.

Most likely this shouldn't cause any problems.