Fix WebConfig bootstrap for legacy Android Chrome
Physical LG Android 5.1.1 testing found Chrome 43 could decode gzip but failed on the bootstrap's arrow syntax. Use ES5 functions and Promises while preserving retries, version refresh, and optional abort handling. Keep Google Zopfli gzip compression at 1,000 iterations. Verified the flashed V4.3 through its WiFi link using the real Android browser: bootstrap and main page gzip responses completed, settings loaded at 910.525 MHz, and no JavaScript or transfer errors were reported. Add a loader syntax regression and document legacy browser support.
This commit is contained in:
1 parent
02b8935794
commit
0feffaa3ab
4 files changed
+52
-42
No files matched your search
@@ -112,6 +112,8 @@ Browsers decompress the pages automatically over ordinary HTTP. WebConfig
|
||||
returns HTTP 406 when a client explicitly excludes gzip. Its large page closes
|
||||
the TCP connection gracefully after the final acknowledged bytes so browsers
|
||||
do not report a completed download as aborted.
|
||||
The bootstrap uses ES5 syntax and Promise-based loading, including on Android
|
||||
5.1.1 with Chrome 43; newer JavaScript syntax must not prevent the page loading.
|
||||
|
||||
Most full-size ESP32 MQTT observer builds have the shared WebConfig portal. On a
|
||||
fresh device with no saved SSID:
|
||||
|
||||
Reference in new issue
Block a user