1995757 - www.investing.com - The quotes do not refresh in real time

Status: VERIFIED FIXED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Raul Bucata]

Environment:
Operating system: Windows 11
Firefox version: Firefox 144.0

Steps to reproduce:

1. Navigate to: https://www.investing.com/markets/united-states
2. Observe the stock/quotes values

Expected Behavior:
They change in real time

Actual Behavior:
Quotes not refreshing in realtime, nothing happens

Notes:

• Reproduces regardless of the status of ETP
• Reproduces in firefox-nightly, and firefox-release
• Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/184448

Comment 1

[Raul Bucata]

Attachment: Chr vs ff

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Comment 3

[Dennis Schubert [:denschub]]

I get a 404 on the websocket URL in Firefox, and a correct 101 in Chrome. Spoofing UA doesn't seem to work.

Comment 4

[Valentin Gosu [:valentin] (he/him)]

I looked at the request headers:

Chrome
GET wss://streaming.forexpros.com/echo/581/rxs1d3a1/websocket HTTP/1.1
Host: streaming.forexpros.com
Connection: Upgrade
Pragma: no-cache
Cache-Control: no-cache
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36
Upgrade: websocket
Origin: https://www.investing.com
Sec-WebSocket-Version: 13
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-US,en;q=0.9
Sec-WebSocket-Key: r6RbAytodNtD7JjfP1nyIg==
Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

Fx
GET /echo/104/i86km0kw/websocket HTTP/1.1
Host: streaming.forexpros.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:146.0) Gecko/20100101 Firefox/146.0
Accept: /
Accept-Language: en-US,en;q=0.7,en-GB;q=0.3
Accept-Encoding: gzip, deflate, br, zstd
Sec-WebSocket-Version: 13
Origin: https://www.investing.com
Sec-WebSocket-Extensions: permessage-deflate
Sec-WebSocket-Key: JPmcZ9R6024q8tH/50rXlQ==
Sec-Fetch-Storage-Access: none
DNT: 1
Sec-GPC: 1
Connection: keep-alive, Upgrade
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: websocket
Sec-Fetch-Site: cross-site
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket

I think the main difference is that Firefox sends Connection: keep-alive, Upgrade - I think the keep-alive is not needed.

Comment 5

[Valentin Gosu [:valentin] (he/him)]

https://datatracker.ietf.org/doc/html/rfc6455

5. The request MUST contain an |Upgrade| header field whose value
   MUST include the "websocket" keyword.

Technically Firefox's behaviour is correct, but it appears some servers just check for exact Connection: Upgrade - Chrome and Safari don't include the keep-alive token, so I guess this is now a web-compat issue.

Comment 6

[Calin Tanase]

I issue no longer reproduces on the latest Nightly (147). The prices are shown in real time now.

Comment 7

[Calin Tanase]

Verified, the issue no longer reproduces.

Tested with:

• Browser / Version: Firefox 146.0-candidate build 1
• Operating System: Windows 10