header.d: mention the "Transfer-Encoding: chunked" handling

Ref: #6144
Closes #6148

diff --git a/docs/cmdline-opts/header.d b/docs/cmdline-opts/header.d
index e84168996c7f6c66e0b300b70c1d193d2ff7b9ea..ac02323b9d125cb298d5907681b4ed336e8c3dcc 100644 (file)
--- a/docs/cmdline-opts/header.d
+++ b/docs/cmdline-opts/header.d
@@ -4,6 +4,7 @@ Arg: <header/@file>
 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: