Catsxp Forum

Hi, in general, Chromium browsers are good but one of the disappointing things about chromium browsers is that we can't disable the captive portal, i don't like captive portal because it can consume energy, wear out the battery...


the command line to disable it seems obsolete, in addition the command line doesn't work all time permanently with all sites, i.e. if the web browser is started from a desktop url shortcut of a website, the command line doesn't work, I noticed it when trying to disable webassembly, if the browser startup from a desktop website's url shortcut , the command line of chromium is no longer effective:

--disable-chrome-captive-portal-detector

I only use wifi, I don't go to hotels, I don't need the captive portal which can consume a lot of energy and we hope Catsxp can add an option to disable captive portal please! thanks!

cromite browser has achieved the feat of disabling captive portal , cromite has made a special commit to disable captive portal :


https://github.com/uazo/cromite/blob/master/ build/patches/Remove-detection-of-captive-portals.patch



Also throium browser managed to disable captive portal :

https://github.com/Alex313031/Thorium

https://github.com/Alex313031/thorium/c ... 75a39b1143

Also recently Supermium browser succeded to disable captive portal :

https://github.com/win32ss/supermium/co ... 508609898b



So we hope please great Catsxp will disable or add option to disable captive portal, thanks !




I like Firefox because it is very simple and effective to deactivate captive portal: it is documented and effective:

disable captive portal prefetch
How to stop Firefox from making automatic connections
https://support.mozilla.org/en-US/kb/ho ... onnections

network.captive-portal-service.enabled false

network.connectivity-service.enabled false

network.prefetch-next false

network.dns.disablePrefetch true

network.http.speculative-parallel-limit 0

Browser.startup.page 0


*******

this is the commit of cromite browser to disable captive portal :


"Subject: Remove detection of captive portals

chrome/browser/net/profile_network_context_service.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/chrome/browser/net/profile_network_context_service.cc b/chrome/browser/net/profile_network_context_service.cc
--- a/chrome/browser/net/profile_network_context_service.cc
+++ b/chrome/browser/net/profile_network_context_service.cc
@@ -360,7 +360,7 @@ void ProfileNetworkContextService::UpdateAdditionalCertificates() {
void ProfileNetworkContextService::RegisterProfilePrefs(
user_prefs::PrefRegistrySyncable* registry) {
registry->RegisterBooleanPref(embedder_support::kAlternateErrorPagesEnabled,

true);
false);
registry->RegisterBooleanPref(prefs::kQuicAllowed, true);
registry->RegisterBooleanPref(prefs::kGloballyScopeHTTPAuthCacheEnabled,
false);

Add to the next version

Amazing !! Thank you so much

IMPORTANT UPDATE :

Hi, yesterday i said that 2 days ago, i discover special Chromium browser 134 compatible with my windows 7 OS 32 bits :

https://github.com/e3kskoy7wqk/Chromium-for-windows-7

I also ask Mr E3kskoy7wqk the developer of Chromium-for-windows-7 to add option to disable captive portal and here his very interesting and instructive response ! maybe this new approach can be useful to Catsxp ! :

"Hello, thank you so much for your suggestion! I reviewed the methods used in cromite, thorium and supermium, and it seems effective, but for now, I don't plan to adopt their methods.

I noticed that, many years ago, Chromium used the enable-captive-portal-detection switch to control the enabling and disabling of captive portal detection. However, after July 27, 2012, 17:15:16, this switch was removed, and captive portal detection became enabled by default. I think that by reversing the logic of this switch's removal, I could achieve the same result. Therefore, I've added this switch back, but due to limited testing environment, I'm unsure if it works as expected.

If this approach doesn't work, I might consider adopting the methods used in cromite, thorium and supermium."

To control whether to enable or disable captive portal detection, Chromium employed the enable-captive-portal-detection switch; however, this switch was deleted after July 27, 2012, at 17:15:16, and captive portal detection was enabled by default.

drimisone 写了： 2025年 1月 19日 03:12 IMPORTANT UPDATE :

Hi, yesterday i said that 2 days ago, i discover special Chromium browser 134 compatible with my windows 7 OS 32 bits :

https://github.com/Block Blast/e3kskoy7wqk/Chromium-for-windows-7


I also ask Mr E3kskoy7wqk the developer of Chromium-for-windows-7 to add option to disable captive portal and here his very interesting and instructive response ! maybe this new approach can be useful to Catsxp ! :

"Hello, thank you so much for your suggestion! I reviewed the methods used in cromite, thorium and supermium, and it seems effective, but for now, I don't plan to adopt their methods.

I noticed that, many years ago, Chromium used the enable-captive-portal-detection switch to control the enabling and disabling of captive portal detection. However, after July 27, 2012, 17:15:16, this switch was removed, and captive portal detection became enabled by default. I think that by reversing the logic of this switch's removal, I could achieve the same result. Therefore, I've added this switch back, but due to limited testing environment, I'm unsure if it works as expected.

If this approach doesn't work, I might consider adopting the methods used in cromite, thorium and supermium."