1
2
3
4

send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (6455/6455), 2.95 MiB | 1.53 MiB/s, done.
Total 6455 (delta 2752), reused 6281 (delta 2580), pack-reused 0
fatal: the remote end hung up unexpectedly

1
2

http.postBuffer = 16777216
http.version = HTTP/1.1

1

git -C .deploy_git push --verbose

1
2
3
4
5
6
7
8
9
10
11

推送数据 2.95 MiB
    ↓ 超过默认缓冲区 1 MiB
Git 改用 chunked 分块传输
    ↓
Traefik / Gitea 链路没有正确处理该请求
    ↓
返回 HTTP 200，但响应体为 0
    ↓
Git 收不到 receive-pack 的 sideband 结果
    ↓
unexpected disconnect

1
2
3

Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests.

Note that raising this limit is only effective for disabling chunked transfer encoding and therefore should be used only where the remote server or a proxy only supports HTTP/1.0 or is noncompliant with the HTTP standard. Raising this is not, in general, an effective solution for most push problems, but can increase memory consumption significantly since the entire buffer is allocated even for small pushes.

1
2
3
4
5

Git 使用智能 HTTP 传输协议向远程服务器发送 POST 请求时，所使用缓冲区的最大大小，单位为字节。
当请求大小超过这个缓冲区时，Git 会使用 HTTP/1.1 的 Transfer-Encoding: chunked，也就是分块传输编码，以避免在本地创建一个非常大的 pack 文件。
默认值是 1 MiB，对于大多数请求来说已经足够。
需要注意的是，增大这个值的作用仅仅是停用分块传输编码。因此，只有在远程服务器或中间代理仅支持 HTTP/1.0，或者没有正确遵循 HTTP 标准时，才应该提高这个限制。
一般来说，增大这个值并不能解决大多数 Git 推送问题。同时它还可能显著增加内存占用，因为即使实际推送的数据很小，Git 也会分配完整大小的缓冲区。

1
2
3

[http]
        postBuffer = 16777216
        version = HTTP/1.1

1
2

git config http.postBuffer 16777216
git config http.version HTTP/1.1