mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #967] configPortalHasTimeout dependings #820
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#820
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dontsovcmc on GitHub (Nov 15, 2019).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/967
I can't understand, why we need to call handleRequest() in root handle to reset _webPortalAccessed?
configPortal timeout start point should be the time when it starts. But now we have another timepoint - when portal opened by client.
Why does it needed?!
If we make timeout only from function call, we simplify configPortalHasTimeout() function and remove handleRequest().
@tablatronix commented on GitHub (Nov 15, 2019):
That is how I hacked the webactive timeout, it was easier than adding new variables for something that is experimental and not even enabled by default. It is a bit of a kludge, it also prevents me from having to modify the timeout evaluation, easier to just bump start time, we do not actually need it..
@tablatronix commented on GitHub (Nov 15, 2019):
https://github.com/tzapu/WiFiManager/blob/development/WiFiManager.h#L246