3 ms·
Yup, Elasticsearch ran into the same problem that Dropbox has, so they use request bodies to get around it. From: https://github.com/elasticsearch/elasticsearc
by ipsum2 12y ago
Yup, Elasticsearch ran into the same problem that Dropbox has, so they use request bodies to get around it.
From: https://github.com/elasticsearch/elasticsearch-definitive-guide/commit/cff7de5722b127ce432a7b3017f103e4d7e9bf65 https://github.com/elasticsearch/elasticsearch-definitive-gu... :
> A GET request with a body?
The HTTP libraries of certain languages (notably Javascript) don’t allow GET requests to have a request body. In fact, some users are suprised that GET requests are ever allowed to have a body.
> The truth is that RFC 7231 — the RFC which deals with HTTP semantics and content — does not define what should happen to a GET request with a body! As a result, some HTTP servers allow it, and some — especially caching proxies — don’t.
> The authors of Elasticsearch prefer using GET for a search request because they feel that it describes the action — retrieving information — better than the POST verb. However, because GET with a request body is not universally supported, the search API also accepts POST requests:
- btilly 12y agoThe significant difference here is that people using elastic search typically control the machines and network involved while Dropbox does not. Therefore it is OK for elastic search to say, "This is a reasonable way to work, and it is up to you to use compatible software etc." But a similar decision on Dropbox's part would mean that a random fraction of their customers would have a broken experience.