Open Bug 1950094 Opened 21 days ago Updated 20 days ago

gojo.wtf - The page fails to load

Categories

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

Firefox 135
Desktop
Windows 11

Tracking

(Webcompat Priority:P3, Webcompat Score:4, firefox135 affected, firefox136 affected, firefox137 affected)

Webcompat Priority P3
Webcompat Score 4
Tracking Status
firefox135 --- affected
firefox136 --- affected
firefox137 --- affected

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat-source:product])

User Story

platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:some
branch:release
diagnosis-team:security
user-impact-score:60

Environment:
Operating system: Windows 11
Firefox version: Firefox 135.0 (release)

Preconditions:

  • Clean profile

Steps to reproduce:

  1. Navigate to: http://gojo.wtf/
  2. Observe

Expected Behavior:
The page loads

Actual Behavior:
The page seems to be stuck in a perpetual loading state

Notes:

  • Reproducible on the latest Firefox Release and Nightly
  • Reproducible regardless of the ETP setting
  • Works as expected using Chrome

Created from webcompat-user-report:919fc54c-daab-410b-899a-32eebd51e3ce

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

The page appears to be displayed correctly when using https:// instead of http://.

Chrome seems to be more aggressive upgrading to https. Freddy, do you know the state of our https-upgrade-features?

Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 4
Flags: needinfo?(fbraun)
Priority: -- → P3

We do not have HTTPS-First enabled for Release yet. It has been on in Nightly for a while. However, explicitly entering an http:// URL in the address bar will prevent the upgrade.

I'm not sure what "stuck in a perpetual loading state" might mean exactly but the site does indeed not load all kinds of resources when used over insecure HTTP. That's because the resource links are https://... and there is no CORS policy to allow the http:// site.

This seems to be a site configuration error. The site is available over HTTP but doesn't work properly.

Flags: needinfo?(fbraun)

This might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1906590 because the site does have an HTTPS RR.

See Also: → 1906590
You need to log in before you can comment on or make changes to this bug.