commit | fe30672809d9dcf83f6cab821d02650b250664b9 | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Thu Mar 12 16:32:08 2020 -0700 |
committer | James Feist <james.feist@linux.intel.com> | Tue Mar 17 16:33:52 2020 +0000 |
tree | fafba78ccfd37847fe927057c30213979bbff46e | |
parent | f857e9ae6f6e7d567462f32cb5d9d3a7b581535e [diff] |
Task: Add payload support This adds the payload values to task responses. Tested: passed validator Change-Id: I50467e28ce8142d198f916ea0c63bd413edcd524 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.