Option to send GET request body · Issue #131 · postmanlabs/postman-app-support



Option to send GET request body · Issue #131 · postmanlabs/postman-app-support

@congruityservice is right; I can say from having used current versions of Elasticsearch that this feature is no longer a requirement as you can send the same request that you would send with a GET with a POST instead and it will work identically.

Now, to sort something out about the HTTP/1.1 specification:

RFC 2616, section 4.3 clearly states:

A message-body MUST NOT be included in a request if the specification of the request method (section 5.1.1) does not allow sending an entity-body in requests.
https://tools.ietf.org/html/rfc2616#section-4.3

However, in the entirety of section 9.3, the section defining the GET verb, nothing prevents a GET request from having a body.

But before you draw any conclusions - the functionality defined for the GET verb also does not include any logic involving the message body.

In other words, if we are to follow the specification:

  1. It is possible to send a message body with a GET request per specification.
  2. However, the server responding to the GET request must ignore the body to follow the standard.

Essentially, there is no point, per standard, to send a body with a GET request, even though it is not explicitly disallowed.

Roy T. Fielding backs this interpretation up:

...any HTTP request message is allowed to contain a message body, and thus must parse messages with that in mind. Server semantics for GET, however, are restricted such that a body, if any, has no semantic meaning to the request. The requirements on parsing are separate from the requirements on method semantics.
So, yes, you can send a body with GET, and no, it is never useful to do so.
https://groups.yahoo.com/neo/groups/rest-discuss/conversations/messages/9962

Taking all of this into consideration, I believe this issue should be closed as adding this functionality should have no effect or use per standard. Elasticsearch, though a great product, should not dictate how the HTTP standard is to be or not to be enforced.


Read full article from Option to send GET request body · Issue #131 · postmanlabs/postman-app-support


No comments:

Post a Comment

Labels

Algorithm (219) Lucene (130) LeetCode (97) Database (36) Data Structure (33) text mining (28) Solr (27) java (27) Mathematical Algorithm (26) Difficult Algorithm (25) Logic Thinking (23) Puzzles (23) Bit Algorithms (22) Math (21) List (20) Dynamic Programming (19) Linux (19) Tree (18) Machine Learning (15) EPI (11) Queue (11) Smart Algorithm (11) Operating System (9) Java Basic (8) Recursive Algorithm (8) Stack (8) Eclipse (7) Scala (7) Tika (7) J2EE (6) Monitoring (6) Trie (6) Concurrency (5) Geometry Algorithm (5) Greedy Algorithm (5) Mahout (5) MySQL (5) xpost (5) C (4) Interview (4) Vi (4) regular expression (4) to-do (4) C++ (3) Chrome (3) Divide and Conquer (3) Graph Algorithm (3) Permutation (3) Powershell (3) Random (3) Segment Tree (3) UIMA (3) Union-Find (3) Video (3) Virtualization (3) Windows (3) XML (3) Advanced Data Structure (2) Android (2) Bash (2) Classic Algorithm (2) Debugging (2) Design Pattern (2) Google (2) Hadoop (2) Java Collections (2) Markov Chains (2) Probabilities (2) Shell (2) Site (2) Web Development (2) Workplace (2) angularjs (2) .Net (1) Amazon Interview (1) Android Studio (1) Array (1) Boilerpipe (1) Book Notes (1) ChromeOS (1) Chromebook (1) Codility (1) Desgin (1) Design (1) Divide and Conqure (1) GAE (1) Google Interview (1) Great Stuff (1) Hash (1) High Tech Companies (1) Improving (1) LifeTips (1) Maven (1) Network (1) Performance (1) Programming (1) Resources (1) Sampling (1) Sed (1) Smart Thinking (1) Sort (1) Spark (1) Stanford NLP (1) System Design (1) Trove (1) VIP (1) tools (1)

Popular Posts