spring-cloud / spring-cloud/spring-cloud-gateway
Status of MultipartFile upload requests in Spring Cloud Gateway MVC
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
There are a number of bugs and open issues around the use of Multipart File uploads via the Spring Cloud Gateway MVC implementation, and there seems to be multiple workarounds or ways to possibly avoid the issue. The docs do not seem to have any information about how to properly and efficiently use Multipart File uploads in either the MVC or the WebFlux implementations. The result is that the current state of File Upload support in Spring Cloud Gateway is VERY confusing and unclear.
The old Netflix-Zuul 1 version of Spring Gateway did have specific documentation on how to utilize File uploads via the gateway, and for applications that needed robust file upload support (including for larger files), that was helpful and was quite successful.
Since it is an important feature for many applications, and configuring and utilizing file uploads CAN be a performance issue or even can cause outages for larger files, having a clear set of docs or information on how to best support file upload features in Spring Cloud Gateway would be advisable.
Even just have an issue that is pinned that highlights the known bugs/issues with using Multipart File would be beneficial to the community while the outstanding issues are resolved.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Spring Cloud Gateway MVC and WebFlux documentation, then compare it with the cited Netflix-Zuul 1 file-upload guidance and the known multipart issues. Done means publishing clear, efficient guidance for multipart uploads, including larger files, or a pinned summary of the current bugs and workarounds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100