Timeline for handle duplicate values for Spring @RequestParam
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2023 at 15:07 | comment | added | Martin P. | In my case for spring-web 5.3.25 it's duplicated for no reason... | |
Jul 6, 2020 at 18:53 | answer | added | John | timeline score: 1 | |
Apr 24, 2014 at 15:10 | vote | accept | Alex Wittig | ||
Apr 3, 2014 at 14:32 | answer | added | Alex Wittig | timeline score: 4 | |
Apr 2, 2014 at 19:21 | comment | added | Alex Wittig |
If you mean a servlet Filter rather than a Spring HandlerInterceptor then yes. I feel like a solution should exist higher than the servlet level though.
|
|
Apr 2, 2014 at 18:06 | comment | added | acdcjunior |
Yeah, it is not possible to change the attributes. To achieve what you want, you have to, in the interceptor, wrap the HttpServletRequest in a HttpServletRequestWrapper (see: stackoverflow.com/questions/1413129/… ).
|
|
Apr 2, 2014 at 17:23 | comment | added | Alex Wittig |
A HandlerInterceptor was my first thought too, but you can't modify parameters from there.
|
|
Apr 2, 2014 at 17:20 | comment | added | acdcjunior |
Strictly speaking, ?param=value¶m=value is not the same as ?param=value only. So if Spring did that "merging" in any way, it would be an invalid behavior. So, yeah, you have to implement it yourself. Be it through a new ...ArgumentResolver or ...Interceptor .
|
|
Apr 2, 2014 at 16:43 | answer | added | geoand | timeline score: 1 | |
Apr 2, 2014 at 16:35 | history | edited | Alex Wittig | CC BY-SA 3.0 |
added 28 characters in body
|
Apr 2, 2014 at 16:21 | history | asked | Alex Wittig | CC BY-SA 3.0 |