Affects: \5.3.3
When a POST request is made using application/x-www-form-urlencoded and I convert the body to a String, the order of the request parameters is changed because the body is created by ContentCachingRequestWrapper.writeRequestParametersToCachedContent rather than the original body. This causes me to be unable to validate requests of this type using a HMAC of the requested content.
Comment From: mjaggard
Hmm, having looked it seems that Jetty has decoded the values into an unsorted & unordered Map so it's not possible for Spring to put them back together in the correct order - and it uses an iterator which will work for any servers that use an orderd map.
The current behaviour is incorrect but the Spring part of the implementation is correct.