Currently, the default HTTP client in the component library is a monster. Instantiating it adds ~160kB of binary size when compiled with -Os (and this is likely multiplied 3x if using factory + 2 OTA partitions).
Looking at the code, it seems that it's using nghttp underneath and such library is a monster as well.
As far as I understand, it makes sense to have a HTTP client that's doing GET / POST over both HTTP and HTTPS, and also supporting redirect and chunked encoding. Provided we use it only synchronously, I think this would cover 95% of the use case.
Furthermore, we can limit header parsing to the status/request line, content type and finding the transfer encoding or content length to limit the binary size.
Would you be open to a simpler (smaller) http client inclusion in the repository ?
esp http client is too large
Jump to
- English Forum
- Explore
- News
- General Discussion
- FAQ
- Documentation
- Documentation
- Sample Code
- Discussion Forum
- Hardware
- ESP-IDF
- ESP-BOX
- ESP-ADF
- ESP-MDF
- ESP-WHO
- ESP-SkaiNet
- ESP32 Arduino
- IDEs for ESP-IDF
- ESP-AT
- ESP IoT Solution
- ESP RainMaker
- Rust
- ESP8266
- Report Bugs
- Showcase
- Chinese Forum 中文社区
- 活动区
- 乐鑫活动专区
- 讨论区
- 全国大学生物联网设计竞赛乐鑫答疑专区
- ESP-IDF 中文讨论版
- 《ESP32-C3 物联网工程开发实战》书籍讨论版
- 中文文档讨论版
- ESP-AT 中文讨论版
- ESP-BOX 中文讨论版
- ESP IoT Solution 中文讨论版
- ESP-ADF 中文讨论版
- ESP Mesh 中文讨论版
- ESP Cloud 中文讨论版
- ESP-WHO 中文讨论版
- ESP-SkaiNet 中文讨论版
- ESP 生产支持讨论版
- 硬件问题讨论
- 项目展示
Who is online
Users browsing this forum: No registered users and 194 guests
- All times are UTC
- Top
- Delete cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. ESP8266EX and ESP32 are some of our products.