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

Re: [RFC PATCH 2/2] http: support omitting data from traces

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jan 18, 2018, 18:25 UTC
Message-ID
<CAPig+cQBysXjoLKRg=tqJnHPdW9jx+TH0=PV-yTyxMqEOtuiMQ@mail.gmail.com>
In-Reply-To
<970dbd7a52de6ab084df8e9ce083bb76ec1889c0.1516235197.git.jonathantanmy@google.com>
On Wed, Jan 17, 2018 at 7:34 PM, Jonathan Tan <jonathantanmy@google.com> wrote:
Show 11 quoted lines
> GIT_TRACE_CURL provides a way to debug what is being sent and received
> over HTTP, with automatic redaction of sensitive information. But it
> also logs data transmissions, which significantly increases the log file
> size, sometimes unnecessarily. Add an option "GIT_TRACE_CURL_NO_DATA" to
> allow the user to omit such data transmissions.
>
> Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
> ---
>  http.c                      | 27 +++++++++++++++++++--------
>  t/t5551-http-fetch-smart.sh | 12 ++++++++++++
>  2 files changed, 31 insertions(+), 8 deletions(-)
Please document GIT_TRACE_CURL_NO_DATA in Documentation/git.txt.
Previous: Jonathan TanNext: Jonathan Tan
Message 3 of 5 in “Cookie redaction during GIT_TRACE_CURL”
  1. 0/2 Cookie redaction during GIT_TRACE_CURLJonathan Tan, Jan 18, 2018
  2. 2/2 http: support omitting data from tracesJonathan Tan, Jan 18, 2018
  3. Eric SunshineJan 18, 2018
  4. 1/2 http: support cookie redaction when tracingJonathan Tan, Jan 18, 2018
  5. Eric SunshineJan 18, 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.