Hi guys,
My comments are here:
1. GET with body vs. POST
· POST is not cache-able by the browser which means that those queries will be executed each time. In some cases we would like to cache them for short period but there will be no possibility for this using POST
In the scenario we’re proposing, POST would only be used for “complex” queries, i.e. ones that are more specific and therefore less likely to be cacheable (though, as a whole, it’s debatable just how cacheable query results might be for CXS data which is, by essence, very dynamic). The simpler queries provided by the GET endpoint would be more likely cacheable and benefit from using the GET method.
· The only API I know for using GET wit body is ElasticSearch, should we base our API on this I would say “Exception”? Furthermore I see in the internet some articles saying that there are servers and clients having issues with body for GET.
See again the links I posted on this. While GET with body is not strictly forbidden, no semantics can be attached to the body and servers are likely to strip it away.
Yes. :)