We are delighted to release Mongoose Embedded Web Server 6.6 today!
You know, Mongoose is more than an embedded web server. It’s a multi-protocol networking library. And, in this spirit, we have expanded the functionality even further. Check out the below, download Mongoose and test for yourself!
STM32 support added
Mongoose 6.6 can be built and run on STM32 microcontrollers. Check out the new example here for an MQTT Client for STM32. The example runs through how to build an MQTT client for STM32 with TI CC3100 WIFI as network module.
PIC32 support added
We’ve also added PIC32 support to Mongoose. And just as for STM32, we have a new example for you to follow here. It runs through how an MQTT Client is intended for running on PIC32 (MX series with TI CC3100 as a network module).
TI CC3200 support improved
We have improved the already supported TI CC3200. Here, the TI Compiler on docker image was updated to version 5.8.2.
New API introductions
We want to make Mongoose as simple as possible to use. Check out the new API we’ve added in 6.6:
mg_http_send_redirect - sends a redirect response
mg_http_serve_file - serves a specific file with a given MIME type and optional extra headers.
MG_F_ENABLE_BROADCAST - new flag, allows to send broadcast messages
MG_EV_SSI_CALL_CTX - new event, the variant of MG_EV_SSI_CALL with context of the SSI call being processed in addition to the tag argument.
We mentioned the STM32 and PIC32 examples already, but they are not all! Check out these additional examples to help you get started with your embedded project:
We always improve bugs along the way between releases. If you come across anything, let us know in our forum.
Use gethostbyname to resolve `hocalhost` if resolving via /etc/hosts failed. (especially useful for Windows users)
Fixed a lot of errors and warning in MSVC compilation
Fixed bug in multithreaded mode support:
Copy flags for accepted connection
Use user timeout in multithreading polling
Smaller bug fixes
We want you to be able to find all the answers you need in our documentation. That’s why we try to improve it as best we can. So you’ll see that we have more clear and structured documentation available as well as explanations for each example added directly in our documentation section.