dump-header.d: Drop suggestion to use for cookie storage

Since --cookie-jar is the preferred way to store cookies, no longer
suggest using --dump-header to do so.

Co-authored-by: Daniel Stenberg
Closes https://github.com/curl/curl/issues/7414

diff --git a/docs/cmdline-opts/dump-header.d b/docs/cmdline-opts/dump-header.d
index 8449dfe8516dcc7aeefc40a7b3580c5dc76e9597..aa3bd9e33b4b9912088daa104cef15a26e84ddc1 100644 (file)
--- a/docs/cmdline-opts/dump-header.d
+++ b/docs/cmdline-opts/dump-header.d
@@ -6,14 +6,8 @@ Protocols: HTTP FTP
 See-also: output
 Category: http ftp
 ---
-Write the received protocol headers to the specified file.
-
-This option is handy to use when you want to store the headers that an HTTP
-site sends to you. Cookies from the headers could then be read in a second
-curl invocation by using the --cookie option! The --cookie-jar option is a
-better way to store cookies.
-
-If no headers are received, the use of this option will create an empty file.
+Write the received protocol headers to the specified file. If no headers are
+received, the use of this option will create an empty file.
 
 When used in FTP, the FTP server response lines are considered being "headers"
 and thus are saved there.