doc: update http.cookieFile with in-memory cookie processing
Documentation only mentions how to read cookies from the given file and how to save them to the file using http.saveCookies. But underlying libcURL allows the HTTP cookies used only in memory; cookies from the server will be accepted and sent back in successive requests within same connection, by using an empty string as the filename. Document this. Signed-off-by: Piotr Szlazak <piotr.szlazak@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Piotr Szlazak committed
Jul 11, 2024 at 08:36 UTC
8d201195515a6b4decc0df435c8fbff93d855a5c
1 file changed
+5
-1
Documentation/config/http.txt
+5
-1
@@ -82,12 +82,16 @@ http.cookieFile::
82
in the Git http session, if they match the server. The file format
83
of the file to read cookies from should be plain HTTP headers or
84
the Netscape/Mozilla cookie file format (see `curl(1)`).
85
+ Set it to an empty string, to accept only new cookies from
86
+ the server and send them back in successive requests within same
87
+ connection.
88
NOTE that the file specified with http.cookieFile is used only as
89
input unless http.saveCookies is set.
90
91
http.saveCookies::
92
If set, store cookies received during requests to the file specified by
90
- http.cookieFile. Has no effect if http.cookieFile is unset.
93
+ http.cookieFile. Has no effect if http.cookieFile is unset, or set to
94
+ an empty string.
95
96
http.version::
97
Use the specified HTTP protocol version when communicating with a server.