diff options
| author | André Srinivasan <andre.srinivasan@gmail.com> | 2024-10-28 12:28:36 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-28 20:28:36 +0100 |
| commit | 50e1564600eaca3ff99ffd7a7f707f564da3af48 (patch) | |
| tree | fd447abe88c0cbcc768a7bf31525bac8eba5b8b9 | |
| parent | f4cf43ecdd6c5c52b5c4ba91086d5c6ccfebcd6d (diff) | |
Update the Forms section of README.md (#1593)
The Forms section of README.md was missing what the data fields are serialized as.
| -rw-r--r-- | docs/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/README.md b/docs/README.md index 65c7ebe4..4b866a04 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1044,7 +1044,7 @@ $ http POST pie.dev/post < files/data.json ## Forms Submitting forms is very similar to sending [JSON](#json) requests. -Often the only difference is in adding the `--form, -f` option, which ensures that data fields are serialized as, and `Content-Type` is set to `application/x-www-form-urlencoded; charset=utf-8`. +Often the only difference is in adding the `--form, -f` option, which ensures that data fields are serialized as key-value tuples separated by '&', with a '=' between the key and the value. In addition `Content-Type` is set to `application/x-www-form-urlencoded; charset=utf-8`. It is possible to make form data the implicit content type instead of JSON via the [config](#config) file. ### Regular forms |