commit | f79b7a502db253f6a862aa2cdf5308a7bf2b9070 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Wed Sep 22 19:04:29 2021 -0700 |
committer | Ed Tanous <edtanous@google.com> | Mon Oct 18 10:23:50 2021 -0700 |
tree | 3ab9fcd35ae5477ac78cacd3cbacdce749ac260d | |
parent | 5edbe947bc474743763b34a89bacf973645fefab [diff] |
Deduplicate url parsing code In the current model, URLs get parsed twice, once to satisfy the authenticate method, and once again later to satisfy the handle() call. This commit deduplicates the parsing. This is wasteful, and as of the previous commit, unnecessary. Specifically, it moves the actual parsing into the request object, and adds a target() method to explicitly set a url. This deduplicates the code that was in http_connection, and centralizes it in request, where it should really belong. Tested: curl --insecure "https://192.168.7.2/redfish/v1" Returns the redfish v1 resource curl --insecure "https://192.168.7.2/redfish/v1/Systems" Returns 401 unauthorized curl --insecure --user root:0penBmc "https://192.168.7.2/redfish/v1/Systems" returns the SystemsCollection Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ie7ee2d9a9a51bf21c03793b35730e7a0ca82623a
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.