Allow a max payload size of 512MB
It's probably not a great idea to allow that big of a payload on the
BMC, but it was supported before, so lets push that discussion to
another time.
Tested:
code builds. Attempting to resolve CI, which will test itself.
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I1f9e489075857621f5295d4870dea9f5767666f0
diff --git a/meson_options.txt b/meson_options.txt
index e808f46..1b148f4 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -17,7 +17,7 @@
option('bmcweb-logging', type : 'feature', value : 'disabled', description : 'Enable output the extended debug logs')
option('mutual-tls-auth', type : 'feature', value : 'enabled', description : '''Enables authenticating users through TLS client certificates. The insecure-disable-ssl must be disabled for this option to take effect.''')
option('ibm-management-console', type : 'feature', value : 'disabled', description : 'Enable the IBM management console specific functionality. Paths are under \'/ibm/v1/\'')
-option('http-body-limit', type: 'integer', min : 0, max : 30, value : 30, description : 'Specifies the http request body length limit')
+option('http-body-limit', type: 'integer', min : 0, max : 512, value : 30, description : 'Specifies the http request body length limit')
# Insecure options. Every option that starts with a `insecure` flag should
# not be enabled by default for any platform, unless the author fully comprehends