Content-length is not set properly

[suculent]

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]

Following solution works for me:

suculent@ada93b7

[scop]

I was bitten by this on Android 7.1.2, and the suggested change works for me too, please apply.

[scop]

@suculent, could you submit a pull request to get this fix in? Thanks!

[suculent]

I've already done this quite a while ago #363

[tzapu]

thanks guys, merged

you need to download the latest master though, until there will be a release

[tablatronix]

The sdk seems to already send content-length headers, I wonder why android is so picky about the order maybe ?

[suculent]

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 15. 9. 2017 v 18:44, Shawn A <[email protected]>:

…

The sdk seems to already send content-length headers, I wonder why android is so picky about the order maybe ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[tablatronix]

Maybe this changed in SDK at some point, shrug