mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Dasgupta (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-3317) URL query string order is undefined
Date Thu, 21 Jan 2016 15:51:39 GMT

     [ https://issues.apache.org/jira/browse/MESOS-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhishek Dasgupta reassigned MESOS-3317:
----------------------------------------

    Assignee: Abhishek Dasgupta

> 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
>            Assignee: Abhishek Dasgupta
>            Priority: Minor
>              Labels: easyfix, mesosphere, newbie
>
> 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)

Mime
View raw message