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
Describe the bug
Currently, if we upload a file of size more than 2.5 MB in unrestricted file upload vulnerability, we will see the 413 Request Entity Too Large error in response. We are looking to not throw errors from openresty and let the vulnerable applications handle it the large request entity
To Reproduce
Go to Unrestricted File Upload Vulnerability
Click on Level1 and upload an image file
Go to developer tools and see the network tab for errors and it will show 413 error.
Expected behavior
OpenResty should not throw 413 errors and let the application throw the error. So we need to remove the limitation from openresty or make it 100MB of size.
Describe the bug
Currently, if we upload a file of size more than 2.5 MB in unrestricted file upload vulnerability, we will see the
413 Request Entity Too Large
error in response. We are looking to not throw errors from openresty and let the vulnerable applications handle it the large request entityTo Reproduce
Expected behavior
OpenResty should not throw 413 errors and let the application throw the error. So we need to remove the limitation from openresty or make it 100MB of size.
Solution
Follow the below link for adding configuration to not restrict the file-upload: https://www.keycdn.com/support/413-request-entity-too-large#nginx
The text was updated successfully, but these errors were encountered: