git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 0/2] Cookie redaction during GIT_TRACE_CURL

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Jan 19, 2018, 00:28 UTC
Message-ID
<cover.1516321355.git.jonathantanmy@google.com>
In-Reply-To
<cover.1516235197.git.jonathantanmy@google.com>
Thanks, Eric. Changes in v2:
 - documented all environment variables introduced
 - made test more clear by ensuring that no cookie keys are suffixes or
   prefixes of others
 - tested empty value

As far as I can tell, it does not seem possible that Git generates a cookie with no equals sign (like "Secure" or "HttpOnly" described in RFC 6265). When I try to craft a cookie file containing that (using "Set-Cookie: Foo=; HttpOnly", for example), the no-equals-sign cookie just disappears.

Jonathan Tan (2):
  http: support cookie redaction when tracing
  http: support omitting data from traces
 Documentation/git.txt       | 10 ++++++
 http.c                      | 82 ++++++++++++++++++++++++++++++++++++++++-----
 t/t5551-http-fetch-smart.sh | 33 ++++++++++++++++++
 3 files changed, 117 insertions(+), 8 deletions(-)
-- 
2.16.0.rc2.37.ge0d575025.dirty
Next: Jonathan Tan
Message 1 of 3 in “Cookie redaction during GIT_TRACE_CURL”
  1. 0/2 Cookie redaction during GIT_TRACE_CURLJonathan Tan, Jan 19, 2018
  2. 2/2 http: support omitting data from tracesJonathan Tan, Jan 19, 2018
  3. 1/2 http: support cookie redaction when tracingJonathan Tan, Jan 19, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.