| commit | 959dfcf42f264e8644d88b355224ff468ebae10d | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 14 Mar 2011 18:28:17 +0000 (14 11:28 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 14 Mar 2011 18:58:51 +0000 (14 11:58 -0700) | ||
| tree | a3965d1fd9b7c09c1dfd8b3b726a26c04e18b902 | treesnapshot (tar.gz zip) |
| parent | 206b099d269955337bd6169f71aa08ba28a0cf4f | commitdiff |
smart-http: Really never use Expect: 100-continue
libcurl may choose to try and use Expect: 100-continue for
any type of POST, not just a Transfer: chunked-encoding type.
Force it to disable this feature, as not all proxy servers support
100-continue and leaving it enabled can cause 1 second stalls during
the negotiation phase of fetch-pack/upload-pack.
In ("206b099d26 smart-http: Don't use Expect: 100-Continue") we
tried to disable this for only large POST bodies, but it should be
disabled for every POST body.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
libcurl may choose to try and use Expect: 100-continue for
any type of POST, not just a Transfer: chunked-encoding type.
Force it to disable this feature, as not all proxy servers support
100-continue and leaving it enabled can cause 1 second stalls during
the negotiation phase of fetch-pack/upload-pack.
In ("206b099d26 smart-http: Don't use Expect: 100-Continue") we
tried to disable this for only large POST bodies, but it should be
disabled for every POST body.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| remote-curl.c | diffblobblamehistory |