回答編集履歴
1
あ
test
CHANGED
|
@@ -5,3 +5,31 @@
|
|
|
5
5
|
出来ると思うよ
|
|
6
6
|
|
|
7
7
|
不完全なHTTPクライアント実装に対する譲歩として、POSTリクエスト使うことはあると思うが、やっちゃだめとはかかれていねかったと思う
|
|
8
|
+
|
|
9
|
+
くわしくはここらへんにかいてあるとおもうよー
|
|
10
|
+
|
|
11
|
+
https://www.elastic.co/guide/en/elasticsearch/guide/current/_empty_search.html#get_vs_post
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
> ## A GET Request with a Body?
|
|
18
|
+
|
|
19
|
+
>
|
|
20
|
+
|
|
21
|
+
> 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.
|
|
22
|
+
|
|
23
|
+
>
|
|
24
|
+
|
|
25
|
+
> The truth is that RFC 7231—the RFC that 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.
|
|
26
|
+
|
|
27
|
+
>
|
|
28
|
+
|
|
29
|
+
> 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
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
|
|
35
|
+
まあ、バージョンふるいドキュメントだし、あんま期待せずに読んでいくのがいいんじゃないかねー
|