1835776 - Continuous request to captive portal

Status: UNCONFIRMED

(Core :: Networking, defect, P2)

Description

[maxzzzz64]

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

Steps to reproduce:

It's enough to navigate on a site with protocol http:// (not https://) and this trigger a continous request for captive portal

Actual results:

see previous point:
It's enough to navigate on a site with protocol http:// (not https://) and this trigger a continous request for captive portal

Expected results:

No continous request for captive portal

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

Can you provide some more details on how to reproduce this? What device? What's the network situation when this starts? Wifi, wired, is this a new network just plugged in/connected-to?
Thanks!

Comment 2

[maxzzzz64]

How to reproduce this? Standard network with first login to firewall at start-up. After some short random time, the captive portal is triggerred
What device ? Firefox 113
OS Windows 11
What's the network situation when this starts? Networking available, already logged to firewall and consensus obtained, already navigated a lot
Network Wired Hard-linked

Comment 3

[u Ltd.]

It happens also to me: I have an HTTP tab open which frequently reloads. This seems to trigger the captive portal detection which happens 14 to 23 times per second, each detection consisting of getting canonical.html, success.txt?ipv4 and success.txt?ipv6, consuming ~44 KiB/s traffic in total over my metered connection.

Firefox 144.0.2 (32-bit) on GNU/Linux

Comment 4

[Kershaw Chang [:kershaw]]

(In reply to u Ltd. from comment #3)

It happens also to me: I have an HTTP tab open which frequently reloads. This seems to trigger the captive portal detection which happens 14 to 23 times per second, each detection consisting of getting canonical.html, success.txt?ipv4 and success.txt?ipv6, consuming ~44 KiB/s traffic in total over my metered connection.

Firefox 144.0.2 (32-bit) on GNU/Linux

Hi, thanks for reporting this.
Could you try to capture a http log with the steps below?

1. Open a new tab and paste this link: about:logging?modules=timestamp%2Csync%2CnsHttp%3A5%2Ccache2%3A5%2CnsSocketTransport%3A5%2CnsHostResolver%3A5%2CCaptivePortalService%3A5&output=profiler
2. Click Start logging and try to reproduce the problem.
3. Stop logging and upload the profile.
4. Since the profile link might contain privacy information, you can send the link to [e-mail].