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

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais
Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.
Arquivadas

Sec-WebSocket-Protocol in websocket handshake response

Firefox Outro
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

Todas as respostas (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.