Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,876 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 0%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Hi, did you every find a resolution for this?
Azure WEB API with large payload
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 76%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Amar-Azure-Practice
656
Reputation points
Hi All,
I have deployed the Asp.net core REST service to Azure as WEB APP.
When I tested the service in n local environment in Visual Studio, the service is working fine with large payload.
When service is running in Local it is accepting the large payload (500 MB size) and responding with large payload (500 MB ).
After deploying this service to Azure Web APP, service is not working with large payload, for smaller payloads service is working fine, but for large payloads service is throwing 500 Server internal error.
I have added the 'RequestSizelimits' on the action methods to support large payload.
but still not responding with large payload messages
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
SnehaAgrawal-MSFT 18,286 Reputation points2021-10-08T18:05:13.557+00:00 Thanks for reaching here! If you are using ASP.NET Core 2.0.0? If so, As its mentioned here
Starting in ASP.NET Core 2.0.0, both Kestrel and HttpSys will be enforcing a a 30MB (~28.6 MiB) max request body size limit.
If the request body size exceeds the configured max request body size limit, the call to Request.Body.ReadAsync will throw an IOException. If this exception is uncaught, Kestrel will respond with a 413 Payload Too Large response and HttpSys will respond with a generic 500 Internal Server Error response.
This limit can be changed either globally or on a per-request basis, and is disabled for Kestrel running behind IIS where the normal web.config limit still applies.
Let us know.
-
Amar-Azure-Practice 656 Reputation points
2021-10-14T18:02:47.34+00:00 Hi Sneha,
I have verified the application running on local development (Running server application in Visual Studio) and it worked well with 500 MB payload, after I have promoted code to Azure after that it is not working with 500 MB file for smaller files it working fine.
for larger file we are getting 500 Internal server error.
Below code block I have added to support large payload and still I don't have luck on it.
in the webBuilder section i have added Limits.MaxResponseBuffersize=250000000
-
SnehaAgrawal-MSFT 18,286 Reputation points
2021-10-20T08:35:14.317+00:00 Apologize for late response on this! Could you please confirm on which tier/sku you have deployed your web app?
Sign in to comment