Closed asvetlov closed 10 years ago
few more interesting discussions: http://lists.w3.org/Archives/Public/ietf-http-wg/2002JulSep/0031.html http://lists.w3.org/Archives/Public/ietf-http-wg/2007JanMar/0076.html
TL;DR technically, it's ok to send body with GET/DELETE requests. Semantically - it's not. In real world only few uses such "feature".
+1
let's unify 'data' processing for all type of requests
When aiohttp.request gets
GET
method with specifieddata
that merges data to url along withparams
.I think that's wrong. HTTP protocol standard (http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html) says nothing about presence/absence body for GET methods.
Moreover elasticsearch uses GETs with body for some REST API methods: see http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-multi-get.html and http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-multi-search.html#search-multi-search
I guess to always process
data
as forPOST
request if specified.