Request for comments: C++ embedded webserver
benh at kernel.crashing.org
Thu Dec 21 11:34:14 AEDT 2017
On Tue, 2017-12-19 at 04:07 +0000, Tanous, Ed wrote:
> I’m looking for comments on a code review that’s been outstanding.
> One of the large pushes we’ve made is to attempt to make the web
> server more efficient, and add capabilities that comprehend long term
> needs of OpenBmc. One key that wasn’t made clear in the commit
> message is that it includes the basic redfish implementation that (we
> hope) should be extensible to the full redfish specification in the
> short term future.
There are plenty of existing HTTP server implementations out there
that are well maintained, any reason why we should invent another one
Also, do we really think perpetuating the use of that monstruosity
masquerading as a programming language that is C++ is a good idea ?
> We would very much appreciate comments to see if we can move this forward.
> The following description is pulled from the readme.
> # OpenBMC webserver #
> This component attempts to be a "do everything" embedded webserver for openbmc.
> ## Capabilities ##
> At this time, the webserver implements a few interfaces:
> + Authentication middleware that supports cookie and token based authentication, as well as CSRF prevention backed by linux PAM authentication credentials.
> + An (incomplete) attempt at replicating phosphor-dbus-rest interfaces in C++. Right now, a few of the endpoint definitions work as expected, but there is still a lot of work to be done. The portions of the interface that are functional are designed to work correctly for phosphor-webui, but may not yet be complete.
> + Replication of the rest-dbus backend interfaces to allow bmc debug to logged in users.
> + An initial attempt at a read-only redfish interface. Currently the redfish interface targets ServiceRoot, SessionService, AccountService, Roles, and ManagersService. Some functionality here has been shimmed to make development possible. For example, there exists only a single user role.
> + SSL key generation at runtime. If an RSA key and cert pair are not available to the server at runtime, keys are generated using the openssl routines, and written to disk.
> + Static file hosting. Currently, static files are hosted from the fixed location at /usr/share/www. This is intended to allow loose coupling with yocto projects, and allow overriding static files at build time.
> + Dbus-monitor over websocket. A generic endpoint that allows UIs to open a websocket and register for notification of events to avoid polling in single page applications. (this interface may be modified in the future due to security concerns.)
More information about the openbmc