From 2c6c5ac44c67293a0b61b5a18a091b5fa7a49cd8 Mon Sep 17 00:00:00 2001 From: Z Date: Mon, 26 Jun 2017 09:15:32 +0200 Subject: [PATCH] Update query-requests-with-large-inputs.md --- execution/query-requests-with-large-inputs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/execution/query-requests-with-large-inputs.md b/execution/query-requests-with-large-inputs.md index 00768ac..6d6bb87 100644 --- a/execution/query-requests-with-large-inputs.md +++ b/execution/query-requests-with-large-inputs.md @@ -1,7 +1,7 @@ # Query Requests with Large Inputs -While HTTP doesn't impose any limit on the length of an URI some implementation of server or client might have difficulties handling long URIs (usually URIs with many or large query parameters). +While HTTP doesn't impose any limit on the length of a URI, some implementation of server or client might have difficulties handling long URIs (usually URIs with many or large query parameters). -Every endpoint with such an URI **MUST** use the HTTP **POST** Request Method and send the query string in HTTP Request Message body using the `application/x-www-form-urlencoded` media type. +Every endpoint with such a URI **MUST** use the HTTP **POST** Request Method and send the query string in HTTP Request Message body using the `application/x-www-form-urlencoded` media type. #### Example @@ -14,4 +14,4 @@ search=attributes&color=white&size=56&... ``` -> _NOTE: Since this operation is safe and idempotent, using the POST method violates the HTTP Protocol semantics and results in loss of cache-ability._ +> _NOTE: Since this operation is safe and idempotent, using the POST method violates the HTTP protocol semantics and results in loss of cache-ability._