| xf.li | 6c8fc1e | 2023-08-12 00:11:09 -0700 | [diff] [blame^] | 1 | c: Copyright (C) 1998 - 2022, Daniel Stenberg, <daniel@haxx.se>, et al. |
| 2 | SPDX-License-Identifier: curl |
| 3 | Short: c |
| 4 | Long: cookie-jar |
| 5 | Arg: <filename> |
| 6 | Protocols: HTTP |
| 7 | Help: Write cookies to <filename> after operation |
| 8 | Category: http |
| 9 | Example: -c store-here.txt $URL |
| 10 | Example: -c store-here.txt -b read-these $URL |
| 11 | Added: 7.9 |
| 12 | See-also: cookie |
| 13 | Multi: single |
| 14 | --- |
| 15 | Specify to which file you want curl to write all cookies after a completed |
| 16 | operation. Curl writes all cookies from its in-memory cookie storage to the |
| 17 | given file at the end of operations. If no cookies are known, no data will be |
| 18 | written. The file will be written using the Netscape cookie file format. If |
| 19 | you set the file name to a single dash, "-", the cookies will be written to |
| 20 | stdout. |
| 21 | |
| 22 | This command line option will activate the cookie engine that makes curl |
| 23 | record and use cookies. Another way to activate it is to use the --cookie |
| 24 | option. |
| 25 | |
| 26 | If the cookie jar cannot be created or written to, the whole curl operation |
| 27 | will not fail or even report an error clearly. Using --verbose will get a |
| 28 | warning displayed, but that is the only visible feedback you get about this |
| 29 | possibly lethal situation. |