Wrong detection of a captive web portal on my own private WiFi network
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: jj.gud, Unassigned)
Details
Attachments
(1 file)
|
1.06 MB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
Since the last Firefox update (Firefox 113.0.1 on Mac Ventura 13.3.1), there is frequently a supplementary line alert, just below the URL target, warning about a "captive web portal", which is ridiculous since I connect to my own private WiFi network.
Actual results:
This message appears for instance while I report this bug on bugzilla.mozilla.org, and many other URLs (see attached .PNG).
Expected results:
NO captive web portal detection !
An option to disable this faulty detection would be nice.
Comment 1•2 years ago
|
||
Thank you for filing the bug report.
Could you please share the Firefox version where it was working for you?
This will help us narrow down the problem causing patch. You could use mozregression to find that.
Alternatively you could follow these instructions to disable the warning.
Thanks for the quick answer.
I downloaded mozregression-gui as suggested, but I did not find how to use it : it shows 3 blanks panes, and nothing I did in Mozilla changed any of those panes.
AFAIR, since I usually update Firefox as soon as I am notified of a new version availability, Firefox must still have been working without this annoying captive portal message in the next to last version (113.0.0 ?).
I then followed your instructions to disable network.captive-portal-service.enabled, and since then the warning message has not appeared again.
Let me know how I can help more to eradicate this bug (within the limits of my non-developer knowledge ;-).
Thanks again.
Comment 3•2 years ago
|
||
We haven't made any changes to our captive portal implementation as far as I know.
Could you capture some HTTP logs using these instructions: https://firefox-source-docs.mozilla.org/networking/http/logging.html to figure out what's rewriting your requests?
Thanks!
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Close as incomplete, because there is no response.
Description
•