docs: fix typos in last web_api update
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
parent
dbf5f93919
commit
d1dfa86081
|
@ -14,10 +14,10 @@ Moonraker's API registration along with the desire to keep consistency
|
||||||
between mulitple API protocols results in an HTTP API that does not
|
between mulitple API protocols results in an HTTP API that does not
|
||||||
completely adhere to the standard.
|
completely adhere to the standard.
|
||||||
|
|
||||||
Moonraker is capable of parsing request arguments from the body
|
Moonraker is capable of parsing request arguments from the both the body
|
||||||
(either json or form-data depending on the `Content-Type` header) and from
|
(either JSON or form-data depending on the `Content-Type` header) and from
|
||||||
the query string. All arguments are grouped together in one data structure,
|
the query string. All arguments are grouped together in one data structure,
|
||||||
with body arguments taking precedence over query query arguments. Thus
|
with body arguments taking precedence over query arguments. Thus
|
||||||
if the same argument is supplied both in the body and in the
|
if the same argument is supplied both in the body and in the
|
||||||
query string the body argument would be used. It is left up to the client
|
query string the body argument would be used. It is left up to the client
|
||||||
developer to decide exactly how they want to provide arguments, however
|
developer to decide exactly how they want to provide arguments, however
|
||||||
|
|
Loading…
Reference in New Issue