This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

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.

Learn More

Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.

What proper headers should I use to succefully end handshake when connecting to WebSocket?

  • 2 odgovori
  • 3 ima ovaj problem
  • 12 views
  • Posljednji odgovor poslao marverix

marverix
marverix
more options

When I try to use WebSocket, my server on handshake send header like this: 

                       $reply = "HTTP/1.1 101 Switching Protocols\r\n" .
                               "Upgrade: websocket\r\n" .
                               "Connection: Upgrade\r\n" .
                               "Sec-WebSocket-Accept: {$accept}\r\n\r\n";

But, FF doesn't really ends/accept (?) it... It just wainting, and after few sec it disconnect. In Chrome browser it works perfectly... :(

When I try to use WebSocket, my server on handshake send header like this: $reply = "HTTP/1.1 101 Switching Protocols\r\n" . "Upgrade: websocket\r\n" . "Connection: Upgrade\r\n" . "Sec-WebSocket-Accept: {$accept}\r\n\r\n"; But, FF doesn't really ends/accept (?) it... It just wainting, and after few sec it disconnect. In Chrome browser it works perfectly... :(

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See https://developer.mozilla.org/en/WebSockets

marverix
marverix Vlasnik pitanja
more options

I realy REALY searched whole internet and I saw this page a lot of times and I have read RFC6455 milion times! Everything is 100% ok!... In Chrome it works just perfect, but in my favorite browser - FF <3 - no... :/