You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our nginx config specifies a limit of 100 MB on the size of the request body. Frontend and Backend implement similar limits:
Before sending a file (e.g., a form attachment), Frontend checks that the file doesn't exceed 100 MB. If it does, then Frontend won't even attempt to send the file and will show an error message (old discussion: Uploading a large media file for draft form fails #178).
Backend rejects JSON requests whose body is more than 250 kB. The exception is creating entities in bulk, in which case a request body of up to 100 MB is accepted.
Today we discussed the possibility that a user might try to change the nginx config, but wouldn't know to change Frontend as well. The Frontend code mentions the nginx config in a comment, but the nginx config doesn't mention Frontend.
Probably the best way to ensure that everything is consistent is to have Docker pass the limit to nginx, Frontend, and probably also Backend. Maybe the limit could be passed as an env variable.
The text was updated successfully, but these errors were encountered:
matthew-white
changed the title
Consistency between nginx and Frontend limits on request body size
Consistency of limits on request body size
Apr 13, 2024
Our nginx config specifies a limit of 100 MB on the size of the request body. Frontend and Backend implement similar limits:
Today we discussed the possibility that a user might try to change the nginx config, but wouldn't know to change Frontend as well. The Frontend code mentions the nginx config in a comment, but the nginx config doesn't mention Frontend.
Probably the best way to ensure that everything is consistent is to have Docker pass the limit to nginx, Frontend, and probably also Backend. Maybe the limit could be passed as an env variable.
The text was updated successfully, but these errors were encountered: