Handle oversized plugins #70
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix for #67
The feature already exists but is not triggered correctly because the NGINX client_max_body_size is set 20M and the max size allowed by the validator is 25Mb.
The suggestion here is to keep the validators limit and increase the NGINX client_max_body_size to 30M. In this case, the validator will raise the error explicitly on the upload page when the plugin size limit is reached without being handled by NGINX and generate the Cloudflare error.
Additional changes:
Publish a plugindocs to include this limitApproval process(ported from the old version)