HTTP cookies are key-value pairs that are sent by the server to the client to store. The client sends the cookies back on subsequent requests. In this way, the server can keep track of the client’s state.
The command line tool curl is a powerful tool that developers use to transfer data to and from a server.
How can you store the cookies sent by the server when using curl? And how can you send those cookies to the server on subsequent requests?
The general design of curl is minimalistic. This means that we need to turn on the “cookie engine”, otherwise curl will not acknowledge any cookies.
We can enable the cookie engine by asking curl to read or write the cookies.
For example, we can activate the cookie engine and read the cookies using the option
--cookie or the shorter version
-b. We can read the cookies from a string
theme=dark and send them in an HTTP request like so:
curl --cookie theme=dark https://www.google.com
curl -b theme=dark https://www.google.com
To read the cookies from a file, we can provide the file name after the read cookie option, like so:
curl -b cookies.txt https://www.google.com
So how does curl know that this time we are providing a file name and not a string? If no ’=’ symbol is used in the argument, curl treats the argument as a filename, and reads data from there.
The above command will only read the cookies from the file. If the server updates the cookies in its response, curl will update that cookie in its in-memory store only, which will be discarded eventually.
We can tell curl to write cookies to a file using the
For example, we can use the following command to save the cookies returned by the server in the file
curl -c cookie-jar.txt https://www.google.com
An important point to keep in mind is that curl will write all cookies from its in-memory cookie storage to the given file only at the end of operations. Curl will not save the cookie data to the file during its lifetime.
Often we will need to read and write cookies at the same time, like so:
curl -b cookie-jar.txt -c cookie-jar.txt https://www.google.com
The cookie file used with curl should follow the Netscape cookie file format. According to the documentation:
The cookie file format is text based and stores one cookie per line. Lines that start with
#are treated as comments.
Each line that specifies a single cookie consists of seven text fields separated with TAB characters. A valid line must end with a newline character.
Field number, type, example data and the meaning of it:
example.com- the domain name
FALSE- include subdomains
TRUE- send/receive over HTTPS only
1462299217- expires at - seconds since 01 January 1970, or 0
person- name of the cookie
daniel- value of the cookie
Loved by over 4 million developers and more than 90,000 organizations worldwide, Sentry provides code-level observability to many of the world’s best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.
Here’s a quick look at how Sentry handles your personal information (PII).×
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.Am I included?
We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII: