-
Bug
-
Resolution: Fixed
-
Neutral
-
5.2.4
-
None
-
Any Browser tested (Firefox, IE)
It is fine to sort the parameters themselves, those can arrive in any order, and the order is not defined in any specification.
But the parameter values, when arrays, cannot be sorted. Even if you say that your cache filter does not support the order of the values (hard to understand, but ok), it is simply not ok that the cache filter performs the sorting in place, thus modifying the order for all subsequent code dealing with the request. The correct order cannot be recovered.
- caused by
-
MAGNOLIA-5215 CLONE - URL's with multiple times a parameter with the same name cause cache collisions.
- Closed
- clones
-
MAGNOLIA-5808 CacheFilter still modifying parameters
- Closed
- relates to
-
MGNLCACHE-56 Semicolons doubled by CacheFilter
- Closed