Lines Matching refs:cookies

7   requests to the same domains and paths for which the cookies were set.
9   Cookies are either "session cookies" which typically are forgotten when the
11   the cookies are not session cookies they have expiration dates after which
17   For a long time, the only spec explaining how to use cookies was the
21   published and details how cookies work within HTTP. In 2016, an update which
26   to deprecate modification of 'secure' cookies from non-secure origins. Both
33   will allow and use cookies marked with the `secure` keyword even when done
35   work with secure cookies.
39   Netscape once created a file format for storing cookies on disk so that they
41   sharing the cookies with browsers, only to see browsers move away from that
56   start with `#HttpOnly_`, which is a prefix for cookies that have the
78   have curl receive and send cookies exactly as mandated in the specs.
84   tell curl a file to read cookies from and start the cookie engine, or if it
88   `-j, --junk-session-cookies`
90   when used in combination with -b, it will skip all "session cookies" on load
95   tell curl to start the cookie engine and write cookies to the given file
112   cookies from the given file. Read-only.
117   closed save all known cookies to the given cookie jar file. Write-only.
122   storage of cookies. Pass in the cookie as an HTTP header with all the
124   also be used to flush the cookies etc.
128   Tell libcurl to ignore all cookies it is about to load that are session
129   cookies.
140   can also set and access cookies.
143   capability to handle JavaScript, such cookies will not be detected or used.