From: "Piotr Szlazak via GitGitGadget" <gitgitgadget@gmail•com>
To: git@vger•kernel.org
Cc: Piotr Szlazak <piotr.szlazak@gmail•com>,
Piotr Szlazak <piotr.szlazak@gmail•com>
Subject: [PATCH] doc: update http.cookieFile with in-memory cookie processing
Date: Sun, 23 Jun 2024 21:24:06 +0000 [thread overview]
Message-ID: <pull.1733.git.git.1719177846725.gitgitgadget@gmail.com> (raw)
From: Piotr Szlazak <piotr.szlazak@gmail•com>
Information added how to enable in-memory cookies
processing. Cookies from server will be accepted and send
back in successive requests within same connection.
At the moment documentation only mentions how to read
cookies from the given file and how to save them to the file
using http.saveCookies.
curl / libcurl will process cookies in memory if file name
is blank. Check curl manpage:
https://curl.se/docs/manpage.html#-b
This is described here in more details:
https://everything.curl.dev/http/cookies/engine.html
And also explained here:
https://www.youtube.com/watch?v=V5vZWHP-RqU&t=11459s
Git documentation was updated to include suggestion how to
enable this by setting empty value for http.cookieFile.
Signed-off-by: Piotr Szlazak <piotr.szlazak@gmail•com>
---
Update http.cookieFile with in-memory cookie processing
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1733%2Fpszlazak%2Fdocumentation-cookieFile-in-memory-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1733/pszlazak/documentation-cookieFile-in-memory-v1
Pull-Request: https://github.com/git/git/pull/1733
Documentation/config/http.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/config/http.txt b/Documentation/config/http.txt
index 2d4e0c9b869..228bed32ec1 100644
--- a/Documentation/config/http.txt
+++ b/Documentation/config/http.txt
@@ -78,10 +78,10 @@ http.extraHeader::
http.cookieFile::
The pathname of a file containing previously stored cookie lines,
- which should be used
- in the Git http session, if they match the server. The file format
- of the file to read cookies from should be plain HTTP headers or
- the Netscape/Mozilla cookie file format (see `curl(1)`).
+ which should be used in the Git http session, if they match the server.
+ The file format of the file to read cookies from should be plain HTTP
+ headers or the Netscape/Mozilla cookie file format (see `curl(1)`).
+ Set it to empty value, to enable in-memory cookies processing.
NOTE that the file specified with http.cookieFile is used only as
input unless http.saveCookies is set.
base-commit: 66ac6e4bcd111be3fa9c2a6b3fafea718d00678d
--
gitgitgadget
next reply other threads:[~2024-06-23 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 21:24 Piotr Szlazak via GitGitGadget [this message]
2024-07-09 21:37 ` [PATCH] doc: update http.cookieFile with in-memory cookie processing Piotr Szlazak
2024-07-09 22:30 ` Junio C Hamano
2024-07-09 23:05 ` Junio C Hamano
2024-07-11 9:18 ` Piotr Szlazak
2024-07-11 8:36 ` [PATCH v2] " Piotr Szlazak via GitGitGadget
2024-07-11 16:05 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1733.git.git.1719177846725.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=piotr.szlazak@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox