-
Notifications
You must be signed in to change notification settings - Fork 38k
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
Consistent handling of null header values in HttpHeaders [SPR-17588] #22120
Comments
Juergen Hoeller commented The 5.0-introduced |
Juergen Hoeller opened SPR-17588 and commented
The specific header setter methods in
HttpHeaders
useMultiValueMap.set/add
for populating the underlying data structure. Unfortunately,null
values are mostly being stored asnull
entries in single-entry lists for a header, or sometimes being skipped altogether. While the end result (e.g. in a populated server response) usually ignoresnull
header values anyway and allgetFirst
access returnsnull
just like it would in case of a non-existing header as well, some user-level accessor methods (e.g.HttpHeaders.getCacheControl()
return a bogus text representation in case of anull
value. Let's streamline this for 5.1.4 as a continuation of theHttpHeaders
refactoring in the 5.1.x line.Affects: 5.1.3
Reference URL: jetty/jetty.project#1116
Issue Links:
Referenced from: commits 5bbbc82
The text was updated successfully, but these errors were encountered: