| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Change-Id: I5ca16c6fa7bc616bfa9bc41c4f86d32fd92b0287
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
- This commit would switch the equivalent extra options that
are used by bmcweb meson build
(From meta-openpower rev: e81f2e3dae2a7e8f1ca2df631fcc4ca05ac93ca2)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ib7cdfb2950f4f028949251233b6f935b300f26cd
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would remove BMCWEB_ENABLE_LOGGING_MW option
as it does not exist in bmcweb in its current state.
(From meta-openpower rev: f819ca47bc1bf401c988459bc519e8a313390bd7)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I8d1333dcf7968a7a6b04d3c829446d60c525fd05
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
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.
(From meta-openpower rev: 18c94c3554002fc2242f268b9eb449ec660ee92b)
Change-Id: I66dda4fa598db0d5ea8216e386d8e90c544e6bc2
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Upstream bmcweb is in recipes-phosphor/interfaces, not
recipes-phosphor/bmcweb. Move to match.
(From meta-openpower rev: 7e685d7edb9e030217d4980aac7397102e0e3fa1)
Change-Id: I04735e31b4f983a15bd07a1dfef5651e6b2d08b6
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
