Specify expected file size in the manifest
As of the last Sitevision release (Cloud and On-prem), zero is accepted as valid value for the maxUploadSizeInMB in the manifest. From now on we recommend to always specify maxUploadSizeInMB.
The manifest has support for the maxUploadSizeInMB property that specifies the max accepted file size the app expects to receive and process. The last released Cloud (2023.11.1.2) and On-prem (2023.10.1.4) versions of Sitevision now supports zero as a valid value, so now there are really no excuses to not always specify maxUploadSizeInMB.
The reason to always specify the maxUploadSizeInMB property is twofold:
- Documentation. The manifest explicitly states whether or not the app expects any request file data.
- Validation and control. A non-zero value bounds the size of expected request file data, i.e. blocks unreasonably large files to be handled by the app.
Apps with non-payload routes (GET, DELETE)
WebApps and RESTApps that only use non-payload routes should always specify maxUploadSizeInMB as zero. It will clearly state that "this app does not expect file data in any request".
Apps with potential payload routes (POST, PUT, PATCH)
WebApps and RESTApps that use payload routes should specify the maxUploadSizeInMB value according to the implemented behaviour of the app.
The app should specify zero as value if no route expects any file data in the request.
The app should specify a reasonable value if any route expects file data in the request.