GET and POST
GET and POST in the Server functions guide.
method defaults to "POST". Use "GET" only for safe reads: the handler's CSRF check skips safe methods, and a
GET call can be cached or repeated by anything between the browser and the server (the answer carries
cache-control: no-store).
POST |
GET |
|
|---|---|---|
| Input | request body, serialize([input]) as JSON |
query ?p=, the same text in base64url |
| Required headers | x-dusk-fn: 1 and a JSON content-type |
x-dusk-fn: 1 |
| Input limit | security.limits.maxBodyBytes, 1 MiB by default (413) |
rpc.maxGetPayloadChars, 4096 characters of p by default (414) |
| Other method | 405 with Allow: GET or POST |
405 |
The method is checked before the body is read, and the id before the method. A call without x-dusk-fn: 1
answers 400, a POST without a JSON content type answers 415, and a GET without p gives the function
undefined as input.