Bug 2443627 - Network check site should use HTTP rather than HTTPS.
Summary: Network check site should use HTTP rather than HTTPS.
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-01 09:17 UTC by realkpavel
Modified: 2026-03-01 09:18 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description realkpavel 2026-03-01 09:17:29 UTC
Description of problem:
The Fedora network check page (http://fedoraproject.org/static/hotspot.txt) defaults to HTTPS in a browser (tested on Firefox and Vivaldi). This prevents captive portals from working properly.

Steps to Reproduce:
1. On a Fedora KDE system, connect to a wifi network with a configured captive portal (for example on a bus, train or fast food restaurant).
2. A popup shows up, saying that the network needs you to log in. Clicking a button opens the fedora network check page in the browser.

Actual results:
The network check page tries and fails to load. The browser displays a connection error.

Expected results:
The captive portal should intercept the connection and show the login screen instead of the Fedora network check site.

3. Open a new tab and navigate to http://httpforever.com
4. The captive portal login screen shows up as expected.

Additional info:
From my testing with various captive portals, the interception logic assumes a HTTP (not HTTPS) connection. I have only encountered one captive portal that worked with the current HTTPS implementation. In a way this is by design for HTTPS - the captive portal is in essence performing a man in the middle attack on your website. However, the site does not transfer any security sensitive info (it just shows an "OK" message), so I think letting the site intercept as designed would be preferrable.


Note You need to log in before you can comment on or make changes to this bug.