[GH-ISSUE #565] add close ability #473

New issue

Open

opened 2026-02-28 01:25:28 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 01:25:28 +03:00

Owner

Originally created by @tablatronix on GitHub (Mar 17, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/565

I was thinking it would be nice to have various close options.
Either hard coded, or vary depending on how the webportal was started or wether captiveportal is enabled?

Exit - shutdown webportal and ap
Close - stop captive portal

I am trying to come up with scenarios.

Maybe you want captive portal enabled, for ease of use, but then you want to stay connected to ap, or leave ap open but turn off captive portal , so you can manually access it again.

I am not sure how all CNAs works but if they get a 200 and not a redirect back, they should close.
We could also add CNA detection via useragents, but that gets crazy

Originally created by @tablatronix on GitHub (Mar 17, 2018). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/565 I was thinking it would be nice to have various close options. Either hard coded, or vary depending on how the webportal was started or wether captiveportal is enabled? Exit - shutdown webportal and ap Close - stop captive portal I am trying to come up with scenarios. Maybe you want captive portal enabled, for ease of use, but then you want to stay connected to ap, or leave ap open but turn off captive portal , so you can manually access it again. I am not sure how all CNAs works but if they get a 200 and not a redirect back, they should close. We could also add CNA detection via useragents, but that gets crazy