10/31/2023 The server responded with a status of 413 request entity too large moodle scorm packageRead Now![]() We can "fix" this problem by turning off the request body inspection, which would disable this feature on this WAF. ![]() Apparently this limit has caused many other people problems as well, as there are 585 votes for a feature improvement to allow this configuration to be greated than 128 KB (link: ). During investigation, we have found out that the problem resides from the "max request body size" limit in the WAF (link explaining restrictions: ). The error is "413 Request Entity Too Large" that is being passed back from the Application Gateway. We have run into a problem with the way our REST service is passing data within its HTML call. The WAF policy only protects this one webapp. ![]() We are protecting the webapp with a WAF policy assigned to a listener on an Application Gateway v2. ![]() We have a webapp (a REST API service) that is sitting in a S1 App Service plan.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |