Jeff King 2e736fd5e9 remote-curl: retry failed requests for auth even with gzip
Commit b81401c taught the post_rpc function to retry the
http request after prompting for credentials. However, it
did not handle two cases:

  1. If we have a large request, we do not retry. That's OK,
     since we would have sent a probe (with retry) already.

  2. If we are gzipping the request, we do not retry. That
     was considered OK, because the intended use was for
     push (e.g., listing refs is OK, but actually pushing
     objects is not), and we never gzip on push.

This patch teaches post_rpc to retry even a gzipped request.
This has two advantages:

  1. It is possible to configure a "half-auth" state for
     fetching, where the set of refs and their sha1s are
     advertised, but one cannot actually fetch objects.

     This is not a recommended configuration, as it leaks
     some information about what is in the repository (e.g.,
     an attacker can try brute-forcing possible content in
     your repository and checking whether it matches your
     branch sha1). However, it can be slightly more
     convenient, since a no-op fetch will not require a
     password at all.

  2. It future-proofs us should we decide to ever gzip more
     requests.

Signed-off-by: Jeff King <peff@peff.net>
2012-10-31 07:45:13 -04:00
2012-06-17 14:04:15 -07:00
2012-04-02 15:06:25 -07:00
2012-03-28 08:47:23 -07:00
2012-05-29 09:28:34 +01:00
2011-03-17 15:30:49 -07:00
2011-12-13 22:53:08 -08:00
2012-04-26 10:22:20 -07:00
2011-10-21 16:04:32 -07:00
2009-09-13 01:32:26 -07:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-05-07 09:34:27 -07:00
2011-05-26 16:47:15 -07:00
2011-08-11 12:21:07 -07:00
2011-09-19 20:46:48 -07:00
2012-06-17 14:04:15 -07:00
2012-01-08 15:07:20 -08:00
2012-04-06 10:15:11 -07:00
2011-12-19 16:06:41 -08:00
2011-12-19 16:06:41 -08:00
2012-02-05 23:53:21 -08:00
2011-08-20 22:33:57 -07:00
2009-04-22 19:02:12 -07:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2010-01-12 01:06:09 -08:00
2012-01-06 12:44:07 -08:00
2010-04-01 23:58:30 -07:00
2011-08-22 10:07:07 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-02-12 19:50:39 -08:00
2012-02-12 19:50:39 -08:00
2012-06-17 14:04:15 -07:00
2012-02-22 18:17:39 -08:00
2012-02-22 18:17:39 -08:00
2011-05-30 00:09:55 -07:00
2010-05-04 15:38:58 -07:00
2009-11-04 17:58:15 -08:00
2011-08-01 15:00:29 -07:00
2011-05-26 16:47:15 -07:00
2011-12-11 23:16:24 -08:00
2009-08-23 17:11:28 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07:00
2011-05-26 13:54:18 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org (read
Documentation/SubmittingPatches for instructions on patch submission).
To subscribe to the list, send an email with just "subscribe git" in
the body to majordomo@vger.kernel.org. The mailing list archives are
available at http://marc.theaimsgroup.com/?l=git and other archival
sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 612 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%