in Azure Functions (C#, Runtime.NET6, HttpTrigger) When receiving an Http Request (POST/Type JSON), the parameters of the body part are
A 413 error (request entity too large) occurs when the base 64 string (image itself encodes about 85KB).
Azure Functions uses a standard plan.
I want to receive the Base64 string in Azure Functions in POST Request and display the contents in log.LogInformation.
The questioner has left and doesn't seem to want to write down how it was solved.
So, I didn't answer the question of what I thought when I saw this thread, but I'll write it down below.
Some articles that google with azure function requestity too large show that CORS configuration avoids problems.
[FIXED] Azure function failing: "statusCode":413, "message": "request entity too large"
I don't understand why CORS is involved, but I thought it would be good to try it.
All I can think of is whether the actual size of the JSON string I sent is too large.
By default, when a client sends a JSON string to an ASP.NET web service method, the length of the JSON string that can be sent to the server is limited to 102,400 characters.
See the article below for more information.
I don't know Azure Functions, but there may be similar restrictions.
© 2023 OneMinuteCode. All rights reserved.