[placement][ptg] JSON payload for GET /a_c
ed at leafe.com
Mon Apr 8 19:20:39 UTC 2019
On Apr 8, 2019, at 12:58 PM, Sean Mooney <smooney at redhat.com> wrote:
> technically i belive its not standards compliant to have a get
> request contain a body. some implemeention allow it but
> if you use a body in a get request i belive it causes issue with loadblancer/
> proxy servers so if we do support a query in a body it will have to be a post or put
> depending on how we choose to model it.
GET *can* have a body, but it is not required to be honored. Query strings don’t have a specified length limitation, but different clients and servers may impose such a limit. It is generally considered that query strings longer than 2K characters should be avoided, so if the query is so complex as to surpass that limit, we may need to move to using a body to hold all that information.
I don’t put much weight into the elegance argument. These queries are going to be programmatically generated, and creating parts of a query string is really no more or less elegant than creating parts of a a JSON blob.
-- Ed Leafe
More information about the openstack-discuss