spring-projects / spring-projects/spring-boot
Expose Tomcat response output stream buffer size as a configuration property
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
After some recent changes in Spring MVC (7.0.6) Tomcat will write the content-length header for us if we write a response body that fits in its output stream buffer. The default size is 8192 bytes, which is completely arbitrary, and some applications (where they often return JSON results slightly larger than that, for instance) would benefit from being able to change the value.
Jetty behaves the same way, and it probably has the same opportunity to configure the buffer size.
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 locating Spring MVC's response handling and the Tomcat output stream buffer configuration, then check whether the corresponding Jetty behavior is exposed similarly. Done means applications can configure the response output stream buffer size and the behavior works for response bodies near or above the default 8192-byte threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100