Bug #4511

Error during WebSocket handshake

Added by saen acro 19 days ago. Updated 3 days ago.

Status:FixedStart date:2017-08-01
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:General
Target version:-
Found in version:4.3-311 Affected Versions:

Description

Vivaldi Browser

tvh.js.gz:511 WebSocket connection to 'ws://192.168.1.222:9981/comet/ws' failed: Error during WebSocket handshake: Response must not include 'Sec-WebSocket-Protocol' header if not present in request: tvheadend-comet

Edge Browser

SCRIPT12152: WebSocket Error: Network Error 12152

IE 11 same situation

Only EPG page show and after few seconds page reload

Associated revisions

Revision 740d9bcb
Added by Jaroslav Kysela 19 days ago

javascript: fix websocket comet protocol identification (for chrome), fixes #4511

History

#1 Updated by saen acro 19 days ago

#2 Updated by Mono Polimorph 19 days ago

saen acro wrote:

Only EPG page show and after few seconds page reload

Me too! With Chrome Browser... only EPG shows.

So, I rollback to the previous snapshot before this change: http://www.tvheadend.org/projects/tvheadend/repository/revisions/f9df9b7401e1838767c0e55126fae7d39640db9a

#3 Updated by john - 19 days ago

+1

Mono Polimorph wrote:

saen acro wrote:

Only EPG page show and after few seconds page reload

Me too! With Chrome Browser... only EPG shows.

So, I rollback to the previous snapshot before this change: http://www.tvheadend.org/projects/tvheadend/repository/revisions/f9df9b7401e1838767c0e55126fae7d39640db9a

#4 Updated by Jaroslav Kysela 19 days ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

#5 Updated by Pyro maniac 12 days ago

I am using reverse proxy with apache and tvheadend; in this situation the problem still exists.

But accessing from the local-area-network without proxy, everything is fine.

Do I have to change my config somehow to ensure tvheadend is accessible through the reverse proxy?

#6 Updated by Jaroslav Kysela 12 days ago

You should configure websockets proxy, too.

#7 Updated by bas co 3 days ago

i'm on v4.3-333-g08c4069
WebSocket connection to 'ws://192.168.0.254:9981/comet/ws' failed: Connection closed before receiving a handshake response

using chromium 60.0.3112.101 64 bits

#8 Updated by bas co 3 days ago

using any other browser (ff, ie, chrome) also fails

#9 Updated by saen acro 3 days ago

(/) Firefox latest 32/64bit no problem
(/) Opera latest no problem
(/) Vivaldi latest no problem
(/) EDGE and IE 11 no problem

#10 Updated by Mark Clarkstone 3 days ago

saen acro wrote:

(/) Firefox latest 32/64bit no problem
(/) Opera latest no problem
(/) Vivaldi latest no problem
(/) EDGE and IE 11 no problem

(/) Chromium 60.0.3112.78 (Developer Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit) - No problem here..

Request URL:ws://192.168.1.3:9981/comet/ws
Request Method:GET
Status Code:101 Switching Protocols
Response Headers
view source
Connection:Upgrade
Sec-WebSocket-Accept:<redacted>
Sec-WebSocket-Protocol:tvheadend-comet
Upgrade:websocket

Also available in: Atom PDF