New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to set Request Size (Dapr: --http-max-request-size flag) #116
Comments
We are investigating and will report back |
Hey. Any updates on it? |
I think it would be great to add this option/parameter as annotation to dapr settings |
Any update on this? I am missing it as well for a production app (always receiving |
This is what I am seeing, which is preventing my production workload from working correctly :( sadly enough I can't compress images below 4 Mb @kendallroden any update? |
Any updates? We are blocked from moving forward until this flag becomes available. |
This feature is also crucial for me to move forward with container apps. The 4MB limit is very restricting. |
Thanks for letting us know I am checking with engineering |
Any updates? It seems that this gives the appearance of being supported via cli (https://learn.microsoft.com/en-us/cli/azure/containerapp/dapr?view=azure-cli-latest#az-containerapp-dapr-enable): az containerapp dapr enable --dapr-http-max-request-size 32 when i run this command the output seems to indicate success: { However, these values are not in the azure portal (see attachment). Also, when i look at the JSON for the container app overview in the portal, I only see: "dapr": { I will add that the dapr error for this is not properly surfaced in the logs. Container apps log the following error: while debugging locally, i see the more helpful dapr error: |
it works if you change the extension by using the command like this one |
That essentially is the command i am running: It shows up in the json settings if you change the API version to 2022-06-01-preview but it does not have an effect on the container - I still receive the error message with requests larger than 4MB. Presumably because this is in the API preview and not actually implemented in the deployed containers yet? |
that works if you use the right template (not a preview one). Just tested on my container apps. |
Can you elaborate a bit on what you mean by "right template"? Here is what i am using: This is not working (for me at least). perhaps i will try setting this to @2022-06-01-preview and see if that works. |
The feature is rolling out across CLI and portal hence why they are not in line yet |
closing due to availability |
Is there a way to set the
--http-max-request-size
flag? I got an app and am sadly enough triggering the body too large errorThe text was updated successfully, but these errors were encountered: