1920679 - investing.com does not load properly (possibly cors issue)

Status: REOPENED

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

Description

[hundreAd]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0

Steps to reproduce:

go to:
https://www.investing.com/charts/advinion.php?version=6.3.1.0&domain_ID=1&lang_ID=1&timezone_ID=8&pair_ID=10529&interval=1D

ff 130.0
Windows 10 [Version 10.0.19043.928]

Actual results:

does not load properly (gives blank screen)

new installation of ff (in virtual machine)
NO settings modifications, NO plugings, etc.

• issue of course occurs outside vm as well

Expected results:

loads find with edge/chrome (default installation, no settings changed)

POSSIBLY cors issue, as in network monitor:
https://advcharts.investing.com/static/advinion/6.3.1.0/ChartCore/js/6.3.1/version/prochart.version.json.js?1727176544642

fails with 403 and "transferred" shows "cors missing allow origin"

again, works fine with other browsers so this is definitely a ff problems (note: SOMETIMES, ff does deign to load the site fine, in which case there is no cors failure)

Comment 1

[hundreAd]

to clarify, the cors failure is for method OPTIONS

Comment 2

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

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

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

It works for me, on Linux and Windows, with Firefox 130 and 132.
Could you check again if you're still seeing the issue?

Comment 4

[hundreAd]

yes, still bugged in ff

Comment 5

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

Did this work in Firefox before?
If so, could you try using https://mozilla.github.io/mozregression/quickstart.html to find the Firefox build that caused the issue?

Otherwise, could you capture some HTTP logs by going to about:logging, click start, reproduce the issue, then upload the profile and post the link here (or send it to [e-mail] if it contains any private information )
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Thanks!

Comment 6

[hundreAd]

(In reply to Valentin Gosu [:valentin] (he/him) from comment #5)

Otherwise, could you capture some HTTP logs by going to about:logging, click start, reproduce the issue

https://profiler.firefox.com/public/ayyq5sbzjpbztfk7vq9raam4x22y7aa4fy0xdn8/calltree/?globalTrackOrder=0w5&thread=2&v=10

Comment 7

[hundreAd]

(In reply to Valentin Gosu [:valentin] (he/him) from comment #5)

If so, could you try using https://mozilla.github.io/mozregression/quickstart.html to find the Firefox build that caused the issue?

works in all nightly versions
fails in release version (130.0.1)

Comment 8

[hundreAd]

(In reply to hundreAd from comment #7)

works in all nightly versions

release 118.0.2 WORKS
release 119.0 FAILS

Comment 9

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

The severity field is not set for this bug.
:kershaw, could you have a look please?

For more information, please visit BugBot documentation.

Comment 10

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

(In reply to hundreAd from comment #8)

release 118.0.2 WORKS
release 119.0 FAILS

For some reason this bug doesn't happen in Nightly. I'm wondering if there's a fix behind a pref that's only enabled in Nightly?
It might have something to do with fingerprinting protection, since for 118 I'm never getting a cloudflare captcha, while in 119 I am followed by the page not working. A few refreshes later it does seem to work, but I haven't quite figured out what makes it work.

Comment 11

[Kershaw Chang [:kershaw]]

This seems like a web compatibility issue to me. Based on the log in comment #6, it’s unclear why the site is returning a 403 error. Note that the CORS error occurred after the 403, so it's likely not the root cause.

Dennis, is there any way we can contact the website and figure out why then reply a 403 error?
Thanks.

Comment 12

[Dennis Schubert [:denschub]]

Let's move this to our component and mark this as needs-contact.

Comment 13

[Jeff Muizelaar [:jrmuizel]]

This works for me in Firefox 139 release and ESR and beta. hundreAd can you still reproduce?

Comment 14

[hundreAd]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #13)

This works for me in Firefox 139 release and ESR and beta. hundreAd can you still reproduce?

works currently
maybe got fixed in ff, or in website, or it some intermediary along the way?
please note however that this never occurred 100%, only sometimes. so this seeming to work does not actually guarantee fixed (unless the actual cause WAS found and indeed fixed, and you are now merely confirming that the fix works)

Comment 15

[Jeff Muizelaar [:jrmuizel]]

(In reply to hundreAd from comment #14)

(In reply to Jeff Muizelaar [:jrmuizel] from comment #13)

This works for me in Firefox 139 release and ESR and beta. hundreAd can you still reproduce?

works currently
maybe got fixed in ff, or in website, or it some intermediary along the way?
please note however that this never occurred 100%, only sometimes. so this seeming to work does not actually guarantee fixed (unless the actual cause WAS found and indeed fixed, and you are now merely confirming that the fix works)

Thanks. If it happens for you again please reopen.