summaryrefslogtreecommitdiff
path: root/docs/cmdline-opts/data.d
diff options
context:
space:
mode:
Diffstat (limited to 'docs/cmdline-opts/data.d')
-rw-r--r--docs/cmdline-opts/data.d10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/cmdline-opts/data.d b/docs/cmdline-opts/data.d
index 9425ba24f..682314c02 100644
--- a/docs/cmdline-opts/data.d
+++ b/docs/cmdline-opts/data.d
@@ -14,17 +14,17 @@ Added: 4.0
Sends the specified data in a POST request to the HTTP server, in the same way
that a browser does when a user has filled in an HTML form and presses the
submit button. This will cause curl to pass the data to the server using the
-content-type application/x-www-form-urlencoded. Compare to --form.
+content-type application/x-www-form-urlencoded. Compare to --form.
--data-raw is almost the same but does not have a special interpretation of
the @ character. To post data purely binary, you should instead use the
---data-binary option. To URL-encode the value of a form field you may use
+--data-binary option. To URL-encode the value of a form field you may use
--data-urlencode.
If any of these options is used more than once on the same command line, the
-data pieces specified will be merged together with a separating
-&-symbol. Thus, using '-d name=daniel -d skill=lousy' would generate a post
-chunk that looks like \&'name=daniel&skill=lousy'.
+data pieces specified will be merged with a separating &-symbol. Thus, using
+\&'-d name=daniel -d skill=lousy' would generate a post chunk that looks like
+\&'name=daniel&skill=lousy'.
If you start the data with the letter @, the rest should be a file name to
read the data from, or - if you want curl to read the data from stdin. Posting