Resolve 413 errors by setting Flask's MAX_FORM_MEMORY_SIZE
limit to 20 MB
#823
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When evaluating the new, to-be-published YSO projects, the requests whose body exceeded 500 KB resulted to
413 Client Error: Request Entity Too Large for url
error, which did not happen on the previous projects update round on May.The cause was the limit introduced in Werkzeug 3.1.0 (pallets/werkzeug#2965):
In Flask 3.1 there is a new config setting
MAX_FORM_MEMORY_SIZE
to set a value for this limit.This PR uses the setting to
disable the limit altogetherincrease the value from the default (500 KB) to 20 MB.In any case, on production Annif should be run behind e.g. NGINX, which can be used to set request size limits more tightly.