aboutsummaryrefslogtreecommitdiff
path: root/docs/cmdline-opts/data-urlencode.md
blob: 4d3f2981335a4051662194496f2abfa668dc27ab (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
---
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
SPDX-License-Identifier: curl
Long: data-urlencode
Arg: <data>
Help: HTTP POST data URL encoded
Protocols: HTTP
Added: 7.18.0
Category: http post upload
Multi: append
See-also:
  - data
  - data-raw
Example:
  - --data-urlencode name=val $URL
  - --data-urlencode =encodethis $URL
  - --data-urlencode name@file $URL
  - --data-urlencode @fileonly $URL
---

# `--data-urlencode`

This posts data, similar to the other --data options with the exception
that this performs URL-encoding.

To be CGI-compliant, the <data> part should begin with a *name* followed
by a separator and a content specification. The <data> part can be passed to
curl using one of the following syntaxes:

## content
This makes curl URL-encode the content and pass that on. Just be careful
so that the content does not contain any = or @ symbols, as that makes
the syntax match one of the other cases below!

## =content
This makes curl URL-encode the content and pass that on. The preceding =
symbol is not included in the data.

## name=content
This makes curl URL-encode the content part and pass that on. Note that
the name part is expected to be URL-encoded already.

## @filename
This makes curl load data from the given file (including any newlines),
URL-encode that data and pass it on in the POST.

## name@filename
This makes curl load data from the given file (including any newlines),
URL-encode that data and pass it on in the POST. The name part gets an equal
sign appended, resulting in *name=urlencoded-file-content*. Note that the
name is expected to be URL-encoded already.