You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jan Schlicht (JIRA)" <ji...@apache.org> on 2015/08/26 10:52:45 UTC

[jira] [Created] (MESOS-3317) URL query string order is undefined

Jan Schlicht created MESOS-3317:
-----------------------------------

             Summary: URL query string order is undefined
                 Key: MESOS-3317
                 URL: https://issues.apache.org/jira/browse/MESOS-3317
             Project: Mesos
          Issue Type: Wish
          Components: libprocess
            Reporter: Jan Schlicht
            Priority: Minor


A `process::http::URL` instance has its query strings stored in a hashmap. Stringifying the instance will use the order defined by the hash function to order the query strings. This order depends on the concrete implementation of the hash function.  
A well defined query string order (e.g. in alphabetical order) may be important for bot detection. If the query strings should be in an alphabetic order, multiple solutions are possible:
1. Use map instead of hashmap for defining query string in URLs
2. Order the query strings while creating the URL string
3. Provide an own string hash function that guarantees a certain order



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)