commit | 418b934abdf346a805816ad2d701dc070dbc08a0 | [log] [tgz] |
---|---|---|
author | P Dheeraj Srujan Kumar <p.dheeraj.srujan.kumar@intel.com> | Tue Jul 13 03:36:20 2021 +0530 |
committer | P Dheeraj Srujan Kumar <p.dheeraj.srujan.kumar@intel.com> | Fri Jul 30 20:19:45 2021 +0530 |
tree | b09d8ee620b60129cdea7fd3aca8dded2f7f066e | |
parent | 42cbb517ffc573e9ec39077f5a59c1443e0ef9ea [diff] |
Fix Klocwork Issue - Dereferencing iterators In the current implementation, the iterator "paths" is being checked for end(), but is being dereferenced in the code even if the iterator is being equal to end(). This commit fixes this issue by returning if iterator equals end() and performing the remaining tasks otherwise. Tested: - websocket_test.py Passed - When there was no "paths" provided from the script, the connection was closed with "Unable to find paths in json data" message. Signed-off-by: P Dheeraj Srujan Kumar <p.dheeraj.srujan.kumar@intel.com> Change-Id: I8651768c057971367dc35b8fd7ae168ab40e3453
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 coverage -C builddir test
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.