Fix filtered HTTP headers in data binding
Prior to this commit, several common HTTP headers were ignored from the data binding process when collecting property values, in gh-34039 and gh-34182. This commit completes the initial enhancement by ensuring that the default header predicate is also considering cases where constructor binding is applied and the Java type has a lowercase variant of the HTTP header name to filter. Fixes gh-34292
This commit is contained in:
@@ -224,7 +224,7 @@ class InitBinderBindingContextTests {
|
||||
|
||||
@ParameterizedTest
|
||||
@ValueSource(strings = {"Accept", "Authorization", "Connection",
|
||||
"Cookie", "From", "Host", "Origin", "Priority", "Range", "Referer", "Upgrade"})
|
||||
"Cookie", "From", "Host", "Origin", "Priority", "Range", "Referer", "Upgrade", "priority"})
|
||||
void filteredHeaders(String headerName) throws Exception {
|
||||
MockServerHttpRequest request = MockServerHttpRequest.get("/path")
|
||||
.header(headerName, "u1")
|
||||
|
||||
Reference in New Issue
Block a user