commit | 54d8bb1354da6d4770d4d092f719f42e918f8bbf | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Mon Jul 20 13:28:59 2020 -0700 |
committer | James Feist <james.feist@linux.intel.com> | Mon Jul 20 20:39:12 2020 +0000 |
tree | c0690df30d16d3b251c4c02e37c7d32057df8c18 | |
parent | 1530261b40a9cbe77f349e4b4ddff427cf626b66 [diff] |
CancelDeadlineTimer after doWrite After doWrite we are no longer in a context where the user can keep the connection open. Cancel the timer. Tested: On a slow connection, still get responses Change-Id: I75a5bb32ccaaae173bb37fe9717b3e63e85c7131 Signed-off-by: James Feist <james.feist@linux.intel.com>
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
BMCWeb is configured by setting -D
flags that correspond to options in bmcweb/CMakeLists.txt
and then compiling. For example, cmake -DBMCWEB_ENABLE_KVM=NO ...
followed by make
. The option names become C++ preprocessor symbols that control which code is compiled into the program.
When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.
When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.