forked from extern/httpie-cli
Fix documentation on file upload (#1000)
As documented later on in "File upload forms", the correct syntax to set the mimetype of the upload is `field@file;type=filetype`
This commit is contained in:
parent
f7e77efe4b
commit
02971b938d
56
README.rst
56
README.rst
@ -462,34 +462,34 @@ their type is distinguished only by the separator used:
|
|||||||
``:``, ``=``, ``:=``, ``==``, ``@``, ``=@``, and ``:=@``. The ones with an
|
``:``, ``=``, ``:=``, ``==``, ``@``, ``=@``, and ``:=@``. The ones with an
|
||||||
``@`` expect a file path as value.
|
``@`` expect a file path as value.
|
||||||
|
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
| Item Type | Description |
|
| Item Type | Description |
|
||||||
+=======================+=====================================================+
|
+==============================+===================================================+
|
||||||
| HTTP Headers | Arbitrary HTTP header, e.g. ``X-API-Token:123``. |
|
| HTTP Headers | Arbitrary HTTP header, e.g. ``X-API-Token:123``. |
|
||||||
| ``Name:Value`` | |
|
| ``Name:Value`` | |
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
| URL parameters | Appends the given name/value pair as a query |
|
| URL parameters | Appends the given name/value pair as a query |
|
||||||
| ``name==value`` | string parameter to the URL. |
|
| ``name==value`` | string parameter to the URL. |
|
||||||
| | The ``==`` separator is used. |
|
| | The ``==`` separator is used. |
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
| Data Fields | Request data fields to be serialized as a JSON |
|
| Data Fields | Request data fields to be serialized as a JSON |
|
||||||
| ``field=value``, | object (default), to be form-encoded |
|
| ``field=value``, | object (default), to be form-encoded |
|
||||||
| ``field=@file.txt`` | (with ``--form, -f``), or to be serialized as |
|
| ``field=@file.txt`` | (with ``--form, -f``), or to be serialized as |
|
||||||
| | ``multipart/form-data`` (with ``--multipart``). |
|
| | ``multipart/form-data`` (with ``--multipart``). |
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
| Raw JSON fields | Useful when sending JSON and one or |
|
| Raw JSON fields | Useful when sending JSON and one or |
|
||||||
| ``field:=json``, | more fields need to be a ``Boolean``, ``Number``, |
|
| ``field:=json``, | more fields need to be a ``Boolean``, ``Number``, |
|
||||||
| ``field:=@file.json`` | nested ``Object``, or an ``Array``, e.g., |
|
| ``field:=@file.json`` | nested ``Object``, or an ``Array``, e.g., |
|
||||||
| | ``meals:='["ham","spam"]'`` or ``pies:=[1,2,3]`` |
|
| | ``meals:='["ham","spam"]'`` or ``pies:=[1,2,3]`` |
|
||||||
| | (note the quotes). |
|
| | (note the quotes). |
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
| Fields upload fields | Only available with ``--form, -f`` and |
|
| Fields upload fields | Only available with ``--form, -f`` and |
|
||||||
| ``field@/dir/file`` | ``--multipart``. |
|
| ``field@/dir/file`` | ``--multipart``. |
|
||||||
| ``field@file;type`` | For example ``screenshot@~/Pictures/img.png``, or |
|
| ``field@file;type=filetype`` | For example ``screenshot@~/Pictures/img.png``, or |
|
||||||
| | ``'cv@cv.txt;text/markdown'``. |
|
| | ``'cv@cv.txt;type=text/markdown'``. |
|
||||||
| | With ``--form``, the presence of a file field |
|
| | With ``--form``, the presence of a file field |
|
||||||
| | results in a ``--multipart`` request. |
|
| | results in a ``--multipart`` request. |
|
||||||
+-----------------------+-----------------------------------------------------+
|
+------------------------------+---------------------------------------------------+
|
||||||
|
|
||||||
|
|
||||||
Note that data fields aren’t the only way to specify request data:
|
Note that data fields aren’t the only way to specify request data:
|
||||||
|
Loading…
Reference in New Issue
Block a user