Files
cpp-project-template/third_party/prometheus/3rdparty/civetweb/examples/https
tqcq c68893bace
Some checks failed
sm-rpc / build (Debug, aarch64-linux-gnu) (push) Failing after 29s
sm-rpc / build (Debug, arm-linux-gnueabihf) (push) Failing after 16s
sm-rpc / build (Debug, host.gcc) (push) Failing after 11s
sm-rpc / build (Debug, mipsel-linux-gnu) (push) Failing after 12s
sm-rpc / build (Release, aarch64-linux-gnu) (push) Failing after 11s
sm-rpc / build (Release, arm-linux-gnueabihf) (push) Failing after 11s
sm-rpc / build (Release, host.gcc) (push) Failing after 12s
sm-rpc / build (Release, mipsel-linux-gnu) (push) Failing after 16s
feat add spdlog
2025-08-22 18:22:57 +08:00
..
2025-08-22 18:22:57 +08:00
2025-08-22 18:22:57 +08:00

HTTPS Server configuration example

This directory contains an example civetweb.conf configuration file for a secure HTTPS server. You can run a HTTPS server without most of the options there - only ssl_certificate and one port (e.g., 443s) in listening_ports is required. The default settings will work, but not comply with up to date security standards. It is somewhat debatable what "up to date security" means - you can use the following web sites to run tests:

Instructions to run the test and to adapt the configuration can be found civetweb.conf. You can test this configuration directly with the standalone server, or you can take the settings and add it into your embedding code.

Note: I do not take any warranty or liability for this configuration, or for the content of any linked web site.