mirror of
https://github.com/cesanta/mongoose.git
synced 2024-12-26 22:41:03 +08:00
143 lines
6.9 KiB
Markdown
143 lines
6.9 KiB
Markdown
# Mongoose - Embedded Web Server / Embedded Networking Library
|
|
|
|
[](https://opensource.org/licenses/gpl-2.0.php)
|
|
[](https://github.com/cesanta/mongoose/actions)
|
|
[](https://codecov.io/gh/cesanta/mongoose)
|
|
[](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:mongoose)
|
|
|
|
Mongoose is a network library for C/C++.
|
|
It implements event-driven
|
|
non-blocking APIs for TCP, UDP, HTTP, WebSocket, MQTT. It is designed for
|
|
connecting devices and bringing them online. On the market since 2004, used by
|
|
vast number of open source and commercial products - it even runs on the
|
|
International Space Station! Mongoose makes embedded network programming fast,
|
|
robust, and easy. Features include:
|
|
|
|
- Cross-platform:
|
|
- works on Linux/UNIX, MacOS, Windows, Android
|
|
- works on STM32, NXP, ESP32, NRF52, TI, Microchip, and other
|
|
- write code once - and it'll work everywhere
|
|
- ideal for the unification of the network infrastructure code across company
|
|
- Built-in protocols: plain TCP/UDP, SNTP, HTTP, MQTT, Websocket
|
|
- SSL/TLS support for mbedTLS and OpenSSL
|
|
- Asynchronous DNS resolver
|
|
- Tiny static and run-time footprint
|
|
- Source code is both ISO C and ISO C++ compliant
|
|
- Very easy to integrate: just copy `mongoose.c` and `mongoose.h` files to your source tree. See
|
|
[exact steps](https://mongoose.ws/documentation/#2-minute-integration-guide)
|
|
- Works in any environment with socket API, like LwIP, Zephyr, Azure
|
|
- Built-in TCP/IP stack with drivers for bare metal or RTOS systems
|
|
- Available drivers: STM32F, STM32H; NXP RT1xxx; TI TM4C; Microchip SAME54; Wiznet W5500
|
|
- A complete Web device dashboard on bare metal
|
|
[Nucleo-F429ZI](examples/stm32/nucleo-f429zi-baremetal) is only 6 files
|
|
- For comparison, a CubeIDE generated HTTP example is 400+ files
|
|
- Built-in TLS 1.3 server-side support
|
|
- Does not depend on any other software to implement networking
|
|
- Built-in firmware updates for STM32H5, STM32H7, and more coming
|
|
- Detailed [user guide, API reference and tons of tutorials](https://mongoose.ws/documentation/)
|
|
|
|
## Usage
|
|
|
|
Create a simple web server that serves a directory. The behavior of the
|
|
HTTP server is specified by its event handler function:
|
|
|
|
```c
|
|
int main(void) {
|
|
...
|
|
struct mg_mgr mgr; // Declare event manager
|
|
mg_mgr_init(&mgr); // Initialise event manager
|
|
mg_http_listen(&mgr, "http://0.0.0.0:8000", fn, NULL); // Setup listener
|
|
for (;;) {
|
|
mg_mgr_poll(&mgr, 1000); // Run an infinite event loop
|
|
}
|
|
...
|
|
}
|
|
|
|
// HTTP server event handler function
|
|
void fn(struct mg_connection *c, int ev, void *ev_data) {
|
|
if (ev == MG_EV_HTTP_MSG) {
|
|
struct mg_http_message *hm = (struct mg_http_message *) ev_data;
|
|
struct mg_http_serve_opts opts = { .root_dir = "./web_root/" };
|
|
mg_http_serve_dir(c, hm, &opts);
|
|
}
|
|
}
|
|
```
|
|
|
|
This HTTP server implements a simple REST API that returns current time:
|
|
```c
|
|
static void fn(struct mg_connection *c, int ev, void *ev_data) {
|
|
if (ev == MG_EV_HTTP_MSG) {
|
|
struct mg_http_message *hm = (struct mg_http_message *) ev_data;
|
|
if (mg_http_match_uri(hm, "/api/time/get")) {
|
|
mg_http_reply(c, 200, "", "{%m:%lu}\n", MG_ESC("time"), time(NULL));
|
|
} else {
|
|
mg_http_reply(c, 500, "", "{%m:%m}\n", MG_ESC("error"), MG_ESC("Unsupported URI"));
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
This event handler is for the MQTT client that subscribes to a topic
|
|
"aa/bb" and prints all messages that receives after that:
|
|
|
|
```c
|
|
static void fn(struct mg_connection *c, int ev, void *ev_data) {
|
|
if (ev == MG_EV_MQTT_OPEN) {
|
|
struct mg_mqtt_opts opts = {.qos = 1, .topic = mg_str("aa/bb")};
|
|
mg_mqtt_sub(c, &opts);
|
|
} else if (ev == MG_EV_MQTT_MSG) {
|
|
struct mg_mqtt_message *mm = (struct mg_mqtt_message *) ev_data;
|
|
printf("Topic: %.*s, Message: %.*s",
|
|
mm->topic.len, mm->topic.ptr,
|
|
mm->data.len, mm->data.ptr);
|
|
}
|
|
}
|
|
```
|
|
|
|
## Commercial use
|
|
- Mongoose is used by hundreds of businesses, from Fortune500 giants like
|
|
Siemens, Schneider Electric, Broadcom, Bosch, Google, Samsung, Qualcomm, Caterpillar to the small businesses
|
|
- Used to solve a wide range of business needs, like implementing Web UI
|
|
interface on devices, RESTful API services, telemetry data exchange, remote
|
|
control for a product, remote software updates, remote monitoring, and others
|
|
- Deployed to hundreds of millions devices in production environment worldwide
|
|
- See [Case Studies](https://mongoose.ws/case-studies/) from our respected
|
|
customers like [Schneider Electric](https://mongoose.ws/case-studies/schneider-electric/) (industrial automation), [Broadcom](https://mongoose.ws/case-studies/broadcom/) (semiconductors), [Pilz](https://mongoose.ws/case-studies/pilz/) (industrial automation), and others
|
|
- See [Testimonials](https://mongoose.ws/testimonials/) from engineers that integrated Mongoose in their commercial products
|
|
- We provide [Evaluation and Commercial licensing](https://mongoose.ws/licensing/), [support](https://mongoose.ws/support/), consultancy and [integration
|
|
services](https://mongoose.ws/integration/) - don't hesitate to [contact us](https://mongoose.ws/contact/)
|
|
|
|
|
|
## Security
|
|
|
|
We take security seriously:
|
|
1. Mongoose repository runs a
|
|
[continuous integration test powered by GitHub](https://github.com/cesanta/mongoose/actions),
|
|
which runs through hundreds of unit tests on every commit to the repository.
|
|
Our [unit tests](https://github.com/cesanta/mongoose/tree/master/test)
|
|
are built with modern address sanitizer technologies, which help to find
|
|
security vulnerabilities early
|
|
2. Mongoose repository is integrated into Google's
|
|
[oss-fuzz continuous fuzzer](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:mongoose)
|
|
which scans for potential vulnerabilities continuously
|
|
3. We receive periodic vulnerability reports from the independent security
|
|
groups like
|
|
[Cisco Talos](https://www.cisco.com/c/en/us/products/security/talos.html),
|
|
[Microsoft Security Response Center](https://www.microsoft.com/en-us/msrc),
|
|
[MITRE Corporation](https://www.mitre.org/),
|
|
[Compass Security](https://www.compass-security.com/en/) and others.
|
|
In case of the vulnerability found, we act according to the industry best
|
|
practice: hold on to the publication, fix the software and notify all our
|
|
customers that have an appropriate subscription
|
|
4. Some of our customers (for example NASA)
|
|
have specific security requirements and run independent security audits,
|
|
of which we get notified and in case of any issue, act similar to (3).
|
|
|
|
|
|
## Contributions
|
|
|
|
Contributions are welcome! Please follow the guidelines below:
|
|
|
|
- Sign [Cesanta CLA](https://cesanta.com/cla.html) and send GitHub pull request
|
|
- Make sure that PRs have only one commit, and deal with one issue only
|