http.postBuffer set at the server side?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We have systems hosting git which are behind proxies, and unless the client sets the http.postBuffer to a large size they connections fails.

Is there a way to set this on the server side? If not would a patch be possible to fix this?

jason.pyeron@hostname /home/jason.pyeron/desktop/projectname
$ git push remote --all
Username for 'https://server.fqdn':
Password for 'https://jpyeron@xxxxxxxxxxx':
Counting objects: 1820, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1276/1276), done.
error: RPC failed; result=22, HTTP code = 411
fatal: The remote end hung up unexpectedly
Writing objects: 100% (1820/1820), 17.72 MiB | 5.50 MiB/s, done.
Total 1820 (delta 527), reused 26 (delta 6)
fatal: The remote end hung up unexpectedly

jason.pyeron@hostname /home/jason.pyeron/desktop/projectname
$ git config http.postBuffer 524288000

jason.pyeron@hostname /home/jason.pyeron/desktop/projectname
$ git push remote --all
Username for 'https://server.fqdn':
Password for 'https://jpyeron@xxxxxxxxxxx':
Counting objects: 1820, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1276/1276), done.
Writing objects: 100% (1820/1820), 17.72 MiB | 11.31 MiB/s, done.
Total 1820 (delta 519), reused 26 (delta 6)
To https://server.fqdn/git/netasset-portal/
 * [new branch]      master -> master

<<attachment: smime.p7s>>


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]