commit | 18c94c3554002fc2242f268b9eb449ec660ee92b | [log] [tgz] |
---|---|---|
author | Adriana Kobylak <anoo@us.ibm.com> | Mon Jan 06 12:14:46 2020 -0600 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Tue May 26 19:41:52 2020 +0000 |
tree | 1bb9ebf97ed361bab4f390b0a6c81d21da0ac6a2 | |
parent | cd80a617f939c24f7f541ad0833d07c91be5ca5a [diff] |
bmcweb: Set BMCWEB_HTTP_REQ_BODY_LIMIT_MB to 400 By default, bmcweb limits the size of the http request body to 30MB to limit a DOS attack based on a large file size. OpenBMC supports "System" or "bundled" images that contain two or more firmware images. For OpenPOWER systems, these include the BMC and Host firmware making the resulting image greater than the default 30MB. A configurable option (BMCWEB_HTTP_REQ_BODY_LIMIT_MB) was added to bmcweb to be able to change this limit: https://github.com/openbmc/bmcweb/commit/0e1cf26b1cd98e0ec069e6187434fcabf1e9c200 Set this option to an arbitrary size of 400MB since the size of /tmp for currently supported OpenBMC systems is ~460MB and /tmp is where the uploaded image files are stored. Change-Id: Ieec1e6f617af42f01b03f20244c68839c09f6951 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
This layer provides support for the BMC firmware on OpenPOWER reference platforms, and/or a base upon which to create a BMC firmware implementation on any POWER system.
This layer depends on: URI: git://git.openembedded.org/openembedded-core layers: meta branch: master revision: HEAD URI: https://github.com/openbmc/meta-phosphor branch: master revision: HEAD URI: https://github.com/openbmc/meta-aspeed branch: master revision: HEAD
More information on OpenPOWER can be found here.
meta-openpower patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.
Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-openpower is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.
Patch checklist. Please ensure patches adhere to the following guidelines:
For questions or help please come join us on the mailing list or in IRC.