summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2000-03-01 22:50:27 +0000
committerDaniel Stenberg <daniel@haxx.se>2000-03-01 22:50:27 +0000
commit190106c98e7e23ac838331fe199e8d07d6faf4b9 (patch)
tree4b7c537dae053110c7b9ed175c70035371b6cb06
parentd64b8cdf237b2221685de797563a0b39ed4acb7a (diff)
downloadcurl-190106c98e7e23ac838331fe199e8d07d6faf4b9.tar.gz
rephrased. -D writes a file, -b reads one.
-rw-r--r--curl.19
1 files changed, 9 insertions, 0 deletions
diff --git a/curl.1 b/curl.1
index b049ec19e..fa505c0b1 100644
--- a/curl.1
+++ b/curl.1
@@ -62,6 +62,11 @@ will make curl record incoming cookies too, which may be handy if you're using
this in combination with the -L/--location option. The file format of the file
to read cookies from should be plain HTTP headers or the netscape cookie file
format.
+
+.B NOTE
+that the file specified with -b/--cookie is only used as input. No cookies
+will be stored in the file. To store cookies, save the HTTP headers to a file
+using -D/--dump-header!
.IP "-B/--ftp-ascii"
(FTP/LDAP)
Use ASCII transfer when getting an FTP file or LDAP info. For FTP, this can
@@ -97,6 +102,10 @@ The contents of the file must already be url-encoded.
(HTTP/FTP)
Write the HTTP headers to this file. Write the FTP file info to this
file if -I/--head is used.
+
+This option is handy to use when you want to store the cookies that a HTTP
+site sends to you. The cookies could then be read in a second curl invoke by
+using the -b/--cookie option!
.IP "-e/--referer <URL>"
(HTTP)
Sends the "Referer Page" information to the HTTP server. Some badly