From 1144886f38fd0811b29c9ea0f39133f47e7cc3fe Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 30 Oct 2020 12:05:47 +0100 Subject: header.d: mention the "Transfer-Encoding: chunked" handling Ref: #6144 Closes #6148 --- docs/cmdline-opts/header.d | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/cmdline-opts/header.d b/docs/cmdline-opts/header.d index e84168996..ac02323b9 100644 --- a/docs/cmdline-opts/header.d +++ b/docs/cmdline-opts/header.d @@ -4,6 +4,7 @@ Arg:
Help: Pass custom header(s) to server Protocols: HTTP Category: http +See-also: --user-agent --referer --- Extra header to include in the request when sending HTTP to a server. You may specify any number of extra headers. Note that if you should add a custom @@ -18,17 +19,18 @@ as \-H \&"X-Custom-Header;" to send "X-Custom-Header:". curl will make sure that each header you add/replace is sent with the proper end-of-line marker, you should thus \fBnot\fP add that as a part of the header -content: do not add newlines or carriage returns, they will only mess things up -for you. +content: do not add newlines or carriage returns, they will only mess things +up for you. -Starting in 7.55.0, this option can take an argument in @filename style, which -then adds a header for each line in the input file. Using @- will make curl -read the header file from stdin. +This option can take an argument in @filename style, which then adds a header +for each line in the input file. Using @- will make curl read the header file +from stdin. Added in 7.55.0. -See also the --user-agent and --referer options. +You need --proxy-header to send custom headers intended for a HTTP +proxy. Added in 7.37.0. -Starting in 7.37.0, you need --proxy-header to send custom headers intended -for a proxy. +Passing on a "Transfer-Encoding: chunked" header when doing a HTTP request +with a requst body, will make curl send the data using chunked encoding. Example: -- cgit v1.2.1