-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
100MB limit raising in actix-multipart example code is ignored #3549
Comments
It seems that the multipart has a total limit of 50 MiB (hardcoded here) and in memory limit of 2 MiB by default. Try increasing them together. |
To correct the example we need to configure the extractor to accept forms up to 100MB when creating the App:
Here it worked as intended. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
53.1MB test file should be accepted as an upload by the example with a 100MB limit, like the 8MB test file was and like it was when using the
FromRequest
example code from actix_multipart::Multipart with a suitably high global limit.Current Behavior
If testing using curl,
Payload error
is returned.When logging is plumbed in,
DEBUG Error in response: Payload(Overflow)
is the result.Also using
MultipartFormConfig
to attempt to raise the limit, as "Note: the form is also subject to the global limits configured usingMultipartFormConfig
." seems to indicate to be necessary, has no effect.Possible Solution
Make it work as described.
Steps to Reproduce (for bugs)
cargo new actix-test && cd actix-test && cargo add actix-web actix-multipart && cargo add serde --features derive
src/main.rs
cargo run
curl -v --request POST --url http://localhost:8080/videos -F 'json={"name": "Cargo.lock"};type=application/json' -F file=@./some_file_over_50_megs
Context
If this isn't fixed, I have to NIH the exact same functionality on top of actix_multipart::Multipart to achieve my goals.
Your Environment
rustc -V
): rustc 1.83.0 (90b35a623 2024-11-26)The text was updated successfully, but these errors were encountered: