Re: [PATCH] Add ERR support to smart HTTP

> > Nevertheless I think it would be a good idea to make *client* more
> > accepting, which means:
> > 1. Printing full HTTP status, and not only HTTP return / error code;
> >   perhaps only if it is non-standard, and perhaps only in --verbose
> >   mode.
> > 2. If message body contains ERR line, print error message even if the
> >   HTTP status was other than "200 OK".  To be "generous in what you
> >   receive" (well, kind of).
> > 3. In verbose mode, if body of HTTP error message (not "HTTP OK")
> >   exists and does not contain ERR line (e.g. an error from web server),
> >   print it in full (perhaps indented).
> >
> > I think that neither of the above would lead to leaking sensitive
> > information.
> 
> I didn't understand this bit about leaking info.  If the bits are
> coming into my machine I know what they are anyway (or am able to find
> out easily enough, even if git itself isn't showing them to me).
> Where's the leak?