commit | c02a74f8504bc42d6e03721aa426d043b6658820 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Wed May 11 14:46:44 2022 -0700 |
committer | Ed Tanous <ed@tanous.net> | Mon May 16 16:44:46 2022 +0000 |
tree | e559146f69dc5f888d5ceef159354526edf4d1e4 | |
parent | d3355c5cdd4ce4e39df7d2f424eb4a60fee16731 [diff] |
Return OData.Version with responses The Redfish specification section 8.1 lists header values that should be returned from responses. It lists OData.Version: 4.0 as required in this same section. Implement this to the specification. Tested: Redfish protocol validator RESP_HEADERS_ODATA_VERSION test now passes. curl --vvv https://$bmc/redfish/v1 shows Odata.Version header set in response. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Id02ec218299524905fbd91cb161bfe727a51fc65
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/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja -C builddir test ninja -C builddir coverage
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.