In case you want to support HTTPS using OpenSSL, note that CivetWeb V1.13 pre-compiled Windows binaries (CivetWeb32.exe/CivetWeb64.exe) require OpenSSL 1.1.x - in case you still need OpenSSL 1.0.x, use CivetWeb32_10.exe/CivetWeb64_10.exe.
DocumentationSome selected documentation can be found in the zip archives containing the pre-compiled executables.
The full documentation to V1.13 can be found in the docs folder in the source zip archives.
In particular, the API documentation is only available in the source archives.
The most recent documentation is available in the Github repository:
https://github.com/civetweb/civetweb/tree/master/docs
Incompatibilities
Some API functions declared as legacy interface several years ago have been removed finally.
Up to V1.12, OpenSSL default version was V1.0.x, while V1.1.x had to be activated by setting a pre-processor define - from V1.13 the default is V1.1.x, while V1.0.x needs to be activated.
License
CivetWeb is free software and uses the MIT license.
You can download and use the binaries free of charge, for personal or commercial use.
You
may embed it into your application and even modify the source code.
Submitting your source code modification
is encouraged, but not required.
GitHub issues can also be used for feature requests and
discussions.
All submission are expected to be made
under the MIT license, authors will be added to the credits file
(automatically for GitHub pull requests, on request for other
contributions like comments with code snippets or issue detailed
reports).
If HTTPS support is required, an additional
transport layer security (TLS) libraries (like OpenSSL) has to be
installed. It is not shipped with CivetWeb, and must be downloaded and
installed separately. TLS libraries may have a different license.
On
the fly compression of static file is supported using zlib. Also zlib is
not shipped with CivetWeb and must be downloaded and installed
separately under a different license.