|
@@ -22,14 +22,10 @@ The file format of the file to read cookies from should be plain HTTP headers
|
|
|
The file specified with --cookie is only used as input. No cookies will be
|
|
|
written to the file. To store cookies, use the --cookie-jar option.
|
|
|
|
|
|
-Exercise caution if you are using this option and multiple transfers may
|
|
|
-occur. If you use the NAME1=VALUE1; format, or in a file use the Set-Cookie
|
|
|
-format and don't specify a domain, then the cookie is sent for any domain
|
|
|
-(even after redirects are followed) and cannot be modified by a server-set
|
|
|
-cookie. If the cookie engine is enabled and a server sets a cookie of the same
|
|
|
-name then both will be sent on a future transfer to that server, likely not
|
|
|
-what you intended. To address these issues set a domain in Set-Cookie (doing
|
|
|
-that will include sub domains) or use the Netscape format.
|
|
|
+If you use the Set-Cookie file format and don't specify a domain then the
|
|
|
+cookie is not sent since the domain will never match. To address this, set a
|
|
|
+domain in Set-Cookie line (doing that will include sub-domains) or preferably:
|
|
|
+use the Netscape format.
|
|
|
|
|
|
This option can be used multiple times.
|
|
|
|