Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimize content type parsing in ServletServerHttpResponse #32361

Closed
sdeleuze opened this issue Mar 4, 2024 · 0 comments
Closed

Optimize content type parsing in ServletServerHttpResponse #32361

sdeleuze opened this issue Mar 4, 2024 · 0 comments
Assignees
@sdeleuze
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone
6.1.5

Comments

@sdeleuze
Copy link
Contributor

sdeleuze commented Mar 4, 2024

The multiple HttpHeaders#getContentType invocations in ServletServerHttpResponse#writeHeaders should be turned into a single one.
@sdeleuze sdeleuze added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Mar 4, 2024
@sdeleuze sdeleuze added this to the 6.1.5 milestone Mar 4, 2024
@sdeleuze sdeleuze self-assigned this Mar 4, 2024
@sdeleuze sdeleuze changed the title Optimize content type parsing Optimize content type parsing in ServletServerHttpResponse Mar 4, 2024
sdeleuze added a commit to sdeleuze/spring-framework that referenced this issue Mar 4, 2024
@sdeleuze
Optimize content type parsing
129af56 
This commit avoids calling HttpHeaders#getContentType multiple times in
ServletServerHttpResponse#writeHeaders.

Closes spring-projectsgh-32361
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdeleuze sdeleuze

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.5
Development

No branches or pull requests
1 participant
@sdeleuze