Avatar for Username

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

Este tópico foi arquivado. Faça uma nova pergunta se precisa de ajuda.

Sec-WebSocket-Protocol in websocket handshake response

  • 1 resposta
  • 1 tem este problema
  • 22 visualizações
  • Última resposta de Gerd

manlm1
manlm1
more options

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
more options

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.