Drew Wells
8c4e0b3041
Added server_domain parameter to an init_ssl_domain callback which is called after the init_ssl callback
|
5 年之前 | |
|---|---|---|
| .. | ||
| _obsolete | 7 年之前 | |
| embedded_c | 5 年之前 | |
| embedded_cpp | 6 年之前 | |
| https | 7 年之前 | |
| multidomain | 7 年之前 | |
| rest | 6 年之前 | |
| ws_client | 6 年之前 | |
| README.md | 7 年之前 | |
README.md
Examples
Two examples show how to embed civetweb into a C (embedded_c) or a C++ (embedded_cpp) application. The C++ wrapper only offers a subset of the full C API, thus the C example is more complete than the C++ example. These examples were not designed with security in mind, but to show how the API can be used in principle. For more information, see the documentation. Some examples can also be found in the test folder (but they are less documented and adapted to the needs of the test framework).
In addition, there is one example how to configure a HTTPS server, to comply with modern security standards (https). It does not hold any source, but only a configuration file and some documentation how to use it.
The multidomain example demonstrates how to host multiple domains with different HTTPS certificates. It uses the standalone server (civetweb.c + main.c) and existing certificates.
The ws_client example shows how to use the websocket client interface to communicate with an (external) websocket server. It uses the "echo demo" of websocket.org, and only works if this server is reachable.
Some no longer maintained examples can be found in the "obsolete" folder. It is not guaranteed that they work in the current version - they are kept for reference, but might be removed in the future.
All examples are subject to the MIT license (unless noted otherwise) - they come without warranty of any kind.