While targeting an application, Burp captures all of the cookies it encounters while proxying and spidering HTTP traffic against a target site. Burp stores these cookies in a cache called the cookie jar. This cookie jar is used within the default session-handling rule and can be shared among the suite of Burp tools, such as Proxy, Intruder, and Spider. Inside the cookie jar, there is a historical table of requests. The table details each cookie domain and path. It is possible to edit or remove cookies from the cookie jar.
Getting caught in the cookie jar
Getting ready
We will open the Burp Cookie Jar and look inside. Then, using the OWASP GetBoo application, we'll identify new cookies added to the Burp Cookie Jar.
...