ContentCachingResponseWrapper.setHeader does not handle null value properly. #34465
Assignees
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: backport
An issue that is a backport of another issue to a maintenance branch
type: bug
A general bug
Milestone
Comments
github-actions
bot
added
in: web
bclozel
added a commit
that referenced
this issue
Feb 21, 2025
Prior to this commit, calling `setHeader` on the response wrapper would have a separate code path for the "Content-Length" header. This did not support calls with `null` values and would result in an exception. This commit ensures that the cached content length value is reset in this case and that the call is forwarded properly to the superclass. Fixes gh-34465
|
Fixed via ccf4b02 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Backport of gh-34460
The text was updated successfully, but these errors were encountered: