http put for network

Signature

> http put {flags} (URL) (data)

Flags

• --user, -u {any}: The username when authenticating.
• --password, -p {any}: The password when authenticating.
• --content-type, -t {any}: The MIME type of content to post.
• --max-time, -m {duration}: Max duration before timeout occurs.
• --headers, -H {any}: Custom headers you want to add.
• --raw, -r: Return values as a string instead of a table.
• --insecure, -k: Allow insecure server connections when using SSL.
• --full, -f: Returns the full response instead of only the body.
• --allow-errors, -e: Do not fail if the server returns an error code.
• --pool: Using a global pool as a client.
• --redirect-mode, -R {string}: What to do when encountering redirects. Default: 'follow'. Valid options: 'follow' ('f'), 'manual' ('m'), 'error' ('e').
• --unix-socket, -U {path}: Connect to the specified Unix socket instead of using TCP.

Parameters

• URL: The URL to post to.
• data: The contents of the post body. Required unless part of a pipeline.

Input/output types:

Examples

Put content to example.com.

> http put https://www.example.com 'body'

Put content to example.com, with username and password.

> http put --user myuser --password mypass https://www.example.com 'body'

Put content to example.com, with custom header using a record.

> http put --headers {my-header-key: my-header-value} https://www.example.com

Put content to example.com, with custom header using a list.

> http put --headers [my-header-key-A my-header-value-A my-header-key-B my-header-value-B] https://www.example.com

Put content to example.com, with JSON body.

> http put --content-type application/json https://www.example.com { field: value }

Put JSON content from a pipeline to example.com.

> open --raw foo.json | http put https://www.example.com

Notes

Performs HTTP PUT operation.