commit | 5070c7ec48e8724cfd31b9a2464ea21a04db6962 | [log] [tgz] |
---|---|---|
author | Abiola Asojo <abiola.asojo@ibm.com> | Tue Jul 29 19:00:04 2025 +0000 |
committer | Gunnar Mills <gunnar@gmills.xyz> | Mon Aug 18 18:40:45 2025 +0000 |
tree | 3bb8f0cb812dfcbea4e60e87a98a6d3b5f9443ae | |
parent | d3616d13fbd236204477312ddf2e9913a7001010 [diff] |
Fix 204/304 incorrectly tracing CRITICAL message Resolve tracing of CRITICAL message on 1xx, 204(no-content) and 304(not modified) when there is no body in the response. The code is changed to check that 1xx, 204 and 304 response with payloadsize of 0 will not trace the CRITICAL message. Removed setting of no_content on PATCH that was being done before other functions are called. Tested: Used the following commands to check that the CRITICAL message is no longer being traced for no-content and not modified response with no body. 204 no-content ``` curl -k -H "Content-Type: application/json" \ -d '{"PowerRestorePolicy":"LastState"}' \ -X PATCH https://${bmc_ip}/redfish/v1/Systems/system ``` ``` curl -k -H "Content-Type: application/json" \ -H "X-Auth-Token: $bmc_token" -X PATCH \ -d '{"LocationIndicatorActive":true}' \ https://${bmc_ip}/redfish/v1/Managers/bmc ``` 304 not modified ``` curl -k -i https://${bmc_ip}/redfish/ --etag-save etag.out \ -H 'If-Modified-Since: Tue, 21 Nov 2050 08:00:00 GMT' HTTP/1.1 200 OK Allow: GET . . . ETag: "B3A9EAA1" Content-Type: application/json Date: Thu, 14 Aug 2025 22:07:27 GMT Content-Length: 26 ETAG=`cat etag.out`; echo $ETAG curl -k -i https://${bmc_ip}/redfish/ -H "If-None-Match: ${ETAG}" HTTP/1.1 304 Not Modified Allow: GET . . . ETag: "B3A9EAA1" Date: Thu, 14 Aug 2025 22:16:27 GMT Content-Length: 0 ``` Change-Id: I98cc096c1f7e506687d4a6bf5a2e51b2231c0d68 Signed-off-by: Abiola Asojo <abiola.asojo@ibm.com>
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL. Http1 and http2 are supported using ALPN registration for TLS connections and h2c upgrade header for http connections.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson setup builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects
.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data
namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb supports various forms of http compression, including zstd and gzip. Client headers are observed to determine whether compressed payloads are supported.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.