Closed Bug 1623501 Opened 4 years ago Closed 4 years ago

HTTP3 - Websocket - Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws - Whatsapp

Categories

(Core :: Networking: WebSockets, defect, P1)

76 Branch
defect

Tracking

()

VERIFIED FIXED
mozilla76
Tracking Status
firefox76 --- verified

People

(Reporter: wtds.trabalho, Assigned: dragana)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(3 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

  • Open
  • https://web.whatsapp.com/
  • Can't connect
  • Sometimes connects after many tries
  • Tried in another container
  • Tried non Fission window
  • Only on Firefox

22:35:53.291 GETwss://web.whatsapp.com/ws [HTTP/3 400 Bad Request 278335ms]

and

22:35:53.291 GETwss://web.whatsapp.com/ws
[HTTP/3 400 Bad Request 278335ms]

Request URL:wss://web.whatsapp.com/ws
Request Method:GET
Remote Address:31.13.85.51:443
Status Code:
400
Version:HTTP/3
	
Response Headers (63 B)	
Raw Headers
date	
Wed, 18 Mar 2020 22:39:47 GMT
Request Headers (573 B)	
Raw Headers
Accept	
*/*
Accept-Encoding	
gzip, deflate, br
Accept-Language	
en-US,en;q=0.5
Alt-Used	
web.whatsapp.com
Cache-Control	
no-cache
Connection	
keep-alive, Upgrade
DNT	
1
Host	
web.whatsapp.com
Origin	
https://web.whatsapp.com
Pragma	
no-cache
Sec-Fetch-Dest	
websocket
Sec-Fetch-Mode	
websocket
Sec-Fetch-Site	
same-origin
Sec-WebSocket-Extensions	
permessage-deflate
Sec-WebSocket-Key	
???????==
Sec-WebSocket-Version	
13
Upgrade	
websocket
User-Agent	
Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/76.0

Actual results:

It's slow and hard to use Web Whatsapp in Firefox
But its too fast in chrome.
Why? And it's hard to connect.

22:36:54.545 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. app.45a9afa0af17d19ea932.js:2:836999

and

22:36:54.545 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. app.45a9afa0af17d19ea932.js:2:836999
22:36:55.673
GETwss://web.whatsapp.com/ws
22:36:58.993
GETwss://web.whatsapp.com/ws
22:37:05.050
XHRGEThttps://web.whatsapp.com/status.json
22:37:15.673 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. 2 app.45a9afa0af17d19ea932.js:2:836999
22:38:12.181
GETwss://web.whatsapp.com/ws
22:38:18.192
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 185ms]

22:38:24.399
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 185ms]

22:38:28.429
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 149ms]

22:38:32.181 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws.

Expected results:

  • Improve HTTP2/HTTP3 sites support
  • Improve errors debug.
  • improve websocket errors info.
  • Improve support for Whatsapp Web

Thanks!

Problems with Whatsapp, websocket and HTTP/3

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Networking: WebSockets
Product: Firefox → Core

Dragana, is this a known bug?

Flags: needinfo?(dd.mozilla)
Assignee: nobody → dd.mozilla
Blocks: QUIC
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(dd.mozilla)
Priority: -- → P1

we should not try sending websocket requests over http3. I will need to debug it a bit to figure out why we are doing it. I think I know ....

Whiteboard: [necko-triaged]
Pushed by ddamjanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ca14cd1c0e0b
WebSocket cannot run over http3. r=kershaw
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Flags: qe-verify+

Hello.
I was unable to reproduce the issue with Nightly 76.0a1 (2020-03-18). Could you provide any extra information on exactly how to reproduce it?

Flags: needinfo?(wtds.trabalho)

Hi,

I can try again.
But just try to activate HTTP/3 flags and DNS over HTTPS.
How flags/configs did you changed? The HTTP/3 it's not the default option yet.

Thanks

Flags: needinfo?(wtds.trabalho) → needinfo?(poke.arnold)

Can you try with: network.http.http3.enabled set to ON.

I was able to reproduce on Windows 10 x64 with Nightly 76.0a1 (2020-03-18) by activating DNS over HTTPS and with the pref enabled.
Thank you Wellington.

Fix confirmed with Firefox 76.0 on Windows 10 x64, Ubuntu 20.04 x64 and MacOS 10.15. Updating the flag to verified.

Flags: needinfo?(poke.arnold)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: