commit | a8086647b103f55116ce4c872e1455ebf1f3e346 | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Tue Jan 07 09:53:20 2020 -0800 |
committer | James Feist <james.feist@linux.intel.com> | Wed Jan 08 17:20:15 2020 +0000 |
tree | 8d0d792afb8047f83777cdb404929d4f82d3b7b0 | |
parent | 8988dda41319950476ebb146df06c2e7b3fbf44d [diff] |
Revert "Connection and websockets fixes" This reverts commit c00500bcb9c5145f5cacb78bbe3dd694fb85ba0a. Reason: Makes image upload fail Tested: Image upload works again requests.post( 'https://{}/redfish/v1/UpdateService'.format(args.address), data=file.read(), verify=False, auth=(args.username, args.password)) Change-Id: Iaf780d052d98accdead32e87f468002f5141b19a 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 prime256v1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.