mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #362] Content-length is not set properly #306
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#306
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 @suculent on GitHub (May 3, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/362
Works on iPhone, but fails on certain Androids accessing the Captive Portal. Solution to fix this was straitforward... adding explicit Content-Length header before all ->send requests.
@suculent commented on GitHub (May 3, 2017):
Following solution works for me:
github.com/suculent/WiFiManager@ada93b721a@scop commented on GitHub (May 26, 2017):
I was bitten by this on Android 7.1.2, and the suggested change works for me too, please apply.
@scop commented on GitHub (Jul 10, 2017):
@suculent, could you submit a pull request to get this fix in? Thanks!
@suculent commented on GitHub (Jul 10, 2017):
I've already done this quite a while ago https://github.com/tzapu/WiFiManager/pull/363
@tzapu commented on GitHub (Jul 10, 2017):
thanks guys, merged
you need to download the latest master though, until there will be a release
@tablatronix commented on GitHub (Sep 15, 2017):
The sdk seems to already send content-length headers, I wonder why android is so picky about the order maybe ?
@suculent commented on GitHub (Sep 15, 2017):
It did not happen only on Android, at least I'm not the Android case, we use iPhones and iPad Pro to test WiFiManager in AP mode.
I need to find correct test case. After upgrading to latest WiFiManager I need to solve own issues first before going back to AP mode.
Odesláno z iPhonu
@tablatronix commented on GitHub (Sep 15, 2017):
Maybe this changed in SDK at some point, shrug