impossible to restore the order of parameters after using QueryStringDecoder

Expected behavior

Order of parameters at query string doesn’t change

Actual behavior

After using such classes as QueryStringDecoder the order of query string parameters changes

if any external library uses you decoder they will have a structure that will break the order of parameters before: param1=1&param2=2&param1=3 after: param1=1&param1=3&param2=2

Is it so neccessary to use such structure to store the parameters: Map<String, List<String>> because it is impossible to restore the order after we put parameters into value list here(addParams method of QueryStringDecoder.class):

 List<String> values = params.get(name);
 if (values == null) {
      values = new ArrayList<String>(1);  // Often there's only 1 value.
      params.put(name, values);
  }
 values.add(value);

[Scottmitch]

Can you clarify what exactly is “broken”? What depends upon the order or query parameters and why can’t you use QueryStringDecoder.uri() for your use case?

i think that the decision to depend from order or not should depends from developers.

If there is no requirement to preserve order defined in any RFC your application shouldn’t depend upon a 3rd party library providing this functionality. If you want/need this behavior (and it is not defined in an RFC) I suggest you implement this behavior in your application.

[Scottmitch]

but as i know proxy server shouldn’t modify calls that go through it.

I would expect a proxy should preserve the semantics of the protocol. This doesn’t necessarily mean what comes in is exactly what goes out.

I will close this issue now. If you find a spot in the HTTP related RFCs which describes the behavior you request please re-open and provide a link.