aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2013-12-18 22:46:38 +0100
committerDaniel Stenberg <daniel@haxx.se>2013-12-18 22:46:38 +0100
commit0a898655e8130214d98cf7dc8609bb2a775a860a (patch)
tree55a922bed2a082d6891ebd57899fc8d173029f73
parent48043f87b60a74af22bfe66a2db3b105a946921c (diff)
curl.1: remove URL encoding phrase from --data description
... it could be misleading a reader into thinking it _has_ to be encoded.
-rw-r--r--docs/curl.110
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/curl.1 b/docs/curl.1
index 49194762a..32ae92a8d 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -287,11 +287,11 @@ data pieces specified will be merged together with a separating
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. The
-contents of the file must already be URL-encoded. Multiple files can also be
-specified. Posting data from a file named 'foobar' would thus be done with
-\fI--data\fP @foobar. When --data is told to read from a file like that,
-carriage returns and newlines will be stripped out.
+read the data from, or - if you want curl to read the data from
+stdin. Multiple files can also be specified. Posting data from a file
+named 'foobar' would thus be done with \fI--data\fP @foobar. When --data is
+told to read from a file like that, carriage returns and newlines will be
+stripped out.
.IP "-D, --dump-header <file>"
Write the protocol headers to the specified file.